iFreilicht

This particular image was done by Maxar, you can see it in the lower right corner.

You can already see it happening in the first reply to this parent:

https://news.ycombinator.com/item?id=29628333

Wait, seriously? How would you do that? And why doesn't it work for ssh keys?

I was under the impression password auth worked very similarly to key auth, as in, the actual bytes of the password or private key are never sent over the wire.

What about having the private key all components are signed with shipped on a USB drive (the SecureStick™) to you with the phone? It could be encrypted with your AppleID, so it's safe during transit. To re-sign new components, you plug the SecureStick™ into the phone, and it will try to connect to any other of your devices (that you of course also trust) to unlock the key.

In a repair shop, they could swap out the component and you then re-sign everything with your SecureStick™ when you come in to pick the device up. You have to trust the repair-shop, obviously.

Alternatively, you could re-sign all components with a private key you generate yourself? But then there's no guarantee that nobody else did just that in transit.

I did it the other way around putting Esc on CapsLock for the whole system. But yes, Esc is a pretty horrible key to reach for, especially considering how often it is used when interacting with vim.

A class with a single function can also be nicely modelled as a function.

That's not 100% accurate. Signal handles message history per device. If you link a new device, you can only see messages that were sent/received after that. There is no way to sync messages between devices, they all get the messages from the signal servers directly. This also means that you can use signal on linked devices if your phone is offline; you just need the phone for initial sign-on.

Especially easy with Vorta [1] and hosted on BorgBase [2]. It's definitely for the technically literate user, but if you are, then it's a dream, and the tutorials by borgbase are super nice.

I was searching for something the could replace Backblaze on Linux for me, and Vorta+BorgBase was even better than that.

Encrypted and compressed by default, deduplicated, life-long (if desired) and diffable history, every snapshot can be mounted locally, alerts on missing backups, just a breeze to use, and works for my personal machines just like my VPS.

[1]: https://vorta.borgbase.com/

[2]: https://borgbase.com/

There is an additional add-on that maked it wireless, but by default it's wired.

Oh wow, this is more than a performance problem, this is a mitigation for a data security problem that only got introduced because trackers try to work around per-domain cookie isolation.

Marketing and pre-installation on devices. Seriously ChromeOS and chromebooks have been gaining huge marketshare, Linux could've been that if there was any player interested and wealthy enough to put on a similar campaign to what google did.

In Germany, our economy pretty much depends on weapons and cars, so that.

But apart from economic reasons, not really.

For me, reST had the big issue of not being as quick to type as markdown. It's a better standard, that's true, and especially the table features are A LOT more useful than MD, but I've always felt a lot more mental resistance and less compatible tooling. I basically picked up MD on the side (on SO and GitHub), but reST I would have to learn.

I liked the idea of that law, but in high-density areas, it didn't change anything. The renters are now implicitly expected to cover the broker fee for thee landlord. If they don't offer that in advance, they won't get the apartment.

None that I found :( You can in theory use inkscape for sketching and then put the resulting SVG into Zim or any note taking app that allows embedding SVGs, but that's the best it gets from what I could find.

Meh, not really. Something being written in Rust is a feature to me.

You can host your own coordination server, right?

So like the ArchWiki but for all things tech, not just Linux?

All the free content you and I provided is our way of giving back to the community that answered our questions.

That content generates value for SO, but they do provide the infrastructure we use for free to get our problems solved and questions answered, so it seems like a fair deal to me.

If you didn't want anyone to profit from your answers, you shouldn't post them. If your answer is reasonably popular, you can bet it will be used in a product that makes money without you ever getting compensated for that.

Is the goal of Servo to replace Gecko eventually? I thought it was more of a testbed for new rendering techniques.

The Dell Precision laptops still have sodimms and M.2 storage, not sure about WiFi.

The idea for upgrading the CPU is that you replace the whole motherboard, but keep everything else.

Yes, the screen is easily swappable. The bezel is held in by magnets and the screen is held in with just four screws. Keyboard is replaceable and quite modular as well as the shell, keys and PCB are separate parts. The power jack is also replaceable. Actually, the whole I/O consist of four modules that you can swap out as desired (and a dedicated headphone jack), so you can decide how many USB-C, USB-A, DP and HDMI ports you want. A dedicated microSD slot is also available.

And no, it doesn’t look hard at all, the whole design is very straight forward. Which makes it all the more surprising why it took this long, but I’m glad someone finally makes it happen.

They highlight an oversized thermal solution to reduce thermal throttling, and say that they’re working on support of popular distros on their product page.

Untrue. The DIY-edition can be bought with no operating system, and they explicitly mention they’re testing for compatibility with popular linux distros.

Very cool as well, but a completely different product in my eyes. The Reform is something I’d tinker and play with, the Framework is what I’d put in my backpack and take to work every day.

Misleading title. This is a beginner introduction, no mastery to be seen. The examples are confusing and partly misleading.

Another reason is apparently modularity. There’s an increasing demand in wider stovetops with more or larger heaters, induction and so on, and having all controls on the top itself means users can combine all ovens with all stovetops. Additionally, ovens at eye-height are becoming more popular, so in some cases there isn’t even an oven below the cooktop.

You could have physical knobs on the top, but those interfere with the pots and sealing them against spills is hard. The only decent solutions I’ve seen are magnetic knobs and a dedicated knob bar that is installed at the face, with drawers below it, but those are much more expensive to produce.

I think Nix will take a long while to increase adoption, because it is hard to learn. The language is new, the concept is new, the mental model is new. But you need to master all of those to use the tool effectively.

Same goes for the other items in your list. Git had enough time and force behind it, and I believe the other tools will succeed as well. But it will take time.

People also love to create and get new and shiny things. Combine that with force of habit, and you get truckloads of engineers that tear down and replace what was working and only needed maintenance.

Both forces exist, the important part is to balance them properly.

Yes, absolutely.

I have to mention Joplin here, which became my note-taking app after a lot of research. There are certainly more powerful apps, but Joplin is open source, runs on all devices, (Windows, Linux, Android and iOS in my case), syncs data via Nextcloud or Dropbox, and supports E2E-encryption. It also allows inserting images directly into the notes, which I found cumbersome with other markdown-based note apps.

The developer is also very active and adds useful features and bugfixes very regularly. Definitely worth the few bucks I donate every month.

https://joplinapp.org/

Unless you're working with strings, which are a hell of a nightmare to use safely. It's become a lot better in terms of the stdlib, but even stuff like the supposedly safe vsnprintf may quickly ruin your day and open potential overflow exploits if you forget to accout for the space of a null terminator or accidentally write the return value to a size_t instead of an int.

Error handling isn't obvious either. The linux kernel does it the right way with error code returns and results in pointers, but that's not the obvious way at all.