
#PieFed 1.2 has just been released.
- Event posts
- 3D rotating tag cloud
- Built-in translation
- Set a reminder on any post/comment
- Log in with LDAP
- and so much more.
Details and links to examples at https://piefed.social/post/1278967
⁂ Article
Piefed community tags
Hi @rimu@piefed.social did Piefed.social update recently to include community tags? I recall this was announced awhile back but it only just started breaking on NodeBB.
"tag": [ { "background_color": "#99c1f1", "blur_images": null, "display_name": "Feature request", "id": "https://piefed.social/c/piefed_meta/tag/198", "text_color": "#000000", "type": "lemmy:CommunityTag" }, ... ]
I should point out that there's nothing wrong with the JSON.
PieFed v1.2 is released
PieFed 1.2 has just been released.
- Event posts
- 3D rotating tag cloud
- Built-in translation
- Set a reminder on any post/comment
- Log in with LDAP
- and so much more.
Details and links to examples at https://piefed.social/post/1278967
#PieFed 1.2 has just been released.
- Event posts
- 3D rotating tag cloud
- Built-in translation
- Set a reminder on any post/comment
- Log in with LDAP
- and so much more.
Details and links to examples at https://piefed.social/post/1278967

Fedinews: il "giornale" con le migliori notizie provenienti dal fediverso italiano
Vuoi leggere un flusso di notizie selezionato dagli utenti italiani del Fediverso?
Allora puoi provare ad aprire la pagina
di FediNews
E se vuoi pubblicare anche tu una notzia che ti sta particolarmente a cuore o che secondo dovrebbe essere presente su FediNews, allora puoi pubblicarla dal tuo account #Mastodon, #Friendica, #Pixelfed, #Lemmy, #Piefed, #Lemmy o #NodeBB!
Se hai un account del forumverso sarà sufficiente sottoscrivere le comunità di feddit.it e citiverse.it.
Se invece hai solo un account social come Mastodon, Pixelfed, #Pleroma o Friendica, allora ti basta menzionare la comunità che ti interessa
Fedinews: il "giornale" con le migliori notizie provenienti dal fediverso italiano
Vuoi leggere un flusso di notizie selezionato dagli utenti italiani del Fediverso?
Allora puoi provare ad aprire la pagina
di FediNews
E se vuoi pubblicare anche tu una notzia che ti sta particolarmente a cuore o che secondo dovrebbe essere presente su FediNews, allora puoi pubblicarla dal tuo account #Mastodon, #Friendica, #Pixelfed, #Lemmy, #Piefed, #Lemmy o #NodeBB!
Se hai un account del forumverso sarà sufficiente sottoscrivere le comunità di feddit.it e citiverse.it.
Se invece hai solo un account social come Mastodon, Pixelfed, #Pleroma o Friendica, allora ti basta menzionare la comunità che ti interessa

How to use Really Simple Licensing (RSL) to block all AI crawlers
RSL is a new initiative by a group of big internet publishers that seeks to define the conditions under which AI crawlers can harvest their content. Their guide describes the various ways the content can be made available, including for free or a paid royalty but only by digging deeper into their reference material was I able to figure out how to prohibit all usage.
Your robots.txt needs to link to a XML file, like this:
License: https://your-domain.tld/rsl.xml
Then in that file you want this:
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/" server="https://rslcollective.org/api"> <license> <prohibits type="usage">all</prohibits> </license> </content></rsl>
That’s it.
If you want to be more liberal you could change the <prohibits> line to
<permits type="usage">search</permits>
That will let them use the content for search, which is probably quite similar to what traditional search engines do. More details in their reference docs.
Optionally to dispel any plausible deniability you can also add a link to rsl.xml as a Link header in every HTTP response.
Link: <https://example.com/rsl.xml>; rel="license"; type="application/rsl+xml"
It’s still too early to say whether AI crawlers will respect the terms of the license any publishers specify, it’ll probably take a court case or two to sort that out.
PieFed has added RSL to it’s code just now. Instance admins who wish to disable RSL can set the ALLOW_AI_CRAWLERS environment variable to anything.
How to use Really Simple Licensing (RSL) to block all AI crawlers
RSL is a new initiative by a group of big internet publishers that seeks to define the conditions under which AI crawlers can harvest their content. Their guide describes the various ways the content can be made available, including for free or a paid royalty but only by digging deeper into their reference material was I able to figure out how to prohibit all usage.
Your robots.txt needs to link to a XML file, like this:
License: https://your-domain.tld/rsl.xml
Then in that file you want this:
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/" server="https://rslcollective.org/api"> <license> <prohibits type="usage">all</prohibits> </license> </content></rsl>
That’s it.
If you want to be more liberal you could change the <prohibits> line to
<permits type="usage">search</permits>
That will let them use the content for search, which is probably quite similar to what traditional search engines do. More details in their reference docs.
Optionally to dispel any plausible deniability you can also add a link to rsl.xml as a Link header in every HTTP response.
Link: <https://example.com/rsl.xml>; rel="license"; type="application/rsl+xml"
It’s still too early to say whether AI crawlers will respect the terms of the license any publishers specify, it’ll probably take a court case or two to sort that out.
PieFed has added RSL to it’s code just now. Instance admins who wish to disable RSL can set the ALLOW_AI_CRAWLERS environment variable to anything.

⁂ Article
Our fediverse conversations are gonna have the context they have been missing!
This past June, I put together a write-up about two major approaches to backfilling conversations. The ability to properly backfill conversations means we will be able to make major inroads toward solving the feeling that the fediverse is quiet.
I, alongside several other members of the SWICG Forums and Threaded Discussions Task Force (ForumWG) have been working toward building implementor support for Conversational Contexts — the ability to explicitly classify a set of objects as belonging to a conversation, whether that be a topic, reply tree, or similar.
I am happy to report that we have made some wonderful inroads this past few months!
- jesseplusplus@mastodon.social has been working closely with the Mastodon team to allow software to backfill from Mastodon — this pull request has now been approved!
- I have been working with both nutomic@lemmy.ml and rimu@piefed.social to allow software to backfill from Lemmy and Piefed, respectively. (Lemmy PR, Piefed issue)
This marks a major milestone in the adoption of conversational contexts. With Mastodon on board backfill will be possible with the majority of the microblogiverse. With Lemmy and Piefed on board, backfill will be possible with the majority of the threadiverse.
Remember that pfefferle@mastodon.social was an early adopter of conversational contexts, and we have been able to backfill from WordPress blogs for quite awhile now (so that's the blogiverse too)
I for one, am eagerly awaiting the next version of all of these softwares!!
When a crawler requests a page that is managed by an RSL license from your website, it must include a valid RSL License Token for the page in the HTTP header using the new proposed License RFC 7235 HTTP Authentication scheme.’
⁂ Article
Our fediverse conversations are gonna have the context they have been missing!
This past June, I put together a write-up about two major approaches to backfilling conversations. The ability to properly backfill conversations means we will be able to make major inroads toward solving the feeling that the fediverse is quiet.
I, alongside several other members of the SWICG Forums and Threaded Discussions Task Force (ForumWG) have been working toward building implementor support for Conversational Contexts — the ability to explicitly classify a set of objects as belonging to a conversation, whether that be a topic, reply tree, or similar.
I am happy to report that we have made some wonderful inroads this past few months!
- jesseplusplus@mastodon.social has been working closely with the Mastodon team to allow software to backfill from Mastodon — this pull request has now been approved!
- I have been working with both nutomic@lemmy.ml and rimu@piefed.social to allow software to backfill from Lemmy and Piefed, respectively. (Lemmy PR, Piefed issue)
This marks a major milestone in the adoption of conversational contexts. With Mastodon on board backfill will be possible with the majority of the microblogiverse. With Lemmy and Piefed on board, backfill will be possible with the majority of the threadiverse.
Remember that pfefferle@mastodon.social was an early adopter of conversational contexts, and we have been able to backfill from WordPress blogs for quite awhile now (so that's the blogiverse too)
I for one, am eagerly awaiting the next version of all of these softwares!!
The master list of PieFed instances is retrieved from the fediverse.observer API. Then an API endpoint on every instance in the list is queried to see if they opted in and to get information about the instance that fediverse.observer does not have.
This happens once per day.
Instance admins can choose to filter out any other instance and defederated ones are automatically filtered.

I'm hoping to maximize the dispersal of new user across all the instances so wanted to keep other options visible from the beginning.
Can't wait to roll this out more widely. A key part of it is that it's built-in to every #PieFed instance, not a separate web site. So it's power comes from everyone being on board.
I'm hoping to maximize the dispersal of new user across all the instances so wanted to keep other options visible from the beginning.
Can't wait to roll this out more widely. A key part of it is that it's built-in to every #PieFed instance, not a separate web site. So it's power comes from everyone being on board.
This web based onboarding UX for #Piefed is perilously close to my suggestion as to how to fix fediverse onboarding that I made back in June.
(IIt seems to lack round robin in place, but other than that, it has a simple, single main choice clearly featured UX placement, but with an offramp to a more complex wizard for those who want one)
cc: @rimu
https://www.timothychambers.net/2025/06/24/the-seven-deadly-fediverse-ux.html
Topic removal from a category/community
Hey @rimu@piefed.social question to you about post removal...
If a remote user posts to a local community, and the local mod deletes it (let's say it's spam of off topic), does the local community federate a delete out?
Technically you're not deleting the content, just removing it from the community.
Is there a different action Piefed takes?
Hey @rimu@piefed.social question to you about post removal...
If a remote user posts to a local community, and the local mod deletes it (let's say it's spam of off topic), does the local community federate a delete out?
Technically you're not deleting the content, just removing it from the community.
Is there a different action Piefed takes?
I'm really happy to see #PieFed doing so well, and third-party apps are picking up API support for it.
Support your Fedi Devs.

People complain that #Mastodon doesn’t integrate with non-Mastodon services. But that’s true of Twitter too—no one ever expected Instagram or Reddit inside Twitter.
The difference is Mastodon can do what Twitter never could. It talks to Instagram-like services such as #Pixelfed. It talks to Reddit-like services such as #Piefed. And Mastodon itself isn’t even Instagram-like or Reddit-like.
If that sounds confusing, that’s fair. It just means shifting your mental model of how the social web actually works.