Works with CUDA and RDPing on a 2x2 monitor grid?

You said you used river, so I’ve checked their wiki https://github.com/riverwm/river/wiki/Recommended-Software#output-configuration

Maybe you can add your tool there as well.

Looks similar to https://git.sr.ht/~leon_plickat/wlopm/

It would be best to try every single one separately, otherwise you’ll have dozens of programs that do the exact same thing, like file explorers.

That said, with Fedora you can list available desktop environments using the default package manager, dnf. In a terminal use the dnf group list command to list all available desktop environments:

dnf group list --available *desktop

Install the required desktop environment using the dnf install command. Ensure to prefix with the @ sign, for example:

dnf install @kde-desktop-environment

After trying the DE, you can remove it with:

dnf remove @kde-desktop-environment

Fun fact: acrobatics are made with lower hydration dough.

If you want dough with crispy outside and soft inside you’re looking for a 65-70% hydration. Acrobatics with this will rip it apart. To open a higher hydration dough you use this technique: https://youtu.be/xzbW8CZx538

Sorry to burst your bubble, but there already exists a proposal to make communities work more like a cloud.

It’s just a matter of time before Lemmy and Kbin implement this.

Yes, the proposal is something like Nostr, but the clients can also relay data on request if they’re online. A little more decentralized.

Worth mentioning that the idea is not to make Lemmy abandon ActivityPub, but to allow further decentralisation.

There wouldn’t be a need to keep all data like a blockchain to query all data since most sort by hot/recent. Something like Gossipsub would suffice for most users.

But whenever an user queries for old or specific data, the request could be directed to a relay that archives and sorts all data.

Not a completely different protocol when the changes are additions to the existing one. The same protocol would still exist and be supported.

P2p enabled instances would have the option to reverse the communication flow, so besides the servers having to send updates to subscribed servers, the subscribers would have the option to ping peers/servers for updates.

This would help with sync issues when a post is made and the changes are not propagated to all subscribers.

Roaming IP wouldn’t be really a problem with libp2p, you can have a permanent address with a peer id.

Most people don’t come here to see archival stuff, so it wouldn’t be so bad if the p2p network cached ephemerally (time limit or a size limit). Old content could still be reached on servers designed to cache old stuff.

Events could be cached on the p2p network, so the phone only pings its peers for new content (mind the existing servers would be peers on the network).

You wouldn’t need to run the service 24/7, just whenever you’re using Lemmy and maybe a few minutes after so your interactions can propagate trough the p2p network. Also the existing servers could be used to cache and relay.