I really wonder how you managed to uninstall nix. Editing configuration.nix shouldn’t even allow for removing .nix…

Anyway, this post made me remember why I used btrfs for my new btrfs system.

That’s one of the reasons I don’t like buying games with Denuvo. Waiting a few years before buying games is something I usually do anyway, so at that point Denuvo DRM would’ve already been removed.

Good idea to write a function, I’ll do that right now. Over the last few weeks I’ve been regularly doing the Ctrl+Z, bg, disown, which does get old pretty quickly. At least I now remember the terms and don’t have to search for them each time I need it :D

I’m honestly fine with DRM, as long as it’s removed within my definition of reasonable time. I’d say a year vor two.

Once the DRM is removed it allows for archiving and preserving the piece of media — as well as pirating copies.

No, this runtime only works if the developer enables it on their side.

I believe the advantage is that old drivers still work as they are all in the kernel. With them sharing much code it’s not even that big of a disk space issue. Edit: A more dynamic approach would be great though, especially with this size issue popping up.

In a way it’s great that I’m able to replace any part of my system and it just works without me having to make sure the old GPU driver doesn’t leave some traces behind–altough while writing this the latter part shouldn’t be an issue with Windows auto download and installation of drivers.

Really very similar to Lemmy, where the identity of each group is tied to a particular server, e.g. lemmy has !anime@ani.social but Matrix has #anime:matrix.org

So what happens if matrix.org goes away or decides the server admin wants to be hostile to #anime?

A matrix room can have multiple identities/adresses set by the room admin. E.g. the admin of !anime:matrix.org could add another adress for the same room on !anime:myanime.instance. Because the room is replicated on all other participating servers, this would let the room continue to exist on the network (besides all matrix.org users not being able to access it).

Matrix does have a single “room id” per room, which looks like it gives the original creating home server more rights, which it does not. E.g. !ehXvUhWNASUkSLvAGP:matrix.org

Any server admin does not have any more rights over a room than another server admin. They can ban the room for their local users, but this does not stop federation as a whole.

[1] https://github.com/element-hq/element-meta/issues/419
[2] https://app.element.io/#/room/#synapse:matrix.org/$htJmba92wLTP9AoFg4eEWi9IXpgwvXr6G9Sa-kBsNNs
[3] https://matrix-org.github.io/synapse/latest/admin_api/rooms.html#delete-room-api

It also appears that anything beyond text has to be hotlinked […]

Matrix allows for media to be hotlinked, but it can also be replicated across servers.

I.e. if I send an image in a room and look at the source (available on many web clients), the image url looks like the following "url": "mxc://matrix.org/qGgUKuZuHcRsWAhSfqKnmtiX". The actual image (and preview) then gets fetched by your server from my server [4], and then gets send to your client.

It’s important to note that a server isn’t required to download all media. If a user does not read a room, it might not download the media from another server, until the user actually wants to view it (or rather that part of the room history). Or a server admin might clean up the media store to free up space.

[4] https://matrix.org/docs/spec-guides/authed-media-servers/

@JackbyDev@programming.dev

They do basic checking for known malware.

You’re right. I’ve read somewhere that Apple plans to work with GSMA to add encryption to the official RCS standard, so this major issue hopefully gets fixed at some point.

RCS isn’t E2E, and it doesn’t minimize metadata.

Moxie Marlinspike has been strongly against federation in Signal because of how it makes avoiding metadata almost impossible.

I’d say there’s basically zero chances Signal will add RCS.

I’d argue XMPP is less ideal than Matrix because groups are located on a single server, which makes them easier to take down than Matrix’ replicated state.

Running any P2P/decentralized protocol over I2P seems to be the best for privacy and censorship-resistance. I2P already works great for torrents, except for it’s speed and lack of users/seeders.

@zabadho@ani.social

The problem always comes down to usability and barrier to entry. Telegram is popular because it’s great to use, and doesn’t moderate much. More private services rarely (never?) reach the level of usability most people expect, often simply because of it’s architecture.

Removing nix is mostly done by deleting /nix, and removing some systemd services, as well as deleting some nix-related users or groups (iirc nixblkd)

Because almost all of nix happens in /nix it doesn’t clutter much of the system.