Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Follows per User, not Blog #285

Open
64bakerst opened this issue Jan 31, 2024 · 0 comments
Open

[Feature Request] Follows per User, not Blog #285

64bakerst opened this issue Jan 31, 2024 · 0 comments

Comments

@64bakerst
Copy link

Using the ActivityPub plugin, for my community, users can have their own profile and ‘micro blog’ on the site – so anyone in the Fediverse can follow an individual user.

But when it comes to following someone, it’s very inconvenient for them to have to create a fedi account somewhere to follow people – they want to be able to publish once from the community/magazine, and also interact with the rest of the fediverse from that profile on our domain – just to have one identity.

Could you please make a version where any user on WP, perhaps with x role (like Author), can follow any account and have their own internal feed on WP, so it’s not per blog, but per user.


I don’t have immediate plans to implement this but I see some obstacles where I’d be curious how to solve them. For example: who should choose which feeds to be followed per user? i.e. what if one user adds an RSS feed to a person they follow and another one doesn’t want that?

Then the person who doesn't want the feed doesn't see it.....?

What I'm saying is the following mechanism should act like a standard fediverse platform - the site (or "blog") collects all the posts from the feeds users follow - so then there's a "Global" timeline which shows everything that gets pulled in - User 1 follows Fedi Account A, and B User 2 follows Fedi Account B, C, and D - so Global Timeline gets the posts from Fedi Account A, B, C, D.
Then the personal timeline shows A & B for user 1, and B, C, D for user 2, and so on.

It's up to the site admin to also set domain blocks if they don't want to pull in the feeds. And to clean up the database if users leave, or after x amount of months/years. So this is really an advanced function. But a need that is growing as Wordpress is becoming a community building "OS".

I'm using Voxel - and can share my use case further, in how I'm implementing ActivityPub for CPTs, for Fedi accounts to follow users from the community - but would like to implement the reverse as well, so the community isn't just a 'publisher', but interacting with Fedi and becomes it's own Fedi network.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant