fediverse

#fedicat #fediverse support is made possible by admins running servers of various flavors (and interesting names) that I can test on, such as: wizard.casa, catodon.social, functional.cafe, gram.social, miraiverse.xyz, wienermobile.rentals, friendica.opensocial.space, plasmatrap.com, bytes.programming.dev, eggplant.place, and takahe.staging.django-cast.com

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.

#asdf #fediverse #Lemmy #piefed #threadverse

"Southwestern Sunrise" is my latest effort...hope you enjoy!

ART - https://peggy-collins.pixels.com/featured/southwestern-sunrise-peggy-collins.html

#southwest #newmexico #landscape #sunrise #colorful #art #arte #buyintoart #kunst #wallartforsale #wallart #artprints #artforsale #fineart #decor #gifts #giftideas #interiordesign #homedecor #contemporaryart #modernart #creativetoots #artbooster #fediverse #fedigiftshop #mastodonart #mastoart

ALT

My #FediforumFriday update this week is that I've been tinkering around at the MVP end of the fediverse, trying out projects like #snac (and also, honk). I really need to write some of these experiences down somewhere! Also, preparing for my talk at #FrOSCON next weekend.

What are you looking at that's interesting and #fediverse-related right now?

Just an occasional reminder that disabling replies is the #1 requested feature from Mastodon.

https://github.com/mastodon/mastodon/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc

(EDIT: Direct link, in case the above doesn't work for you: https://github.com/mastodon/mastodon/issues/8565)

Limiting who can reply is also worth giving a thumbs-up to, currently at #10.

https://github.com/mastodon/mastodon/issues/14762

#mastodon #fediverse #ReplyControls #SocialMedia #TrustAndSafety

The last #snac release fixes a problem with the Mastodon API. Now, apps (or webapps like Phanpy) properly work as the "inifite scrolling" has been fixed.
Thanks, @grunfink - this was one thing that kept some of my friends away from self-hosting with snac, and now I can help them to have their own digital home.

#Fediverse

A new release of TootSDK - 14.4.0 📣

https://github.com/TootSDK/TootSDK/releases/tag/14.4.0

What's changed:

- Add instance domain blocks and peers endpoints @dale_price

Community contributions are greatly appreciated 🙌

#iOSDev #Swift #TootSDK #Fediverse

I have to say I don't agree with @fediforum who consider #Bluesky part of the #fediverse. Is Bluesky making any attempts to interoperate with other fedi services that I'm not aware of?

ALT

As #Fedify's author, I'm contemplating its adoption beyond Ghost's #ActivityPub implementation. Finding potential users for ActivityPub tools seems challenging—perhaps I'm addressing a very niche need?

While the technical complexity of ActivityPub makes tools like Fedify valuable, I wonder about the actual market demand for federation outside specific communities.

Open, decentralized systems make sense to many developers, but businesses often prefer closed ecosystems that align with traditional models.

Still, I see potential as the #fediverse grows and digital sovereignty concerns increase. Fedify aims to lower the technical barriers to federation.

I'm curious: Which projects would benefit most from Fedify today? What would make federation compelling enough for platforms to implement?

Would appreciate perspectives from both developers and platform owners.

Fediforschung beginnt mit Dir!
Das Fediverse ist groß, bunt und manchmal ein bisschen rätselhaft. Doch das sollten wir nicht als Nachteil betrachten, sondern als spannende Herausforderung. Deshalb hat @digitalcourage ein kleines Mitmach-Abenteuer erstellt für alle, die das #Fediverse besser verstehen wollen: Denn Neugier ist der Anfang von Erkenntnis und Wissenslücken bieten Gelegenheit, etwas Neues zu lernen. Wir müssen nur wieder Lust entwickeln, Technik selbst zu begreifen und uns damit digital selbst zu behaupten. So gewinnen wir die Freiheit und Mündigkeit zurück, die uns Big Tech permanent abtrainieren will.
Auf der Seite
https://digitalcourage.de/fediforschung
findest Du kleine Aufgaben, Experimente und Beobachtungen, mit denen Du das freie, dezentrale und wirklich soziale Netzwerk Schritt für Schritt erkunden kannst.
Viel Spaß!

(Textgrundlage aus dem heutigen Newsletter von Digitalcourage.)

#Fediforschung #Fediverse #digitalcourage #Spiel #Rätsel #Abenteuer

We're now in Trakt migration 2.0.

The move by Trakt that triggered Trakt Migrtation 1.0 was understandable, they have to make money.

But in this latest move, messing with grandfathered accounts, no, not understandable.

You just don't mess with grandfathered accounts ever in any service. That's your way of saying, "Thank you for always being with us since the beginning".

My mobile network plan is a grandfathered account, and the network have been trying to get us to "upgrade" to a "better" plan. Ad that's to mention one such.

Even in gaming, grandfathered accounts are not touched ever. If they cancel, that's the only time things change. Why? Simple, the current contract/subscription ended. So, the next time the user subscribe, it will be under the current scheme.

In addition, owners of grandfathered accounts will do everything to keep it. They'll borrow money if it comes to that. You have grandfathered accounts that are paying you but the owners are rarely using it. Compare that to the owners cancelling their grandfathered accounts because it no longer has any value for them.

Just like right now. Many are cancelling because.

Time to move to #NeoDB or #SIMKL

Pick NeoDB if you want to be in the #Fediverse. Or, pick SIMKL if you want free "Pro" just by logging-in at least 20 days.

Both NeoDB and SIMKL combines various databases into one easy to use interface.

#Tracking #Shelf #Catalogue #Library

ALT

I just set up an easy to remember link for my #NeoDB shelf/catalogue/library account:

https://loomenji.youronly.one ( @youronlyone )

😁

It's in addition to the following:

* fediverse.youronly.one - @youronlyone
* atmosphere.youronly.one - @youronly.one
* gallery.youronly.one - @[email protected]
* wiki.youronly.one - youronlyone.tiddlyhost.com
* threads.youronly.one - @youronly.one.ofcl

If you have a personal domain name, use it for redirection (301 or 302). Easy to remember.

Another advantage, if you ever decide to move instances or change your accounts, you don't have to reprint business cards and update links everywhere, just change your redirect target setting. (It won't move your content of course.)

And if you're bridging to the #ATmosphere network, you can use your own domain as your handle for your #Fediverse network accounts (if supported by your bridging platform)!

Make use of your domain name! Redirect!

( #Loomenji #루멘지 #ルーメンジ #路明地 )

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

#fedidev

Do you run a public Fediverse server? Are you accepting new members? Would you like to be listed on https://fedi.garden?

If so, please DM me 🙂

(NOTE: All the servers listed have to be compatible with the seven points at https://fedi.garden/about-this-site)

#Fediverse

Hello to all 🤒🫂 I'm really pushing myself here lol but no worries just want to say Hi to everyone here in #Mastodon

Hoping u guys are doing well & safe..Thank you 4 all who wished 4 my speedy recovery💙 U guys are amazing!
I'm still battling this bad flu [this one's tough😤] Trust me I really want this 2 leave me,but Bad news #leptopsirosis is going rampant here & I had 2 get tested either tomorrow or next day..PLEASE PRAY 4 ME.

PS. Thank u Jonas K.💚

w/ love
yu.

#fediverse #flu

New: Taking Control of Your Timeline - in Different Ways

#Fediverse platforms as well as #Bluesky offer to give the user control of their timeline - in contrast with the control that Big Tech Platforms have with their algorithmic timelines.

But the approach is surprisingly different: fediverse platforms like Mastodon give you control over *how* you see the content you follow, whereas Bluesky gives you control over *what* content you see

https://fediversereport.com/taking-control-of-your-timeline-in-different-ways/

Hey fedi 👋🏻
I guess I'll take a break from fediverse and internet for 1 or 2 months. My real life got busy, I mean too busy 😔
I'm not leaving BTW. I'll come visit you guys when I get free time but won't be that active.
So take care and stay safe.
See you soon..
#fediverse

New: Why is Meta adding fediverse interoperability to Threads?

Threads' most recent update allows people on Threads to follow people on the #fediverse, albeit with some significant caveats.

But one simple question has bugging me for a long while: Why? Why is Meta adding interoperability to their platform?

https://fediversereport.com/why-is-meta-adding-fediverse-interoperability-to-threads/

Quite some tech journalists and "influencers" out there keep on telling us that #Mastodon (and the whole #fediverse, because they typically don't know that there is more than just one service ;) is losing users after the last wave of newcomers.

Weird thing is: I keep on getting more followers and my timeline is getting better and more diverse with a lot of inspiring content and respectful discussions.

So, I guess, smaller is better :) Thank you all for being awesome!

Mastodon Now Sends Referer Headers! Hurrah!

https://shkspr.mobi/blog/2024/12/mastodon-now-sends-referer-headers-hurrah/

Back in 2022, I wrote this rather grumpy post on Mastodon, the federated social media platform.

@[email protected] Eden

Mastodon enforces a "noreferrer" on all external links.

I have mixed feelings about that.

As a blogger, I want to see *where* visitors are coming from. I also like to see (and sometimes join in) with the conversations they're having.

But, I get that people want privacy and don't want to "leak" where they're visiting from.

Is it such a bad thing to tell a website "I was referred from this specific server"?

When you click on this link - https://www.bbc.co.uk/news - your browser says "Hey! BBC! Please can I have your /news page? BTW, I was referred here by shkspr.mobi. THANKS!" This is called the "Referer" and, yes, it is mispelt.

One the one hand, sending the referer is good; it lets the linked-to server know who is linking to it. That allows them to see where traffic is coming from. On the other hand, this could be bad for much the same reason.

If you run a server anarcho_terrorists.biz, you probably don't want the FBI knowing that your members are sharing links to their pages. If you run a small personal server, you may not want anyone knowing that you personally linked to them. If you run a server for a marginalised community, you may not want a hate-site to know your members are linking to you.

But if you're a large-ish, general purpose, non-private site - like Mastodon.social - where's the harm in allowing referer headers?

Anyway, for historic reasons, Mastodon blocked the referer header. This, I believe, was sensible for smaller servers but a miss-step for larger servers. As I pointed out last week:

@[email protected] Eden

Two years later.

Want to know one of the major reasons Mastodon didn't catch on with journalists and large website owners?

It is *invisible* in referrer statistics.

Here's my blog from the last month.

BlueSky now sends me more traffic than Bing.

How much traffic does Mastodon send? It is impossible to know due to the "noreferrer" header in all links.

(I'm not saying your privacy isn't important. But you can't grow a community if no-one knows you exist.)

I'm not the only one to make this point - it has been a popular complaint for some time.

A few days ago, Mastodon changed to allow this to be configurable.

This is excellent news. Website owners will be able to (somewhat) accurately see how much traffic Mastodon sends them. That way they can determine if there is a suitably large audience to engage with on the Fediverse.

It is, of course, slightly more complicated than that!

Instance owners can opt-in to allowing Referer headers (it is off by default).
The policy means that only the domain name is sent; not the full page.
Mastodon is federated and there are thousands of sites. Even if they all opted-in, their statistics will be fragmented.
Apps can set their own Referer header - leading to more fragmentation.
Even if they do opt-in, users can set their browsers not to send Referer headers.

Nevertheless, I'm delighted with this change. Hopefully it will allow the Fediverse to grow and attract more users.

#fediverse #http #mastodon