Today I learned that #PieFed has RSS feeds for at least Topics and Communities.
That community one is a hoot - PieFed, serving up a #NodeBB forum as an RSS feed. ActivityPub is bonkers.
https://piefed.social/topic/fediverse.rss
https://piefed.social/community/activitypub@community.nodebb.org/feed
@verge Thankfully, there is now the billiionaire-free decentralized #threadiverse: #Lemmy, #Mbin and #Piefed
What do you notice about the comments on this post?
https://piefed.social/post/555259
The post was made in the news@lemmy.world #Lemmy community and other posts linking to the same news article were made in technology@lemmy.world and in askusa@discuss.online. 3 different posts in 3 different communities.
#PieFed de-duplicates them and only shows the post once in your timeline and when viewing the post all the comments on those 3 posts are shown in the same list.
Fedi fragmentation = solved
Hi @andrew_s@piefed.social/@freamon and @nutomic@lemmy.ml —I'm working (not-so-secretly) on refactoring NodeBB so that it is able to "browse" remote audiences/group actors, and that would include things like PieFed and Lemmy communities.
N.B. Given varied nomenclature (group/category/community/subforum), the ForumWG calls this structure an "audience".
Where I am at now is working through the logic for slotting an object into a category.
The most obvious choice here would be to look at as:audience. It's even specified in 1b12, and the majority of threaded implementations follow 1b12.
I am making this post because nutomic explicitly removed the audience from being served in Lemmy (as of January this year), so I don't think relying on that property would be wise.
I asked in that issue whether Lemmy finds community via to/cc (it does). Does PieFed do the same?
Would this also open up the possibility of a topic/context being part of multiple audiences/communities? Interesting...
I’ve created #Piefed’s first dedicated community to movies!
If you’re on #Mastodon, #Akkoma, or #Sharkey, follow it here:
And if you’re on #Lemmy, #Mbin, or Piefed follow it here:
!movies@piefed.social
From now on, all my posts about movies, including reviews, will be posted there.
Everyone is welcome and you’re allowed to chat about whatever movie-related things you like. 
#PieFed just added a multi-reddit feature, which we're calling "Feeds". It combines multiple Communities (actors of type "Group" in ActivityPub) into one.
Feeds can be followed from other PieFed instances, which will subscribe the follower to all the communities in the feed.
Try it out at https://piefed.social/feeds
It's similar to PieFed's concept of a Topic https://piefed.social/topics, except topics are maintained by the instance admins. Feeds are crowdsourced and federated topics.
One thing that prevented me from jumping on the Lemmy bandwagon was the UI that I found underwhelming and a bit unpractical (and I'm someone who prefers the "old Reddit" UI and who doesn't mind the vanilla Mastodon).
That was until I discovered Piefed! Very similary to Lemmy (I assume it's a fork) but with a much nicer UI. It also has a great onboarding except for the part where it automatically signed me up to too many topics.
(thanks @atomicpoet@atomicpoet.org for putting it on my radar)
#Reddit #Lemmy #Piefed #Fediverse
Everything on this #Piefed community does not originate from Piefed:
https://piefed.social/c/lumoura
It originates from #Akkoma or #Pixelfed. Specifically, I’m sending posts that originate from @atomicpoet@atomicpoet.org and @atomicpoet@pixelfed.social to @lumoura@piefed.social.
Now why would I do this? Because I want to:
Yes, I believe this is a very big deal—which is why I talk so much about it.
Here’s screenshots of all four photo-based #Piefed communities I’m running.
Now if these posts look familiar, that’s because I’m posting them from #Akkoma and #Pixelfed – and they’re submitted to Piefed by tagging the relevant communities.
This is what I mean when I say that people on #Lemmy are seeing something drastically different from what you’re seeing on #Mastodon.
I’m leveraging Piefed for something incredibly neat.
You might notice that I’m tagging my photography posts with usernames. In fact, those are not usernames – they are #Piefed communities.
And to get the full effect of what I’m doing, it’s important to visit each individual community for the full aesthetic impact. So here’s the links:
@dustbloom@piefed.social: https://piefed.social/c/dustbloom@blue@piefed.social: https://piefed.social/c/blue@lumoura@piefed.social: https://piefed.social/c/lumoura@sizz@piefed.social: https://piefed.social/c/sizz@recordpics@piefed.social: https://piefed.social/c/recordpicsMore important is how I’m submitting content to those Piefed communities. From pixelfed.social and atomicpoet.org, I’m uploading photos from those two servers: pixelfed.social is my own artwork; atomicpoet.org is interesting art I stumble upon. After I upload a photo, I give it a description in a post, then tag it with the community “username” I want it to submit it towards.
Once the post is live, the originating server sends the post over to Piefed, and Piefed reposts it to the community I tag.
Voila! I now have submitted my post to an aesthetic and curated community, for which anyone can collaborate with me on.
Within a day, we got lots of activity here – and several people are already interacting with photos posted there.
Sizz is now on the Fediverse!
I’ve created @sizz, a new image-based #Piefed community that is an evolution of r/Sizz, a subreddit that I started back in 2017 and currently has 37K subscribers.
While other #Sizz communities exist on the Fediverse, this is the only one that I am involved with. Unlike the subreddit, this one will have relaxed rules for now – at least until there’s reasons to adjust them.
Enjoy! This will be bustling quite soon!
I wanted to see the current status of group actor support in #Mastodon.
This feature has been requested all the way back in 2016. It’s a feature request that is so old, it’s the 139th ticket. After it was made, @gargron stated shortly after:
I made a decision not to implement groups. They offer little benefit over a cost of added complexity, and the bangtag syntax personally irks me too.
A year later, he re-opened the feature request and said:
Reopening, but not high priority.
No further update since then. Nearly a decade after this feature had been requested, group support has not been added and it’s still not a high priority.
Now the intent of this post isn’t to wag my finger at Mastodon and say, “How dare they!” It’s clear that Mastodon is in a transitional state right now, and their focus is on other things – like quote posts and search.
But it is to say that the development of this feature is so completely out of Mastodon’s control that it now represents an opportunity loss for the platform. Because the truth is – whether or not Mastodon supports group actors – many Mastodon users are using it anyway even though this causes quite a few UI/UX problems along the way. Namely, the common Mastodon user cannot differentiate between a single user account and a group actor.
So now we have two groups of Mastodon users: those who want to make use of services like #Lemmy, #Piefed, #NodeBB, and those who are completely unaware of those services and ask, “Why the hell is Mastodon acting like this when I try to interact with that account?”
More to the point, group actors should be embraced because not only is this a valuable feature, but they’re also critical for community safety. No one can moderate a hashtag, but they can certainly moderate a Lemmy community.
Like I said, though, development of Mastodon is ongoing – whether Mastodon participates or not. And that specific element of the #Fediverse continues to grow, despite the fact that the most used Fediverse service (sans Threads) regards it as “low priority”. As long as Reddit and Facebook Groups users seek out an open, federated alternative, there will be demand for group actors.
Why am I saying all this? Because this is my plea for better interoperability. It is certainly within Mastodon’s right to be picky about what features they implement. However, the Fediverse would be plainly better if Mastodon finally supported this important ActivityPub standard.
I’ve created four new #Piefed photo-based communities. They are:
I’ll mostly be using these communities to post photos from #Akkoma and #Pixelfed. Not only will they categorize these photos in a coherent manner, they’ll be open for other contributors, and also be easy to moderate.
Why not use hashtags instead? Simple: anyone can use a hashtag and no one can moderate them. Which means they’re easy to spam.
For my purposes, groups are simply better.
PieFed mod tools - quick demo - no audio
Yep, you can post from a #Pixelfed account to a #Piefed community!
This is a big bloody deal to me, and I have lots of use cases for that ability!
Basically, this means my #Pixelfed account doesn’t have to be devoted to a single topic anymore! I can put all my images on one account and sort them according to community—which can also be used by others!
Here’s the original Pixelfed post:
https://pixelfed.social/p/atomicpoet/798415830074783205
Here’s how it exists on Piefed:
https://piefed.social/post/489174
And the screenshot is how it appears in the #Lemmy app @voyagerapp.
Nope, mentioning a #Lemmy group actor like @pcgaming@lemmy.ca does not result in my post appearing in that Lemmy community.
Other people have said that it’s possible to post to Lemmy from a microblogging platform, but every time I’ve tried, I haven’t been able to get it to happen.
So I may have to duplicate several Lemmy communities in #Piefed simply because it plays better with microblogging platforms like #Mastodon and #Akkoma.
RE: https://atomicpoet.org/objects/c76d141f-be15-4821-9ed0-2e88e56b43f5
