Can you give examples ? That’s partly why I ask this question.

I think having instances or communities dedicated to that would be wonderful.

I think having separate identity providers would work well with this. Those identity providers could optionally verify age and location, and your instance can just trust them on that to make it exclusive to certain ages or locations.

You can only filter and sort what was downloaded by the client. So that runs into resource constraints.

There shouldn’t be resource constraint issues in downloading new content Metadata from all your subscriptions

tags

When I say “standardize tags on all content”, what I mean is make it a standard to have the option of having tags on every type of content, and treat tags as a first class attribute of the content. The XKCD you reference is not relevant.

That’s more the ATproto/Bluesky vision.

Sure, they use it. But it is compatible with activityPub as well.

I’m so far paging, and it’s so annoying this isn’t the default design on the fediverse.

On 4, I also agree, but what’s the best alternative?

I think instance owners should retain the ability to make some blocks non-negotiable. They are responsible for the instance and legal implications after all.

I do like this, but it does require responsibility from the user to maintain their keys. I think having it as an option is great, alongside the identity providers I speak about.

That’s precisely why I call it necessary, you’re right!

Thank you for listening to my idea, and I’m glad you like it :)

The first issue you bring up would be resolved with the idea of separating identity and authentication as separate providers from instance providers. In fact, it’s much better than just relying on a small difficulty, as that is more likely to discourage a well meaning non-technical person than a malicious actor.

Wktn separate identity providers, your instance can trust the identity providers that have good reputation. And if I want to be seen by your instance, then I have to have one of those identity providers approve me.

Different identity providers will have different standards and requirements.

The downside is that if you’re new to the fediverse, you have no way of knowing whose lists you should follow.

Isn’t the whole idea that you choose a trans-friendly instance and you naturally adopt the instance wide blocklist? Same thing here, except you choose the block list similar to choosing an instance in the old flow.

And if you disagree, this could still easily be mediated. For example, the instance could have a default block list. As long as one can opt out, that would respect user choice.

Or choosing the blocklists can be part of the account creation flow.

There’s others ways to go about it.

Beyond that though, on an instance like blahaj, it would be largely irrelevant, because there is no scenario where I let transphobes federate to the instance

What I suggest isn’t meant to take away the instance owner ability to defederate or moderate. But this makes it such that you don’t have to modify your moderation strategy when your users can adopt different moderation in addition to what you have. (example: maybe a large group of your users want to block US-centric content, or political content, etc.) and people not on your instance could possibly adopt your moderation as well!

An easy middle ground is the ability to sync your block list with someone else. This gives the same capability you desire, but allows users freedom to do it on their own. Everyone’s happy! What do you think?

I agree with this. I think instance owners retaining ability to block other instances is still unfortunately necessary, if at least for administrative and legal reasons. But putting the onus on granular blocking controls on the user is a big achievement, as I prefer the user to retain that control.

What exactly would be controlled differently under this direct democracy?

Can we please keep the respectful ones so we have a chance to dispel their beliefs? There is overwhelming propaganda against Venezuela that is easy to disprove, but most of their spaces ban us (example: reddit). I wish we have a chance to argue our perspective.

Not with gentoo!

I tried using bubble wrap for this purpose, but it’s too difficult and doesn’t seem to target this use case.

If you just make it public it wouldn’t be an announcement, and it wouldn’t have the irreplaceable first impression effect that you fear, because the only people who will see it are the very curious ones like I am.

At least explain to us what it’s all about if you won’t post it. I would love to know and see if I would be interested in contributing!

I don’t want to watch the people who aspire to do it as a job. They saw some influences online who are profit driven and think they can get similarly rich. Many see it as an easy job (it’s not).

I want to watch people motivated by their thirst for creativity and sharing knowledge, and if money comes their way they will see it as secondary. I would prefer them to do something else as a job.

bringing up RSS feeds is actually very good, because although you can paginate or partition your feeds, I have never seen a feed that does that, even when they have decades of history. But if needed, partioning is an option so you don’t have to pull all of its posts but only recent ones, or by date/time range.

I would also respectfully disagree that people don’t subscribe to 100’s of RSS feeds. I would bet most people who consistently use RSS feed readers will have more than 100 feeds, me included.

And last, even if you follow 10,000, yes it would require a lot more time than reading from a single database, but it is still on the order of double digit seconds at most. If you compare 10,000 static file fetches with 10,000 database writes across different instances, I think the static files would fare better. This isn’t to mention that you are more likely to have to write more than read more (users with 100k followers are far more common than users with 100k subscriptions)

And just to emphasize, I do agree that double digit seconds would be quite long for a user’s loading time, which is why I would expect to fetch regularly so the user logs onto a pre made news feed.

Sure, but constantly having to do it is not really a bad thing, given it is automated and those reads are quite inexpensive compared to a database query. It’s a lot easier to handle heavy loads when serving static files.