Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |
| fediverse-notes-users [2025/12/04 07:30] – z428 | fediverse-notes-users [2025/12/04 08:59] (current) – z428 |
|---|
| * There's no really good way of general "Fediverse level" support for end users especially when it comes down to needs and feature requests. If you have immediate technical questions, in most cases your instance admin will be able and happy to help. For more fuzzy technical questions, like communications noticed to be lost between users on different instances, it gets more difficult and requires a bit more knowledge about project structures, people and their means of communication - yet it's still somehow possible. But at the very least if you are, say, on Mastodon and want to be able to see your pixelfed contacts stories, you're basically lost. At this point, so is the Fediverse promise of not needing accounts on more systems anymore because "everyone just can talk to everyone else". | * There's no really good way of general "Fediverse level" support for end users especially when it comes down to needs and feature requests. If you have immediate technical questions, in most cases your instance admin will be able and happy to help. For more fuzzy technical questions, like communications noticed to be lost between users on different instances, it gets more difficult and requires a bit more knowledge about project structures, people and their means of communication - yet it's still somehow possible. But at the very least if you are, say, on Mastodon and want to be able to see your pixelfed contacts stories, you're basically lost. At this point, so is the Fediverse promise of not needing accounts on more systems anymore because "everyone just can talk to everyone else". |
| * Somewhere near the community aspects of things: One of the usual selling points is stating that things are compatible and it's cool that every system can talk to every other system because they're all using the same protocol - until they are not. As outlined before, there's no shortage of interoperability glitches in the Fediverse, and also there's no shortage of that dreaded "works-on-my-software" attitude and people stating that whichever (valid) problems one might encounter or run into are just problems caused by their (obviously stupid) choice of federated software. It all too often boils down to fingerpointing and blaming "the others" for messing up compatibility and being in charge to fix things on their end. | * Somewhere near the community aspects of things: One of the usual selling points is stating that things are compatible and it's cool that every system can talk to every other system because they're all using the same protocol - until they are not. As outlined before, there's no shortage of interoperability glitches in the Fediverse, and also there's no shortage of that dreaded "works-on-my-software" attitude and people stating that whichever (valid) problems one might encounter or run into are just problems caused by their (obviously stupid) choice of federated software. It all too often boils down to fingerpointing and blaming "the others" for messing up compatibility and being in charge to fix things on their end. |
| * Especially if coming from Facebook, visibility settings of posts behave not as expected. No matter whether wanting to temporarily hide all posts ever made from any visitor of ones profile regardless of contact relationship or wanting to add or remove access to individual posts for certain users retroactively - the current nature of federation doesn't seem to handle this at all in any platforms out there (tested on Sharkey, Friendica, Mastodon, Hubzilla). | |
| | |
| |
