Piefed has feeds now!
-
While the actor is a
Group
and you can follow it, no posts areAnnounced
. All the federation of posts is still driven by the individual communities within the feed. You'll need to modify Lemmy to add the logic of subscribing to the constituent communities when you receive anAccept
.Also there are
Add
andRemove
activities sent out whenever the feed owner manages the list of communities within which would need to be handled.Documentation still to come...
Ah its more complicated than I thought. We also have a similar or same feature on the roadmap, when I get to that it can federate with Piefed.
-
Reminder that Piefed's patreon is only at $18 a month. If you have the means, consider donating to the project to say thanks for all of the work and effort being put into it
To anyone not wanting to give on Patreon, there is also: https://liberapay.com/PieFed/
-
Feeds are a combination of communities into one, like multireddit or mastodon tags.
Try it out!
So do I understand correctly that these are identical to Topics, except customizable without requiring backend changes?
Sweet!
-
Neat, it federates. Seems to work similar to a normal community, so it should be easy to follow these feeds from Lemmy.
That's cool, i hope lemmy federates with it in the future
-
The feed creator needs to know about the communities so they can type/paste the community address in, yeah. This feature takes the expert fediverse landscape knowledge contained in the heads of the terminally online and makes it available to more casual/new users.
Once a community is known to an instance it is available via the search feature. Thus this really doesn't improve discoverability at all assuming the person adding it to the feed is already using the instance.
What it however does is moving the conscious choice of looking for and joining a community to an opaque follow feed button that makes someone subscribe to a lot of communities they know nothing about other than that someone else thought they somehow fit to a single word tag (and it is worse than hashtags on Mastodon as it is not the person making the post that adds them, but a totally unrelated 3rd party).
-
c/all is worse imo and with feeds you will at least have control over picking topics you're interested in unlike c/all. We should be focusing on opting out from c/all more as it causes far more damage and it's been that way for a long time unlike feeds on such a small platform that just got the feature implemented.
Also the opt-in would be a great way to KILL the entire feature that's been the most hyped up and requested feature across the entire threadiverse. BRUH
Imagine having all communities opted out from c/all by default. That would be stupid and make everything hard to access.
Opt-out on the other hand for public feeds specifically is something that I support. But then good luck having that supported on lemmy where almost all communities exist.
Opt-out on the other hand for public feeds specifically is something that I support. But then good luck having that supported on lemmy where almost all communities exist.
Lemmy already has a setting
community.hidden
so that communities dont show up on the All feed. But this is not easy to access at the moment. I can fix that. -
So do I understand correctly that these are identical to Topics, except customizable without requiring backend changes?
Sweet!
Exactly
-
Opt-out on the other hand for public feeds specifically is something that I support. But then good luck having that supported on lemmy where almost all communities exist.
Lemmy already has a setting
community.hidden
so that communities dont show up on the All feed. But this is not easy to access at the moment. I can fix that.Oooooooh, love u.
-
Opt-out on the other hand for public feeds specifically is something that I support. But then good luck having that supported on lemmy where almost all communities exist.
Lemmy already has a setting
community.hidden
so that communities dont show up on the All feed. But this is not easy to access at the moment. I can fix that.Yes having that option more easily accessible would be much apprechated.
-
Yes the All feed has the same problem, but posts need to be significantly more popular for them to even register in the All feed. Thus most small communities currently fly under the radar of the All feed, and if they do get a popular post it nearly always becomes a moderation nightmare.
Hashtags on Mastodon have a similar problem, having given rise to the usually dreaded "Reply guy" issue.
I think most people on Lemmy haven't really thought this through and what the implications of such a feature are once it becomes widely used.
And no, the one that is doing the opt-in is the person creating the feed without asking the community that is being forcefully opted-in. Giving them the option to veto that is better than having them realize that they have been opted into something they don't agree with by being flooded with trolls and off-topic comments.
I appreciate your words of caution. Remember this feature is very new and will no doubt get a lot more finesse added in future. There's no point building some baroque all singing-all-dancing perfect thing unless we're sure people will use it and by releasing earlier we get valuable feedback which determines whether we continue building that feature at all, etc.
-
PieFed (and the Lemmy apps Sync and Connect iirc) can already do this, by blocking all users from the instance. It works much better than the Lemmy equivalent that would be better named as a community muting, since it still allows users to troll you in communities located on other instances.
I don’t want to block the users though, I just don’t want to be subject to their authority. Which means I can’t use their communities. Combining them into one big bag subverts my autonomy to do so.
-
I don’t want to block the users though, I just don’t want to be subject to their authority. Which means I can’t use their communities. Combining them into one big bag subverts my autonomy to do so.
??????????????
Just don't use public feeds and have your own private feeds split into topics you're interested in where you don't have communities you dislike included. You have all the autonomy you need. No one tells you to subscribe to that one specific feed that doesn't curate the communities in the way you dislike. Just use it to organise your own subscriptions to have them by topics or catered for different moods of the day.
-
Feeds are a combination of communities into one, like multireddit or mastodon tags.
Try it out!
Does posting to a feed post to all the communities in it?
-
Does posting to a feed post to all the communities in it?
Feed isn't a place you can post to. It just collects posts from different communities into one feed/stream.
-
Yes the All feed has the same problem, but posts need to be significantly more popular for them to even register in the All feed. Thus most small communities currently fly under the radar of the All feed, and if they do get a popular post it nearly always becomes a moderation nightmare.
Hashtags on Mastodon have a similar problem, having given rise to the usually dreaded "Reply guy" issue.
I think most people on Lemmy haven't really thought this through and what the implications of such a feature are once it becomes widely used.
And no, the one that is doing the opt-in is the person creating the feed without asking the community that is being forcefully opted-in. Giving them the option to veto that is better than having them realize that they have been opted into something they don't agree with by being flooded with trolls and off-topic comments.
Im still confused on what your worry is? That people will reply to a post without reading the comments?
-
Ah its more complicated than I thought. We also have a similar or same feature on the roadmap, when I get to that it can federate with Piefed.
For the federating its a new kind of AP actor. I'll be putting in a FEP for it in the near future, but its basically a "Group" that only cares about the "Following" collection.
You can see example json for the AP interactions here: https://codeberg.org/rimu/pyfedi/src/branch/main/docs/activitypub_examples/feeds
The AP interactions for a Feed are:
- Send a Follow request for a Feed
- Accept a Follow request (this is automatic for public feeds)
- Reject a Follow request (this is automatic for private feeds)
- Announce an Add of a Community to a Feed
- Announce a Remove of a Community from a Feed
- Send a Delete of a Feed to subscribers
-
Im still confused on what your worry is? That people will reply to a post without reading the comments?
No, the problem is that people that have no relation to the community start commenting and getting into arguments.
Say for example a /c/anarchism gets added to a "politics" feed. And suddenly you have a bunch of people that have no clue (or even a pretty false idea) commenting on posts in the anarchism community because they think it is just another politics posts. Then others that are actual members of that community start getting into largely off-topic arguments with these commenters and when moderators step in you shortly after get complaints from people about being "censored for their totally valid opinion about politics" and so on.
-
Im still confused on what your worry is? That people will reply to a post without reading the comments?
More like reply to posts without regard for its host community. In other words, context collapse where the community is the main context.
-
More like reply to posts without regard for its host community. In other words, context collapse where the community is the main context.
Wouldnt each post still indicate what community its on though?
-
This doesn’t appeal to me at all. The whole point of Lemmy is that I can avoid certain instances that have oppressive admins.
The whole point of lemmy is decentralization. Not being run off by bad mods. I agree that a lot of big instances have rude admins and mods but this idea is for similar communities with similar modding. If the mods agree then what’s the issue? A lot of big instances communities have the exact same mods anyways.
An example for my use case is I want to support slrpnk and post on their selfhosting com but I don’t want only 1 answer. Federating my post to all three big selfhosting communities would allow more interaction while still being decentralized in the sense of not instance dependent.