The good thing is that the DIY people don’t need to reinvent the wheel - you can just fork an existing project and shape it into what you’re interested in. There’s are already some bare bones implementations around that lend themselves well to building things on top of.
Of course not arguing that making it simple isn’t a good thing - but the reality is that interoperability between platforms like this is a complex challenge, and even though nothing is perfect ActivityPub is doing a pretty neat job making it a reality.
The growing options to just fork is an interesting and good point. Quite a few languages and stacks are now represented in some project somewhere.
That being said, we’re probably fast approaching the point where some form of generic modular software for the lower level stuff would provide a productivity boost to the ecosystem. My understanding is that there’s some work starting on that front for testing and maybe a sort of reference implementation.
No, just the work of building the federation part of a platform.
Look at both mastodon and Lemmy, both have a huge blind spot for a major part of the ActivityPub protocol. Mastodon doesn’t manage groups well and Lemmy doesn’t manage users well, as content creating actors that is. This is obviously by design to a large extent, but the difficulty of expanding the bounds of a platform to include more of the spec seems to clearly be part of the problem.
That platforms struggle to interact with each other more than the promise of the fediverse implies.
Segregated platforms is a hang over from competitive big social. It’s all just text messages in the end as webpages are all just HTML. Part of the promise of the fediverse is to break down these capitalistic walls. If it’s too hard to engineer though, then the promise may need some rethinking.
Well from what I’ve gathered it’s tough work for DIY people too.
The good thing is that the DIY people don’t need to reinvent the wheel - you can just fork an existing project and shape it into what you’re interested in. There’s are already some bare bones implementations around that lend themselves well to building things on top of.
Of course not arguing that making it simple isn’t a good thing - but the reality is that interoperability between platforms like this is a complex challenge, and even though nothing is perfect ActivityPub is doing a pretty neat job making it a reality.
The growing options to just fork is an interesting and good point. Quite a few languages and stacks are now represented in some project somewhere.
That being said, we’re probably fast approaching the point where some form of generic modular software for the lower level stuff would provide a productivity boost to the ecosystem. My understanding is that there’s some work starting on that front for testing and maybe a sort of reference implementation.
deleted by creator
No, just the work of building the federation part of a platform.
Look at both mastodon and Lemmy, both have a huge blind spot for a major part of the ActivityPub protocol. Mastodon doesn’t manage groups well and Lemmy doesn’t manage users well, as content creating actors that is. This is obviously by design to a large extent, but the difficulty of expanding the bounds of a platform to include more of the spec seems to clearly be part of the problem.
deleted by creator
That platforms struggle to interact with each other more than the promise of the fediverse implies.
Segregated platforms is a hang over from competitive big social. It’s all just text messages in the end as webpages are all just HTML. Part of the promise of the fediverse is to break down these capitalistic walls. If it’s too hard to engineer though, then the promise may need some rethinking.