![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/1be75b15-2f18-429d-acf7-dcea8e512a4b.png)
That could also mean client API-compatible, so Lemmy apps would work with it, which doesn’t address federation.
That could also mean client API-compatible, so Lemmy apps would work with it, which doesn’t address federation.
Will it federate with Lemmy? I would miss you folks.
Who cares? It’s run by reactionary incels, transphobes, and racists.
Wait until you find out who runs Lemmy development.
Anthony Bray the convicted burglar?
I have read that early DualSense units had a bug that affected battery life. If you still have yours, it might be worth updating the firmware.
Or the well-maintained and developed derivative:
https://f-droid.org/en/packages/com.shatteredpixel.shatteredpixeldungeon/
Tell me you’re an opinionated novice without telling me you’re an opinionated novice.
(edit:specificity)
Wildermyth is a lovely combination of storytelling and xcom-style combat, with a genealogy system and chances for your heroes (and their descendants) to reappear in future games.
It wasn’t a recorded video. It was a live stream. They must have made it private when it ended.
Use Tor.
Do you mean Tor Browser? Because using Tor alone won’t stop fingerprinting.
This one offers daily trading cards for finishing a discovery queue, and stickers for following a “browse by category” link on the main page and clicking the “claim” button.
Looks like the site is overloaded at the moment. Some things are not working quite right.
Related: A very similar question posted by the same person yesterday.
How to turn them square?
I don’t think yt-dlp has built-in image cropping, so it’s just going to download thumbnails in the resolutions provided by the server. (See the --list-thumbnails option.) To crop what you download, consider a tool like (ImageMagick)(https://imagemagick.org/).
Lemmy tip: Don’t indent your paragraphs.
We’re writing in Markdown here, so 4+ spaces at the beginning of a line triggers code formatting. It breaks line wrapping, so many readers are forced into a lot of horizontal scrolling back and forth if they want to read your text. It sometimes also breaks color schemes, burning dark-mode readers’ eyes with blocks of bright white.
Back to your request…
Your description reminds me of bits of Cyberpunk 2077 and Overwatch, but I don’t think it’s either of those. It doesn’t exactly match any games I can think of right now. Good luck. :)
Obviously you need someone joining the room for the room metadata to be shared between homeservers.
Well then, your assertion that Matrix gives it freely is false.
Not so with Matrix, where a joining homeserver get full retroactive access to all the room metadata since the room’s creation.
This is false, too. Historical event visibility is controlled by a room setting. (And if you don’t trust admins of a sensitive room to configure for privacy, then you’re going to have bigger problems, no matter what platform it’s on.)
Edit: I suppose you might argue that you can bypass this by running your own homeserver and attempting to join the room from it, thereby granting visibility not through joining (as you wrote), but instead through federation with the server you control. The thing is, you can’t do it without permission. Room admins can simply deny your join request when they see what server you’re on. This might make sense in a particularly sensitive room, for example, just as it would to restrict history visibility.
you really need to stop privacy LARPing
LARPing? I’m not the one stirring up drama with falsehoods and patronizing snark, am I? Farewell.
Matrix stores all this info and gives it freely to other servers retroactively(!)
Can you show me the part of the spec that allows a server with no room members to get private room info from another server? I’m skeptical, but if true, I believe that would be worth reporting as a bug.
network layer sniffing (which is anyway much harder to do)
You’re funny.
The network layer of all internet servers reveals almost everything you listed. Signal has the same problem, and there’s nothing they can do about that. The only way to avoid it is to use a completely peer-to-peer model (Matrix has started work on this, btw) and avoid communicating across network routes that can be monitored.
There might be one exception, depending on what you mean by “Accounts”: The user IDs participating in a room can be seen by server operators and room members. But then again, server operators can already see their users’ IP addresses (which is arguably more sensitive than a user ID), and I believe room members have to be allowed into the room in order to see them. For most of us, that’s fine. Far from a disaster.
Human behavior is funny, isn’t it? No matter what the topic, there are always people around who like to repeat criticism they heard from someone else, even if it’s so vague as to be useless (“metadata disaster”) or they don’t understand the details at all.
It’s not a disaster. A few minor bits of metadata (avatars and reactions, IIRC) haven’t been moved into the encrypted part of the protocol yet. If that’s a problem for your use case, then you might want to choose a platform with different flaws, or simply avoid those features. It’s already good enough for the needs of many privacy-minded folks, though, and it continues to get better.
Indeed, protocol is independent from implementation language, but that isn’t the question at hand.
Do you know whether Beehaw will still federate with the lemmyverse (and therefore the rest of us) after moving to Sublinks?