As far as I can tell, following someone via Kbin is for either getting their microblog posts (Mastodon-style) or for more generally getting their activity federated to your instance (if it’s like the general ActivityPub concept).
Just somebody that you used to know.
As far as I can tell, following someone via Kbin is for either getting their microblog posts (Mastodon-style) or for more generally getting their activity federated to your instance (if it’s like the general ActivityPub concept).
If you could run your own Signal instance, then that could help alleviate concerns of bad faith operators. That’s what Session is essentially (started as a fork of Signal): https://getsession.org
It’s not reactive. A proper reactive system can handle fluctuations in usage patterns more robustly.
Anything less than 99% of infrastructure working that way would be surprising. Everything is held together with scotch tape and scotch whisky.
Spez is playing both sides so he comes out on top!
There are two legitimate concerns about Signal: they use real phone numbers as identifiers, and you have to trust Signal as the server operator as they don’t allow their client to be used with other servers. While the server software is also open source, you have to trust that they’re running the same version in production.
Oh no, Apple develops Apple-specific features to add value to their products! Someone alert the Department of Justice! My bubbles will NOT be discriminated against!
No need to refresh. Duplicate replies are a fact of life on federated sites or threads that get a lot of activity.