I think what @light wants is a Fediverse Custom Feed (rather than a List).
RE: https://mastodon.social/@light@noc.social/114162333801375136
I think what @light wants is a Fediverse Custom Feed (rather than a List).
RE: https://mastodon.social/@light@noc.social/114162333801375136
I have been talking about Custom Feeds for the Fediverse.
I will be setting up a demo server for Custom Feeds — so Fediverse developers can ad support for Fediverse Custom Feeds to their software.
(And have something to test again.)
@reiver i built on #fedialgo to make a customizable feed algorithm that is pretty much how i interact with #mastodon these days. it's available as an #npm package.
here's the demo app: https://github.com/michelcrypt4d4mus/fedialgo_demo_app_foryoufeed
this is what the demo app looks like:
Custom ("algorithmic") feeds for the Fediverse are being worked on.
See the #FediverseCustomFeeds hash-tag.
https://mastodon.social/@reiver/113668493283013849
https://mastodon.social/@reiver/113668169170211551
https://mastodon.social/@reiver/113429881149273852
.
I have been arguing similar — that the issue isn't that recommendation-engine based feeds are the problem — but that the problem is whose interests has it been designed to serve‽ — yours‽ or someone else's‽
A recommendation-engine that serves YOUR INTERESTS can be useful and desirable.
Creating a Fediverse Custom Feed —
From a programmer's POV, for creating a Fediverse Custom Feed —
The client-side app doesn't care how the content gets into a feed
I.e., it doesn't care what algorithm you did or didn't use to create a Fediverse Custom Feed
You (the program powering the Fediverse Custom Feed) provides content — and the client-side app displays it.
Just set Actor type="Feed".
4/
Fediverse Custom Feeds are a powerful technology!
And are one piece in creating a "plug-in" system for the Fediverse.
3/
The UI/UX part of a Fediverse Custom Feed is making apps understand what to do with a Actor type="Feed" actor.
For example — when the user "Follows" an Actor type="Feed" actor, then the app could make the content from that actor show up next to the home-feed, as an alternative feed.
2/
The Protocol part of a Fediverse Custom Feed is a new Actor Type — the "Feed".
We already have Actor Types:
• Application
• Group
• Organization
• Person
• Service
https://www.w3.org/TR/activitystreams-vocabulary/#actor-types
Add "Feed" to that list.
I don't always go on social-media.
But when I do I want Fediverse custom feeds.
Fediverse Custom Feeds
Let's make them exist!
Instead of having a single home-feed. You could have multiple feeds of your choosing.
For example—
Do you want a feed of just mutuals — you can do that with Fediverse Custom Feeds.
What about a feed showing just people you follow who do NOT post very often — you can do that with Fediverse Custom Feeds.
If fact, you can any kind of feed you can imagine.
I submitted a Talk Proposal for a talk at FOSDEM 2025 to the FOSDEM organizers.
I have given talks at many conferences. But this is the first time I have submitted anything to FOSDEM.
I will see if it gets accepted or not.
This talk (if accepted) would fall under the Social Web track:
https://fosdem.org/2025/schedule/track/social-web/
The FOSDEM Social Web track is focused on the Fediverse, ActivityPub, etc.
The Fediverse could have custom feeds.
Fediverse front-end client applications just need to add support for it.
(A custom feed could just be an actor that you can put along side the home-feed in the front-end UI.)