Maybe Torvalds will make Sebastian understand that Linux is not a product, it’s an ecosystem, and maybe finally make him review Linux properly without the “as an average tech consumer” approach he’s been doing. It’ll never be “ready” through that lens if always approached with a FOMO attitude.
One can’t be free when sucking it up to big tech all the time because “you need the latest fancy half baked proprietary features”.
You need to set up your PC to be on that IP address first, TFTP doesn’t magically listen to a particular IP, you need to configure the PC with that IP.
ip link set eth0 up
ip addr add 10.10.10.3/24 dev eth0
ip addr add 10.10.10.1/24 dev eth0
Then you can start the TFTP server on the interface:
dnsmasq -d --port=0 --enable-tftp --tftp-root=/path/to/tftp/root -i eth0
This is why when an app pops up that permission dialog, you always say no. The number of permissions Meta apps ask immediately upon startup is a red flag on its own.
Can’t collect and upload what it doesn’t have.
For all its flaws and mess, NFS is still pretty good and used in production.
I still use NFS to file share to my VMs because it still significantly outperforms virtiofs, and obviously network is a local bridge so latency is non-existent.
The thing with rsync is that it’s designed to quickly compute the least amount of data transfer to sync over a remote (possibly high latency) link. So when it comes to backups, it’s literally designed to do that easily.
The only cool new alternative I can think of is, use btrfs or ZFS and btrfs/zfs send | ssh backup btrfs/zfs recv which is the most efficient and reliable way to backup, because the filesystem is aware of exactly what changed and can send exactly that set of changes. And obviously all special attributes are carried over, hardlinks, ACLs, SELinux contexts, etc.
The problem with backups over any kind of network share is that if you’re gonna use rsync anyway, the latency will be horrible and take forever.
Of course you can also mix multiple things: rsync laptop to server periodically, then mount the server’s backup directory locally so you can easily browse and access older stuff.
It won’t do much in english, but makes a lot of sense for french, spanish and other languages using heavily gendered nouns.
In english, “the user” is neutral. In french, you have “l’utilisateur” and “l’utilisatrice”, because everything including nouns are gendered. So you’re stuck misgendering half the population by default. This lets you address women as women and men as men.
The writing’s been on the wall since they swapped to ColorOS with Android 12 and the bootloader update that came with it that no longer supports relocking, along with the delayed/nonexistent source code releases for the kernel.
It’s very sad that basically the only real option is Google’s Pixels, and even there the tides are turning.
Technically it wasn’t really designed with megainstances in mind that swallows the entire fediverse.
My instance has no problem whatsoever keeping up and storage is well under control. But we’re few here subscribed to a subset of available communities so my instance isn’t 90% filled with content I don’t care about and will never look at. Also reduces the moderation burden because it’s slow enough I can actually mostly see everything that comes through.
Lemmy itself is also pretty inefficient in that regard, you can very much make software that pulls instead and backfill local cache as needed.
Even my Reddit subscriptions would be pretty easy on my instance.
deleted by creator
One thing to keep in mind is ActivityPub isn’t exactly made for social media in the sense most people use it nowadays. It’s intended to be more like RSS feeds: you’re support to subscribe to stuff like news sites and be able to bring it all into a content aggregator. Seen that way, its design makes a lot of sense.
It kinda works well for public microblogging as well. It’s when you start involving moderation, voting, sharing, boosting that things get kinda weird.
I’ll add some of my comments to that discussion.
You guys have basically been describing Aether and Nostr
The main issue is when your instance starts federating, accounts are created with a key pair that you will lose when changing software, and generally a whole bunch of URLs will no longer be valid. The actor ID of your user is https://feddit.org/u/buedi, not just buedi. Mastodon might make it https://feddit.org/@buedi instead. As per the spec, that is the canonical URL for the user/actor.
Other instances will still try to push content to your instance assuming the software it was registered with. So you may continue to receive data for Lemmy communities which Mastodon has no clue what that is or what to do with it.
You can host the API/frontend on a different domain no problem, but the actual ActivityPub service should be on a dedicated subdomain to avoid the issues.
That said, I believe after a couple days/weeks, it should eventually sort itself out as your instance keeps erroring out and gets dropped and reregisters with the new software.
There’s a reason it only supports Pixel phones: none of the other manufacturers produce phones that are suitable for it. All the other ones either don’t let you unlock the bootloader, won’t let you relock it with your own keys, or disables other security featurea. Meaning anyone can just flash whatever code they want to the phone and completely nullify the security model.
For a bit, OnePlus did support this but they quietly removed that feature with the Android 12 bootloader update, and otherwise cut you off from the TEE anyway so the OS can’t even verify the boot chain.
The GrapheneOS team said they would happily support other devices if any met their criterias for support. None do. Pixels are the only phone where you can properly flash a custom OS on, and relock the bootloader and disable OEM unlocking like it’s the official OS with all the security features functional.
For decades, we offshored that stuff there because it was cheaper. Now we’re acting shocked pikachu that the asians that have been producing our chips for the last 30 years are better than us at producing chips. Not just chips, hell of a lot of manufacturing in general too.
We may have the brains that designs the chips here, but the asians have the hands on experience at the fab, so…
That seems like a good way to get vendors to start only shipping firmware updaters that only runs on Windows again.
I don’t think I’ve ever updated a BIOS from any operating system, always flashed via the BIOS itself. Most can flash the BIOS without even a CPU installed these days.
It’s a good idea to validate the information before being outraged at it.
If that works, something with the PipeWire state might be weird. Tried deleting pipewire/wireplumber in ~/.local/state followed by a reboot (or restarting pipewire and wireplumber). That should reset it.
Aside from the other answers, no you can’t offload computations to memory. Memory stores data, it doesn’t compute.
The only way having more memory can possibly improve performance, is by having a cached copy of files so they don’t have to be fetched from disk, and applications potentially caching the results of heavy but reusable computations. (Unless you run out of memory and starts spilling over to disk, then more memory will make it fast again by avoiding swapping).
I mean I guess technically yes you could transcode into H264 into a tmpfs mount, and then play the H264, but you’re still not doing it faster and certainly not fast enough to watch in real time, you’re just decoding the AV1 well in advance before actually watching it.
Nope. Even Qualcomm themselves provide what’s needed to run Linux on the Windows for ARM PCs.
The only one I can’t find for sure is whether there’s any lockdown on the firmware for the Microsoft Surface and Copilot+ laptops, but I’m also not finding any sources pointing that it would be. But at this point you’re buying Microsoft hardware, what do you expect.
It has nothing to do with ACPI whatsoever. And firmwares this broken are the exception not the rule.
You can mostly backup everything but it’s impossible to make a perfect backup like the old days anymore because of the TEE. Flashing a new ROM will change the keys and permanently make the old data worthless. Stuff like Google Authenticator for example simply won’t backup even with a perfect bit copy.
Apps will restore okay but many will be logged out and have lost their permissions and push notification registration with Google.