We Distribute is teaming up with Bonfire to develop a new kind of social instance - one that elevates curation and discovery to promote all things Fediverse. It’s a social instance, but also a discovery portal.
Sounds like what I’ve been dreaming of for a while. Curious to see how things work out.
Sounds cool! Although I do not really get it.
I always miss the basic grammar of software platform announcements - making things hard to understand. Especially fedi-projects can be confusing.
So, it is an instance. How do I interact with it? As a user on that instance or any fedi instance?
Do I use the website or my own instance?
Basically who am I (the user), and what do I do? And where do I do it?
Thanks
The link to Fedizen.net in the article appears to be dead
Should be good now, we redeployed onto a beta release to test out some feature fixes. We’re basically dogfooding this every day!
Why is the development group not federated?
It should be now
I’m subscribed but there still seems to be an issue with the federation for Lemmy.
It’s going to be, group federation only partially works in Bonfire today. The devs are very close to shipping it in an upcoming stable release.
That’s… how lemmy works by default? I don’t get it.
Can you show me where Lemmy does this? I don’t natively come across podcast content from Castopod, nor do I see PeerTube content unless someone adds a link to a post. I don’t see Lemmy directing people to creators, writers, musicians, etc. What about articles ? I rarely see if at all articles that come from blogging instances
Seems to be a mix between what WeDistribute currently is, but aggregating content from different sources, and a Bonfire instance. So an effort to mix the old web with the social web. The best parallel to me seems to be websites with associated forums back in the old days, but a federated version.
I’m interested to see how it works out.
Is there a way to read the article that doesn’t download a file?
Unsure what you mean as the link works for me but here https://archive.ph/vd9um
Sweet it’s fixed. Thank you for noti





