@ fedi (ツ) Some more suggestions:
CherryPick:
Kirschwasser, sake, melon soda, Pocari Sweat, matcha powder. Stirred with a fork for obvious reasons.
Hubzilla:
Yes. As in everything your bar has to offer.
Micro.blog:
Sorry, this cocktail is closed-source.
Lemmy:
Jack Daniel's, Coca-Cola. Surprised?
...okay: Russian Standard vodka, Havana Club rum, baijiu, tomato juice.
# FediMeta # FediverseMeta # CWFediMeta # CWFediverseMeta # CherryPick # Hubzilla # MicroBlog # Lemmy # Cocktail # Cocktails
It is still not possible to follow someone on #Mastodon (or elsewhere) from #Lemmy or #Piefed, right?
So no use of the WP-plugin #activitypub either. Is that correct?
🫧 socialcoding..
boosted
⁂ Article
My hypothesis on why Lemmy is rejecting valid activities
I have not been able to successfully post to a Lemmy instance either as a post or a comment. A cryptic error message is returned where the error is unknown and the message is a generic message:
{"error":"unknown","message":"data did not match any variant of untagged enum AnnouncableActivities"}From my logs, it seems this is happening:
- I make a valid ActivityPub request with the audience of a community (or cc a user).
- Lemmy makes an ActivityPub request back at me at
/. - My web site does not handle ActivityPub at
/, and responds with atext/plainerror message. This is default behavior in Drupal. - Lemm...
⁂ Article
My hypothesis on why Lemmy is rejecting valid activities
I have not been able to successfully post to a Lemmy instance either as a post or a comment. A cryptic error message is returned where the error is unknown and the message is a generic message:
{"error":"unknown","message":"data did not match any variant of untagged enum AnnouncableActivities"}From my logs, it seems this is happening:
- I make a valid ActivityPub request with the audience of a community (or cc a user).
- Lemmy makes an ActivityPub request back at me at
/. - My web site does not handle ActivityPub at
/, and responds with atext/plainerror message. This is default behavior in Drupal. - Lemm...
Ti piacciono i vecchi forum, ma vorresti che fossero collegati ai social network e ai blog? Ecco citiverse.it, la città dei social liberi e l’alternativa ai gruppi locali Facebook!
Abbiamo bisogno di un’alternativa ai gruppi Facebook per gli utenti italiani, in particolare i gruppi locali; ma non potendo competere con Meta, dobbiamo fare in modo che gli utenti del forum non siano da soli…
#Citiverse #citiverseIt #fedditIt #Forum #Friendica #informapirata #LeAlternative #Lemmy #Poliverso
4 media
Poliverso - notizie dal Fediverso ⁂
liked this activity
Ti piacciono i vecchi forum, ma vorresti che fossero collegati ai social network e ai blog? Ecco citiverse.it, la città dei social liberi e l’alternativa ai gruppi locali Facebook!
Abbiamo bisogno di un’alternativa ai gruppi Facebook per gli utenti italiani, in particolare i gruppi locali; ma non potendo competere con Meta, dobbiamo fare in modo che gli utenti del forum non siano da soli…
#Citiverse #citiverseIt #fedditIt #Forum #Friendica #informapirata #LeAlternative #Lemmy #Poliverso
4 media
Ti piacciono i vecchi forum, ma vorresti che fossero collegati ai social network e ai blog? Ecco citiverse.it, la città dei social liberi e l’alternativa ai gruppi locali Facebook!
Abbiamo bisogno di un’alternativa ai gruppi Facebook per gli utenti italiani, in particolare i gruppi locali; ma non potendo competere con Meta, dobbiamo fare in modo che gli utenti del forum non siano da soli…
#Citiverse #citiverseIt #fedditIt #Forum #Friendica #informapirata #LeAlternative #Lemmy #Poliverso
4 media
9 consigli per usare Lemmy (e feddit.it)
Feddit.it non è solo un’istanza locale, ma è anche diventato un servizio pubblico per tutti gli utenti italiani di tutte le istanze. Ecco qualche consiglio
https://www.informapirata.it/2025/06/10/9-consigli-per-usare-lemmy-e-feddit-it/
#Feddit #fedditIt #Friendica #LeAlternative #Lemmy #Mastodon #Pixelfed #RaccoonForLemmy
https://www.informapirata.it/2025/06/10/9-consigli-per-usare-lemmy-e-feddit-it/
2 media
wakest ⁂
boosted
How PieFed federates “flair” on posts and comments
On the surface flair on PieFed functions very similar to how it does on Reddit – on posts they’re community-specific tags that can be used to filter posts in a community. People can also add flair to themselves which is just a piece of text that appears next to their name whenever they make posts or comments in the community. This can be helpful for giving a hint about someone’s background, interests or expertise.
However PieFed is federated and there are copies of the communities on multiple servers (instances). The way to use ActivityPub to create and maintain those copies is described in FEP 1b12 which makes no mention of flair. I have made some minimal additions to that FEP, described below:
For flair on posts, the Lemmy devs have already done quite a bit of work on this, which I added a little to, so that flair can have colors. Community actors have an additional type of tag:
{
"type": "Group",
"id": "https://piefed.social/c/piefed_meta",
"name": "piefed_meta",
/* ... */
"lemmy:tagsForPosts": [
{
"type": "lemmy:CommunityTag",
"id": "https://piefed.socia1/c/piefed_meta/tag/whatever",
"display_name": "Some Post Tag Name",
"text_color": "#000000",
"background_color": "#dedede"
}
]
}lemmy:tagsForPosts is a list of lemmy:CommunityTag objects.
So now all the different copies of the community will know which flair can be used there. When creating a post in the community we just need to add one or more lemmy:CommunityTag objects to the Page activity:
{
"id": "https://piefed.social/post/1",
"actor": "https://piefed.social/u/rimu",
"type": "Page",
/* ... */
"tag": [
{
"type": "lemmy:CommunityTag",
"id": "https://piefed.social/c/piefed_meta/tag/whatever",
"display_name": "Some Post Tag Name"
},
{
"href": "https://piefed.social/post/1",
"name": "asdf",
"type": "Hashtag"
}
]
}In this example the post also has a #asdf hashtag on it.
User flair is simpler because it’s not managed by the community moderators and is not a fixed list. PieFed simply adds the author’s flair to every comment (federated as a Note activity) they make. When a Note is received the author’s flair is updated on the receiving instances.
{
"id": "https://piefed.social/comment/1",
"actor": "https://piefed.social/u/rimu",
"type": "Note",
/* ... */
"flair": "PieFed dev"
}This means that when someone changes their flair it will take effect immediately on their instance but until they write a comment it won’t propagate to other instances. As flair is primarily used on comments and the people using flair will tend to be posting a lot of comments this is kinda “good enough”.
It would be trivial to add a “flair” attribute onto posts too and have receiving instances read that. User flair shows up next to the author’s name on their posts so arguably it makes sense to send it then too.
Let’s see how it goes.
How PieFed federates “flair” on posts and comments
On the surface flair on PieFed functions very similar to how it does on Reddit – on posts they’re community-specific tags that can be used to filter posts in a community. People can also add flair to themselves which is just a piece of text that appears next to their name whenever they make posts or comments in the community. This can be helpful for giving a hint about someone’s background, interests or expertise.
However PieFed is federated and there are copies of the communities on multiple servers (instances). The way to use ActivityPub to create and maintain those copies is described in FEP 1b12 which makes no mention of flair. I have made some minimal additions to that FEP, described below:
For flair on posts, the Lemmy devs have already done quite a bit of work on this, which I added a little to, so that flair can have colors. Community actors have an additional type of tag:
{
"type": "Group",
"id": "https://piefed.social/c/piefed_meta",
"name": "piefed_meta",
/* ... */
"lemmy:tagsForPosts": [
{
"type": "lemmy:CommunityTag",
"id": "https://piefed.socia1/c/piefed_meta/tag/whatever",
"display_name": "Some Post Tag Name",
"text_color": "#000000",
"background_color": "#dedede"
}
]
}lemmy:tagsForPosts is a list of lemmy:CommunityTag objects.
So now all the different copies of the community will know which flair can be used there. When creating a post in the community we just need to add one or more lemmy:CommunityTag objects to the Page activity:
{
"id": "https://piefed.social/post/1",
"actor": "https://piefed.social/u/rimu",
"type": "Page",
/* ... */
"tag": [
{
"type": "lemmy:CommunityTag",
"id": "https://piefed.social/c/piefed_meta/tag/whatever",
"display_name": "Some Post Tag Name"
},
{
"href": "https://piefed.social/post/1",
"name": "asdf",
"type": "Hashtag"
}
]
}In this example the post also has a #asdf hashtag on it.
User flair is simpler because it’s not managed by the community moderators and is not a fixed list. PieFed simply adds the author’s flair to every comment (federated as a Note activity) they make. When a Note is received the author’s flair is updated on the receiving instances.
{
"id": "https://piefed.social/comment/1",
"actor": "https://piefed.social/u/rimu",
"type": "Note",
/* ... */
"flair": "PieFed dev"
}This means that when someone changes their flair it will take effect immediately on their instance but until they write a comment it won’t propagate to other instances. As flair is primarily used on comments and the people using flair will tend to be posting a lot of comments this is kinda “good enough”.
It would be trivial to add a “flair” attribute onto posts too and have receiving instances read that. User flair shows up next to the author’s name on their posts so arguably it makes sense to send it then too.
Let’s see how it goes.
⁂ Article
ActivityPub: The Good, the Bad and the Ugly
ActivityPub is the best protocol available for interoperable federated social media—primarily because no other current federated protocols target social media, offer interoperability, and aren't deprecated.
