cross-posted from: https://lemmy.blahaj.zone/post/25042034

This post is "FYI only" for blahaj lemmy members. It is not a debate, and is not intended for non blahaj lemmy users to weigh in and offer opinions.

I recently received reports of a feddit.uk user espousing transphobia. Specifically, this was a feddit.uk user refusing to use the word cis, repeating the "adult human female" dog whistle, and claiming that trans women are not women. I approached a member of the feddit.uk admin team and raised my concerns and sought clarification of their stance on posts like this, where the transphobia is mostly dogwhistles, and "civil disagreement" on the validity of trans folk.

I was told by the feddit.uk admin that their preferred response is this kind of transphobia is to "sort it out through discussion and voting". However, the comments in question are currently more upvoted than downvoted, and little "sorting out" has occurred. The posts remain in place.

At this point, the admin stopped responding to my messages despite being active elsewhere on lemmy. When it became clear they were ignoring my messages and had no intention of removing the posts in question, I made the decision to defederate the instance.

I know some folk agree with the feddit.uk admins approach of pushback through discussion and voting, but this instance is not designed to be that kind of space. Blahaj lemmy is meant to be a place where we can avoid the rampant transphobia universally visible on nearly every other social media platform, and where we can exist without needing to debate our right to do so.

Hi,

I would like to compare our moderation options in the various software of the fediverse. But i can't achieve it alone, so i need admins and moderators help.

Can you list all admin and moderation option for each software in comment ? So, later we can do a nice table that will show us what the fediverse is missing :3

And let's share about what feature do you miss ? How do you desescalate ? Do you try to explain to users ?

🧮 Decentralization Scoring System (v1.2)

This scoring system evaluates how decentralized and self-hostable a platform is, based on four core metrics.

📊 Scoring Metrics (Total: 100 Points)

📋 Example Breakdown (Estimates)

📧 Email

• Top Provider User Share: Google ≈ 17% → Score: 27/30
• Top Provider Content Share: Google likely handles ≈ 17% of mail → Score: 27/30
• Self-Hosting: Server: Easy (Can leverage hundreds email hosting services) → Score: 16/20
• Self-Hosting: Client: Easy (Thunderbird, K-9, etc.) → Score: 18/20

Total: 88/100

🐹 Lemmy

• Top Provider User Share: lemmy.world ≈ 37.17% → Score: 12/30
• Top Provider Content Share: lemmy.world likely hosts ~37% content → Score: 12/30
• Self-Hosting: Server: Easy (Docker, low resource) → Score: 18/20
• Self-Hosting: Client: Good FOSS apps, web UI → Score: 18/20

Total: 60/100

🐘 Mastodon

• Top Provider User Share: mastodon.social ≈ 42.7% → Score: 11/30
• Top Provider Content Share: mastodon.social ≈ 45–50% content → Score: 10/30
• Self-Hosting: Server: Docker setup, moderate difficulty → Score: 15/20
• Self-Hosting: Client: Strong ecosystem (Tusky, web, etc.) → Score: 19/20

Total: 55/100

🟣 PeerTube

• Top Provider User Share: Framatube (~17%) → Score: 27/30
• Top Provider Content Share: Estimated around 20% → Score: 25/30
• Self-Hosting: Server: Docker, active community, moderate resources → Score: 16/20
• Self-Hosting: Client: Web-first UI, FOSS, some mobile options → Score: 18/20

Total: 68/100

🖼 Pixelfed

• Top Provider User Share: pixelfed.social ≈ 23% → Score: 24/30
• Top Provider Content Share: Estimated around 30% → Score: 21/30
• Self-Hosting: Server: Laravel-based, Docker available, some config needed → Score: 15/20
• Self-Hosting: Client: Web UI, FOSS, mobile apps in progress → Score: 18/20

Total: 63/100

🔵 Bluesky

• Top Provider User Share: bsky.social ≈ ~90%+ (very centralized) → Score: 0/30
• Top Provider Content Share: Nearly all content on bsky.social → Score: 0/30
• Self-Hosting: Server: PDS hosting possible but very niche → Score: 4/20
• Self-Hosting: Client: Mostly official client; some 3rd party → Score: 10/20

Total: 14/100

🟠 Reddit

• Top Provider User Share: Reddit hosts all user accounts = 100% → Score: 0/30
• Top Provider Content Share: Reddit hosts all user-generated content → Score: 0/30
• Self-Hosting: Server: Not self-hostable (proprietary platform) → Score: 0/20
• Self-Hosting: Client: Some unofficial clients available → Score: 3/20

Total: 3/100

How Scores are Calculated

🧑‍🤝‍🧑 How User/Content Share Scores Work

This measures how many users are on the largest provider (or instance).

• 100% (one provider): If one provider has all the users, it gets 0 points.
• No provider > 10%: If no provider has more than 10%, it gets full 30 points.
• Between 10% and 80%: Anything in between is scored on a linear scale.
• > 80%: If a provider has more than 80%, it gets 0 points.

📊 Formula:

Score = 30 × (1 - (TopProviderShare - 10) / 70)
…but only if TopProviderShare is between 10% and 80%.
If below 10%, full 30. If above 80%, zero.

📌 Example:

If one provider has 40% of all users:
→ Score = 30 × (1 - (40 - 10) / 70) = 30 × (1 - 0.43) = 17.1 points

🖥️ How Ease of Self-Hosting Scores Work

These scores measure how easy it is for individuals or communities to run their own servers or use clients.

This looks at how technically easy it is to run your own backend (e.g., email server, Mastodon server) or User Interface (e.g., web-interface or mobile-app)

• Very Easy: One-command, low resources, great documentation → 18–20 points
• Moderate: Docker or manual setup, some config, active community support → 13–17 points
• Hard: Complex setup, needs regular updates or custom config (e.g. DNS, spam) → 6–12 points
• Very Hard or Proprietary: Little to no self-hosting support, undocumented → 0–5 points

📚 Sources

//TODO This is very much still a work in progress, so it likely still contains mistakes and the example data isn't yet retreived from reliable sources. I'm working on that. If you want to help provide sources please do.

This is saved on GitHub, https://github.com/NoBadDays/decentralization-score/blob/main/decentralization_score_2025.04.md

If you have ideas or thoughts on how this can be improved, let me know

A page dedicated to the Nomadic(portable) identity in the Fediverse. If you are on Mbin/Friendica/Mastodon or other software that allows you to follow users you can follow the official @nomad account for updates

It is not really a fediverse feature but i enjoyed a lot discovering it. :)

One advantage of nomadic identity is that it is probably the best existing way of moving your identity from one server to another. Unlike projects based on ActivityPub, it doesn't create a dumb copy or partial copy of your account on another server and leave the original behind as a usually dead account. It actually moves the content without leaving anything behind, and it moves all the content.

So let's suppose [email protected] wants to move to bar.social. The process goes like this:

• Create a new account on bar.social (unless Alice already has one there).
• Upload the whole [email protected] channel to the new account on bar.social. This can be done either by having bar.social download it from foo.social or by manually downloading the channel from foo.social to a file and then manually uploading this file to bar.social; the latter has been experienced to be more reliable.
• Change the identity of the channel which is still [email protected] at this point to [email protected].
• Have all contacts on servers that understand nomadic identity change their connections with [email protected] to [email protected]. Hubzilla and (streams) users will only notice the move because the ID has changed, but everything will work the same after the move.
• Delete the old instance of the channel on foo.social.
• If the account on foo.social has no more channels, delete the account on foo.social.

Afterwards, at least on Hubzilla, all non-nomadic contacts, for example on Mastodon, have to be manually notified of the move. They are one-sided at this point, i.e. they are followed, but not followers. So all followers have to manually follow [email protected] after the move.

When a community needs to move to another instance, it can be a rocky process.

It doesn't need to be, though - as long as someone on your instance has been a part of the community for a while your instance will already have quite a lot of the content from the old community. All we need to do is change our record of which instance the community belongs to and that's what PieFed's new 'Move community' feature does. Check out the video for a quick demo.

The full process is:

1. Ensure the copy of the community on this instance has been active long enough to receive a decent amount of posts. The move process will not copy posts so having an account on this instance subscribed to it for a while is the only way to get old posts here.

2. Lock the old community to by setting it to 'moderators only' so no one else can post in it.

3. Create a post in the old community announcing the impending move to piefed.social. Paste the url of that post into the field below.

4. Submit the 'move community' form (there is a link in the sidebar of every remote community) to send the request to piefed.social admins.

5. piefed.social admins will review your request, turn this community into a local one and contact you.

6. Update your announcement post in the old community to encourage people to join the new community at
   [email protected].

publication croisée depuis : https://rblind.com/post/3476242

As part of OurBlind's continued efforts to provide accessible online spaces for the blind and visually impaired community, we've developed custom themes for Lemmy, to use on our Lemmy instance on Rblind, and to make available for others, in keeping with the themes' license terms and the spirit of free and open source software.

If you're reading this on www.rblind.com and are not signed in, you're using RBlind-Dark. We hope you're enjoying it! If you log in, you can switch to RBlind-Light. Once logged in, go to your username, then Settings and, use the Themes dropdown to make your selection: we suggest RBlind-Dark or RBlind-Light at the end of the list.

Why these themes matter to us

We started this Lemmy instance back in 2023, prompted by the Reddit API protests. Reddit Inc., the company that controls the website our community r/Blind is on, had announced policy changes that made the apps most of us used to participate in the Reddit community impossible to maintain. During this time it became clear to us and many other online communities that a corporate-owned platform would always be subject to pressures that are contrary to our needs. We launched this site as our blind-friendly home base in the fediverse, a decentralized and often self-hosted social media platform.

The goal of having our own home server was always to be able to make our own decisions about the software we run on it. One of those decisions is that the visual styling should always be comfortable for low-vision users and other disabled people, as part of our core audience. That meant designing and providing themes that, within our technical limitations, conform to the Web Content Accessibility Guidelines (WCAG).

How we designed our Lemmy themes

OurBlind admins contracted Travis, a talented graphic designer from within the community, for this project. Check out his website here. Together we went over specific requirenments within WCAG and the site's usage, colors, layout, preliminary testing, and communication, to develop both the themes themselves and the framework for future work and sharing.

How these themes meet our goals

In short, the new themes ensure high contrast, colorblind friendly colors, readable fonts, and appropriately-sized and readable buttons and links.

Following are examples of the home feed using the new themes.

RBlind-Dark example

RBlind-Light example

Time for testing and feedback

These have been audited by OurBlind admins, but that's only part of the validation process. If you're using this site and have low vision, colorblindness, a cognitive or a motor disability, consider providing feedback. Do they work well given your needs and use case? Do you like them? Does something not work quite right? Comment below or fill out the anonymous survey. Don't hesitate to comment if you're not a member of this instance or not disabled - we want these to be helpful to as many people as possible. Thank you!

We'll be collecting feedback and open to revisions until February 1st 2025. Even after that, we'll still be interested in your experience, but will take longer to respond and adjust.

How to use these themes on your own instance

As mentioned, this project is all about the value of free and open source software in ensuring control and autonomy. We're making this our home in the fediverse and we want to be good neighbors. We already offer the broader community a place for discussions around blindness, but we also want to contribute back.

These themes are licensed under GNU AFFERO General Public License and available at the Codeberg repo to be used or modified. Updates to the themes that come as a result of user feedback will be available there. Definitely give Travis a star and consider hiring for your own design needs, he's been a delight to work with.

The repo is also mirrored on GitHub for accessibility reasons.

Thanks, from RBlind

This community's journey has been long and thrilling, across three platforms and over a decade. Everybody on the admin and moderation team has deeply benefitted from and grown with the community. These themes are a humble gift to our members and our neighbors on the fediverse. May they make all our lives that bit more comfortable.

Written Version: https://fedihost.co/blog/slug/migrating-to-gotosocial-from-mastodon

GoToSocial

If you've ever used something like Twitter or Tumblr (or even Myspace!) GoToSocial will probably feel familiar to you.

You can follow people and have followers, you make posts which people can favourite and reply to and share, and you scroll through posts from people you follow using a timeline.

You can write long posts or short posts, or just post images, it's up to you.

You can also, of course, block people or otherwise limit interactions that you don't want by posting just to your friends.

Mastodon & GoToSocial

Mastodon is great! If you want a full-featured ActivityPub microblogging server with all the bells and whistles, go use that instead :)

GoToSocial's niche is small or single-user instances running on low-powered devices, like single-board computers or old laptops repurposed as home servers.

Our focus is on providing lightweight software which is simple to install and maintain, and has good security and sensible defaults out of the box.

The system requirements are right here

Other GoToSocial features are here.

Migration Mastodon to GoToSocial

One of the coolest things about GoToSocial is support for the Mastodon move command.

Allowing you to migrate a Mastodon account to and from GoToSocial. We're going to go through how to do a migration today with version 18.3 of GoToSocial.

Create A GoToSocial Instance: https://fedihost.co/pricing

Limitations

There are a few limitations to migration and things you should know about a migration first.

Things You Can Migrate

• Followers - Automatically
• Bookmarks - CSV Download/Upload
• Follows - CSV Download/Upload
• Lists - CSV Download/Upload
• Mutes - CSV Download/Upload
• Blocks - CSV Download/Upload
• Domain Blocks - CSV Download/Upload
• Hashtags - Manual Data Entry

Things You Can’t Easily Move

At this point your posts and media cannot easily be migrated. If you are on someone else's mastodon server or one of the large public instances like mastodon.social you cannot migrate your posts.

If this is important to you there is a tool and you are comfortable with command line tools there is a tool called slurp which effectively recreates your posts and media on your new instance.

Portability If you like GoToSocial it is better to move onto an instance and domain that you have some control over sooner rather than later. One advantage of this is a fully portable account

A thorough review of trials, tribulations, and tests to bridge the gap from publishing online to federated social networking.

So, you're captivated by the fediverse—the decentralized social web powered by protocols like ActivityPub. Maybe you're dreaming of building the next great federated app, a unique space connected to Mastodon, Lemmy, Pixelfed, and more. The temptation to dive deep and implement ActivityPub yourself, from the ground up, is strong. Total control, right? Understanding every byte? Sounds cool!

But hold on a sec. Before you embark on that epic quest, let's talk reality. Implementing ActivityPub correctly isn't just one task; it's like juggling several complex standards while riding a unicycle… blindfolded. It’s hard.

That's where Fedify comes in. It's a TypeScript framework designed to handle the gnarliest parts of ActivityPub development, letting you focus on what makes your app special, not reinventing the federation wheel.

This post will break down the common headaches of DIY ActivityPub implementation and show how Fedify acts as the super-powered pain reliever, starting with the very foundation of how data is represented.
[...]

cross-posted from: https://dubvee.org/post/3151231

Bugfixes

• [a84bc5db] Add community-banned indicator to vote view if banned_from_community is present in the API response.

• [1e5bfeae] Disable actions if banned from community (all actions the API forbids if user is community banned):

  • Post/comment vote buttons
  • Edit post/comment
  • Delete/Restore post/comment
  • Report post/comment
  • Moderation buttons (if a mod is banned but not removed from mod team, they'll still see mod action buttons but be unable to perform any)
  • Create post, subscribe, and "community settings" buttons in /c/community and community modal

• [0216bc2a] Don't cache getCommunity lookup results. While nice in theory, it prevents being aware you've been banned or any changes to the community during the cache validity window with no way to automatically invalidate beyond a fixed TTL.

• [d4df7d05] Don't badge-ify post and comment links. That worked well until people would link entire paragraphs. :sigh: So they're regular links now, but they still open up in modals.

• [ac8db3d] Bring community mod team management section up to current API spec

  • "Top Mod" can now transfer community
  • Added confirmation dialogs when removing a mod or transferring a community.
  • Made "transfer community" button icon less ambiguous

• [564980d9] Selecting "browse communities" from the /instances list was still using the old URL param for the instance rather than the new route param.

New Features

User Purge [Admin]

Admins can now ues the user profile menus/modals to purge users.

Inline Comment Removal Reason

Notes:

• This only works if you are viewing a post on your home instance. Otherwise, the "Removed by Mod" text won't be linked to the modlog, and the removal reason will not be present.
• This feature is disabled by default. To enable, go to Settings -> Posts and Comments -> Show Inline Comment Removal Reasons

If a comment has been removed by a mod, it is now linked to the modlog. Additionally, Tesseract can attempt to lookup the comment in the modlog and display the removal reason.

Additionally, if you are a mod, it will show you the comment content that was removed. Have to pull this from the modlog along with the reason (so if that lookup fails, this won't work either). Hiding removed comments from mods is yet another big-brain move by the Lemmy devs that I have to cleanup client-side.

Changes

User Profile Share Button + Support for LemShare

The "Share" button on user profiles is now a menu, and I got rid of the separate buttons for "Lemmyverse Link" and "Actor ID". Added support for Lemshare. Now, clicking "Share" button in user profiles will open a menu with the following options:

• Lemmyverse Link
• Lemshare Link
• Threadiverse Link
• Actor ID
• Local Link (Local to your instance)

Misc

• On main feed, when expanding "Site Info" or "Legal" panels in the sidebar, add a mini site card (logo + name) at the top.
• Limit post flairs to 25 characters before truncating; add title tooltip with full flair text
• Removed the +/- quick (un)subscribe buttons from post/comment community icons since the community modal makes subscribing/unsubscribing easy and these are no longer necessary.
• Removed red background on removed comments. Looks okay on a single comment, but once you have to break up a slapfight, it's just too much.

Tags

• ghcr.io/asimons04/tesseract:1.4.34
• ghcr.io/asimons04/tesseract:v1.4.34
• ghcr.io/asimons04/tesseract:latest

Nice feature :)

At https://piefed.social/user/settings you can now choose who is allowed to PM you.

The default value is "This instance" which will cut you off from PMs from all other instances. We're currently dealing with a bit of gore spam but once a more long-term solution is found a more relaxed default should be possible.

• context: https://lemmy.dbzer0.com/post/40460535
• https://grafana.lem.rocks/d/bdid38k9p0t1cf/federation-health-single-instance-overview?orgId=1&var-instance=lemmy.world&var-remote_instance=aussie.zone&from=now-2d&to=now

Source: https://fedidb.org/software/lemmy?version=0.19.11

Dont render images in private message (#3043)

https://join-lemmy.org/news/2025-04-08_-_Lemmy_Release_v0.19.11