944 karma · joined December 5, 2010
The idea of the PLUS variant is both simple and effective: instead of verifying <user,password> with the help of a salt you are verify <user,password,tls session key>.
That way the authenticating is only valid on a single TLS connection.
This is also called channel binding.
Oh my. I guess this needs some more attention. This might be a state actor open source supply chain issue.
And it is particularly bad timing. 23.10 was released yesterday, so a new kernel should roll into 22.04 soon. It would also fix most of the software complaints if the auther would have used 23.10.
Please save yourself from the hassle of compiling a kernel, especially for Ubuntu (the userspace _expects_ Ubuntu patches, e.g. for apparmor). Pick a distro with a recent release, and for Ubuntu in particular check if you can live with 2 upgrades a year until you reach the next LTS (April of even years, so right now the _next_ upgrade. Worst case is 3 upgrades).
I am not a "fan" of the fan noise, so I checked and the EC firmware was open source. It was possible to raise the fan tipping point to run the laptop hotter and more silent.
People have also tried to set the power clamping later. That works and is equivalent to limit it in the BIOS.
Key point is: this does not mean you have to run it that way. Add a power profile, l configure the fan curve, enjoy.
Germany has an opt-in policy for these programs: I would have to go to the Bundespolizei (federal police) at an Airport to declare that I am fine with regular data transfer of my police records. Only afterwards can I join these programs. Sorta double opt-in: opt-in in Germany, opt-in in the US.
So I am surprised this is news as it is exactly what I am told the program is doing. It's also not like this is a search on social media and alike (something that could also happen and would be a huge privacy breach).
Is the main issue here not the US but that other countries share this without better explanation / opt-in controls? And to be fair I hate that I would have to go to an Airport to kick this off. It's horrible UX but good privacy defaults.
One of my favorites is extensive rights management. Especially on CMS. More ofte than not it is part of a buying decision, but used Stallman style soon after.
The observation that these credentials leak is correct. Or that you grow permissions over time for no other reason than doing work. A wheel group would today quickly attract users, too.
So let it be. The latest iteration is "basically let everyone, but audited and short term only". I find that very close to Stallmanns idea, for very different reasons.
Anyway, everything wondered where "Pull Requests" come from? Literally an E-Mail saying "please pull my branch ... at ....". Git has special tools to create and apply mails.
GitHub copied most of the LKML/kernel development flow and turned it I to a web UI. That's nice, but the text workflow is often faster and easier. And it works. And it is decentralized (a key requirement).
So yes. It is not broken. And GitHub would break the decentralized nature to some extent.
The constraint for large scale city heat pumps in the winter would be that you don't freeze up the ground. The suggested solution is A/C via heat pump in the summer. But if you have just too much excess heat anyway then that's actually good news.
So the options are bootcamp or not. Not from the ground up or not. Bootcamps cater thst group. Ideally skilled, smart, willing to learn but on a tight schedule and in need of a job.
This also changed my mind a bit on how to think about bootcamps. They are a way to give people who couldn't afford a longer education on the discipline an entry point.
All the success or failure is still on the person, and there is a lot to learn, but I respect everyone going through the hard path.
The try/catch construct require too much code for the common propagate case.
It would be nice if Java had a similar construct for error handling.
This has actually been the case in Germany (and perhaps even EU) for a while. Mostly because courts have ruled that cancelation must not be harder than signing up.
In Germany they were especially trying to force you to send letters or fax cancellations when you could sign up or upgrade via phone, e-mail or web form. Courts said no to that practice.
Are people fleeing the Windows as Ad Space direction? Are they fed up with Mac OS oddities? Do they use their Steam deck more?
Or are they just enjoying the Linux experience....
I know that after years of Linux usage I can't stand Windows in-your-face Ads and "use our accounts". And I can't stand the locked down Apple ecosystem either. But what drives others? Are there any good sources on that question?
The OS is open source. The finish is good (though not high end materials but still water proofed), runs for multiple days and does phone notifications just fine.
It is very bare bones though.
Fiber slows down Berlin <-> NYC by a lot. I usually use Wolfram Alpha for this and it's like 30ms fiber vs. 21ms vacuum.
So in theory starling could offer less hops and better latency. The detour to space isn't that bad either, ~1100km on a 6500km route, and fiber will need some extra hops and detours too.
A common theme is to set the user ro "deleted user".
As long as it is not associated with you it's fine.
Also you request deletion that the party and their contractors hold. So a mailing list may not show your name for past messages, but delivered mails are outside their perimeter/scope.
So very likely tied to the most common national air quality scale.
So it's explicit in what it shows.
OpenWRT supports a few lantiq systems with xDSL modems.
I was running both, but in the end switched to bridge mode on a dedicated modem.
You can run your linux kernel with init=/bin/bash and .... well, you've got a shell!
A minimal init system can be a shell script that starts some services. Job done. That has historically been the way to do it. There are also several other init systems that are native code based.
Systemd is at the other end of the spectrum. It will setup cgroups and resource limits, syslog sockets per service, supervise services, support socket activation etc. etc. And that's without looking at timesyncd, resolved, networkd and a whole set of other systemd tools.
I personally find it to be rather low complexity for what it offers, but it has a higher baseline complexity, so be prepared to learn along.
And finally.... The maintainer is a rather controversial personal of pulseaudio fame.
Still, it could be not disclosing it in such cases and live with it in a gray zone.
At 30 TBs the hot data set is huge an there is a long tail of queries not loaded into memory.
Plus they were saying 10k+ connections per server. So we are probably looking st 500k+ connections.
There is also a regular influx on unoptimized / badly written queries as people add features/games etc. Plus you can end up with random spikes.
This setup is likely optimized for high read availability. The slides mention the mental overhead of failovers. This is a thing. Try to explain and help each team understand how to do those safely. Downtime are also not an option.
So there is quite some information and context (likely) missing. I used to manage a similar scale zoo of MySQL (similar peak QPS, less total data iirc). I am not sure I would subscribe so much on the Vitess as solution side though. Galera and Group Replication can give you hassle free failovers, add some read replicas and you have a really nice DB setup that can scale horizontally amd vertically until you hit the write limitations per server.
Less bandwidth. Some users pay for bandwidth. Or have a monthly cap. So less bandwidth is a monetary advantage for users. It also may decrease time to play.
Similar, but less ctitical, for storage.
One rule of thumb when switching codecs is "don't decrease quality". I buy that Meta did that. Which would result in a slight improvement in quality (of course sold as big snd noticable) while getting storage and bandwidth down (or allow for better quality in the bandwidth adaptive case).
That saud. Yes. OPUS! Although other aites got quite some bad press for low bitrate opus.
This project is beyond awesome, but keep in mind that HW support also boils down to kernel and OS support. E.g. Audio support is still a mixed bag and only started (partially) working with the latest update.
I couldn't find the number with searches (I tried before) and I didn't even know that it might be helpful (didn't find it before, so how could I tell) but the AI spilled out and told me how useful it is.
This made me change my mind on search vs. AI. I got what I needed while I was unable to retrieve it with search. It was at least a 10x improvement over search.
But I do think there is space for both.
I prefer the search on the original sites, but this looks neat if you want the payload of a package.
The 1200h are slightly above the 1000h target put in place by the cartel.
Go back 10 years and many laptops had issues with cpu frequency scaling and sound quality. (Cheap components that would either start producing audible or em noise that would impact sound)
I am not sure if the last chapters of "The hard thing about hard things" or "Venture Deals" had more details.
So you can expect Series A with fresh funds and money (10 years runtime left).
They weren't old enough by 2020/early 2021. Series A was 2012. It's usually 10 years after that you need to IPO.
So the expected IPO would be 2022. Bad timing/luck.
Similar for those option plans. Planned IPO +2 years should OK. Unless it hits you like the last 2 years.
It does not turn the speakers into something high-end, but it is significantly better than before and easy to swap.
Podman is what you would want to learn on top.