Azura

If the community is hosted on the defederated instance then I believe you wouldn’t see that post either. I believe the community instance reposts the post so that it can federate to all subscribed instances. And those might only be known to the instance that hosts the community. So everyone goes through it as a proxy.

The way I was thinking you could still go to the original community and skip the aggregated one. So you could have c/gardening and c/flowers, but also c/backyard which could combine the two. You could still go to either one, but for easier discoverability you could create aggregators or include an aggregator in your community, and do this cross server. So if you have two very popular and overlapping communities you could combine them easier. Could also be a client feature I suppose. But right now you’d have to manually hunt for the possibly dispersed communities yourself. Alternatively I guess there is an argument for smaller communities being better which I do agree with. It was just a not very thought through idea :) Or you could have community redirects. So c/technology on lemmy.world could decide to seamlessly redirect to c/technology on Lemmy.ml if wanted. Edit: although the more I think about this the more it sounds like more trouble than it’s worth.

I think community consolidation/aggregation is something that might want to be looked at. It’s possible to have a gardening community on multiple servers with different content. This will confuse people. So having a way to merge posts from two communities into a bigger community per server may be a good idea. So if you set up gardening communities on two servers you can choose to have posts show for each of them in your community. And making this a server or community setting still gives the ability to either have this or not have this if the communities are truly supposed to be separate. This would also give some kind of redundancy where the original community server can go offline but multiple different servers can still exchange messages that eventually make it back to the main community. Truly decentralized.

The point is that someone wanted to make it, and then made it. It doesn’t have to have billions of users to have been fun to make, or even to have reasons for existing. Pixelfed needs a few people to want to use it to keep existing. Instagram needs all of you + your data. And once it inevitably does something people are unhappy with, Pixelfed will be there. And once the service people will somehow find themselves on after Instagram does the same, Pixelfed will probably still be there, then. As long as one person is interested in running an instance/updating the software/either of those two, it will keep existing. People used to, and still do, post pics on their website. What’s the point of that? People who have friends on Instagram will stay on Instagram. People who have friends on Pixelfed/Fedi as a whole, will probably keep using Fedi. It’s not an all or nothing game.

Because everyone uses the internet exactly like you do. :)

Owncast is streaming only, PeerTube has streaming as a feature. If you’re only looking to stream, run Owncast. It’s lighter on resource usage, easier to set up, fewer moving parts. If you want video hosting with maybe streaming as a bonus, you want PeerTube.

Maybe someone here already said this but if you find a community with not a lot of traffic here, make sure to post in it. Others might go looking for it and find nothing, just like you did. Perpetual cycle of I see nothing, I leave. If someone’s active, maybe someone else will be active with you. And then two turns to four to 8 and so on. Even if it feels like you’re screaming into the void, keep screaming. The void is infinite and someone’s bound to hear you eventually.

Yup also doesn’t work on Mlem for me

Don’t forget accessibility. Vision, motor, etc. sorry but the state of most of that is not so good right now.

I should X that sounds like I should delete/close that. How apt.

I personally like Mona.