Search results

Another small step in Forgejo federation.

Getting Forgejo and mastodon services to talk had some unexpected pitfalls.
Mastodon only federates on port 443 for example, that means Forgejo needs to be able to listen on a privileged port even for testing. You can imagine the troubles setting up our e2e tests properly.

This is finally behind us and were now aiming to integrate the test into the automated test suite (with a lot of work already done by @famfo)

Excerpt of a mastodon log, it shows a successful connection attempt against a forgejo instance running on the https port.
0
0
0

One of the powerful things about the Fediverse and Social Web is that people can follow you from anywhere!

People from the same server you are on.

But also people from other servers can follow you.

Should the ability for people on other servers to follow you be OFF by default?

And, only people on the same server you are on can follow you by default?

0
0
0

It’s not finished. It’s not perfect. But it’s real. 🥹

Loops is now open, built in public, and growing every day — laying the groundwork for a future where you can build your own TikTok.

A future where governments can’t censor you. Where corporations can’t control the conversation. Where the social web belongs to the people again.

This is how it starts. ✊

joinloops.org/

0
0
1
0
0
0

A 🧵on the ongoing project - which is designed to enable along with of all types of libraries, especially , and even

You can find more info at meansofp.org/, and the codebase is at meansofp.org/.

We have a discord at discord.gg/DxUrwhDg - but also moving lots of the discussion here to !

0
0
0

¡Hola a todos! 👋🏻

Nuestro servidor de Loops, (Loops.one) ya federa con el Fediverso desde la última actualización. 🎉🎉

Podéis buscar vuestros perfiles (por ejemplo el mío es @trankten@loops.one) y los posts directamente desde cualquier software compatible con ActivityPub. :onepiece_luffy:

💡¡Algunas cosas aún están en pruebas y podrían no funcionar correctamente, así que por favor, cualquier bug no dudéis en avisar!

:Loops: Welcome to Loops. Welcome to Fedi..Loops 😎

⛓️‍💥 loops.one

  • Trankten :tkz:

Logo de Loops.one con el fondo blanco y un texto indicando "Federación Activada"
0
0
0
0
0

🧵1of2 aren't just "not ready yet." They're devices by design.

@Em0nM4stodonEm :official_verified: called Meta's Ray-Ban glasses exactly what they are: voyeurism tools.

The keeps reviewing them like consumer gadgets instead of acknowledging the harm potential.

Here's what's actually happening when these become mainstream:
1. Recording people without clear consent indicators.
2. Facial recognition in public spaces.
3. Data harvesting from every interaction.
4. Stalkers and harassers getting military-grade surveillance capabilities.

The community understands something Big Tech pretends not to: Technology isn't neutral. Design choices reflect values.

When Meta builds glasses that can secretly record, they're not solving problems.

They're creating new ones for the most vulnerable people.

Women, trans folks, activists, and marginalized communities already navigate constant surveillance and harassment.

Smart glasses amplify existing power imbalances in dangerous ways.

🧵2of2 This is why building ethical alternatives matters.

The exists because we refused to accept that surveillance capitalism was inevitable.

We chose over centralization.

over corporate control.

We need the same approach for

Hardware that clearly indicates when it's recording. Software that keeps data local. Designs that prioritize consent over convenience.

The question isn't whether this technology will exist. It's who gets to control how it works.

Meta's approach serves advertisers and data brokers. A community-driven approach would serve actual human safety and dignity.

My framework: Technology should expand human agency, not reduce it.

When surveillance tools are marketed as consumer convenience, we have a responsibility to call out the real consequences for vulnerable people.

What's your take? How do we build wearable tech that serves community safety instead of corporate surveillance?

0
0
0

I've been busy wrapping up the final parts of Loops ActivityPub federation!

We will ship with two modes (Open and Lockdown), the latter allowing you to restrict federation with allowed instances only (and enforced via AuthorizedFetch)

You can also disable Federation support

I'll have a better ETA this weekend after some more testing ✨

Thanks to phpstan, this may even ship this weekend 🚀

Loops Admin Dashboard Federation SettingsLoops Admin Dashboard Federation SettingsLoops Admin Dashboard Federation SettingsLoops Admin Dashboard Federation Settings
0
1
0
0
0
0
0
0

🐛 GTS-HolMirDas v1.2.1 Released - Important Bugfixes

Fixed some critical issues that prevented the RSS-based content discovery from working properly. Thanks for sharing, @christianteqqy

🔧 What's Fixed:

  • Inline Comment Support: Fixed parsing of RSS feeds file when using inline comments
  • Control Character Error: Resolved "URL can't contain control characters" error caused by comments in same line as URLs
  • RSS File Parsing: Comments after # are now properly stripped from URLs
https://mastodon.social/tags/homelab.rss    # 20 posts default
https://fosstodon.org/tags/docker.rss?limit=50   # 50 posts

📦 Update Instructions:

# Download latest version
wget https://git.klein.ruhr/matthias/gts-holmirdas/raw/v1.2.1/gts_holmirdas.py

# Restart your container
docker compose restart gts-holmirdas

#GoToSocial #RSS #ContentDiscovery #SelfHosting #OpenSource #Federation #Homelab #Docker

0
0

Why on earth was the #ActivityPub protocol even let out the door without a well-specified and mandatory graceful, non-destructive key rotation scheme?

Yes I know the privacy issues. Those are not valid reasons to not have such a mechanism; it's a valid reason to not enable or use one.

What we're stuck with now is a ton of instances with absurdly long, legacy-algorithm keys (RSA-4096) with no way to replace them with shorter/better keys without effectively losing everything ever posted on the instance.

The protocol is only 7 years old! EC crypto was well-established at the time, and should have been the default.

And what happens once everyone has to replace the keys, because RSA is broken by quantum computers (I know, probably 100 years to go)? The #Fediverse will be a wasteland, with no instances trusting anything from any other instance, so all #Federation breaks down.

Sorry if I got some details wrong about what the protocol says. If I get flamed to death for being wrong, then I'll consider that a Good Thing(TM). I've been trying to find a way to rotate/replace keys for a while and all my searching turns up is either 1) confirmation that most people don't know or care about cryptography, or 2) https://socialhub.activitypub.rocks/t/key-rotation-notification/562 - which really isn't helpful.

If it is possible to gracefully rotate the key(s) of an instance/user, there really has to exist some documentation that explains clearly how to implement this in a server and how to exercise it as a server operator.

#Cryptography #Rant #Mastodon

0
0

Concept for discussion: Replacing HTTP Signatures with Bearer Tokens for ActivityPub Federation

Curious what other people think about this idea. What if federation security was re-worked to use target-assigned
bearer tokens to authenticate GET/POST requests? This would remove the need for complicated signing schemes and reduce system load under heavy traffic bursts (as no cryptography is required).

A basic implementation could look like this:
1. When instance A (
a.example.com) first attempts to federate with instance B (b.example.com), a POST request is made to a dedicated registration endpoint. (for discussion, we'll say it's https://b.example.com/activity-pub/register-instance). This request includes fields necessary for verification, including the source domain name, target domain name, and a securely-generated verification token. Other metadata could be included to allow instance B to selectively allow/prohibit federation based on other criteria, but this is optional.
2. Instance B makes a POST request back to a dedicated verification endpoint on instance A (for discussion, we'll say it's
https://a.example.com/activity-pub/verify-registration). This request must include the target domain name and verification token provided in step 2.
3. Instance A checks the verification token (and verify that it matches the target domain name) and return a successful value.
The verification code must be invalidated after this call!
4. Instance B, after verifying instance A's request, returns a securely-generated
federation key back to instance A. This federation key is a bearer token used to authenticate all requests from instance A to instance B. This key must be unique to instance A!
5. Instance A completes the original request with the
Authorization header set to Bearer {federation_key}.
6. Instance B receives the request, detects the federation key, and checks it against the list of registered instances.
7. If the key does not exist or A has been defederated, then a
403 Forbidden error is returned.
8. If the key is expired or revoked, then
401 Unauthorized error is returned. Upon receiving a 401 error, instance A should start over from step 1 to re-authenticate and complete the request with a new token. This process should not be repeated for recursive failures!
9. If the key is approved, then a
200 OK response or 202 Accepted response is returned, and A can consider the request as successful.

Advantages versus HTTP Signatures:
- No cryptography requirements.
- Simple logic, no edge cases around HTTP query parameters or header order.
- Equally effective for all request types.
- Keys can be easily revoked or rotated.
- Supports authorized fetch and defederation use cases "by default".

Disadvantages versus HTTP Signatures:
- Breaks the actor model - instances are required as a first-class concept. (but really, the actor model is basically dead already. you can't even federate reliably without a WebFinger server, at minimum.)
- Requires multi-request "handshake" before communication. (but this is already required in practice, since a signature can't be validated without first requesting the signing actor.)
- Out-of-band protocol - communication can't happen over ActivityPub / ActivityStreams because this is a prerequisite to authenticate any request. (but again, we already require WebFinger and some software requires NodeInfo for full support.)

So, what are your thoughts? Good idea? Bad idea? Did I miss something? Please let me know, I welcome replies here!

0

Socialhome v0.22.0 released, with a completely new UI!

This is a massive milestone for the #Socialhome project, one that could not have been possible without the hard work of @alain@jase.socialAlain St-Denis. If you have followed the Socialhome project, you'll know that Alain has been responsible for most of the development of project in the recent years. This includes rewriting the #federation library to ensure #ActivityPub support is first class. More recently Alain has taken the challenge of rewriting the frontend, which has fallen into a rather poor state over the years.

The new UI work is actually a coordination of two people working many years apart. Way back years ago @lightone@mastodon.xyzlostinlight made some UI designs for a new Socialhome UI (thank you! <3). While the designs were not implemented for years, they were not forgotten. In 2023 Alain jumped to the challenge and started the full UI rewrite of the Socialhome frontend. This UI has now matured into a state that it is good for daily usage - which is the main focus of this release!

Currently, a Socialhome installation will still default to the old UI. If you do want to try out the new UI for example on socialhome.network, go to the account settings and toggle the "New UI" flag. Going back is also easy, should the new UI cause unforeseen issues (please do report!).

If you are a server admin, see the new UI installation instructions for how to add the new UI to your instance.

This is not all! The releases of v0.21.0 and v0.22.0 also contain a bunch of other changes and fixes. Most notably;

  • ActivityPub profiles are now richer, including bio and a larger picture, in addition to an avatar.
  • Many new API's to support the new UI, including session authentication, search, media upload, content fetching over uuid, profile organize and profile settings.
  • Whoosh has been replaced with Xapian as a search index backend.

See the full changelogs. Additionally, the federation library has received a ton of changes and fixes which can be found here.

Also, last but not least, we moved from GitLab to Codeberg. Check out the new repositories.

Installing and updating

We recommend using the Docker images (amd64/arm64).

Notes on how to use the Docker images can be found in the docs.

What is Socialhome?

Socialhome is best described as a federated personal profile with social networking functionality. Users can create rich content using Markdown. All content can be pinned to the user profile and all content will federate to contacts in the federated social web. Federation happens using the ActivityPub and Diaspora protocols.

Please check the official site for more information about features. Naturally, the official site is a Socialhome profile itself.

Try Socialhome?

If you want to try Socialhome first before trying to install it, register at https://socialhome.network and then ping us with a comment on the user name chosen to get the account approved. You can also request account approval in the chat room. This unfortunately approval step is due to spammers.

Contribute

Do you want to work on a Django and VueJS powered social network server? Join in the fun! We have easy to follow development environment setup documentation and a friendly chat room for questions.

#socialhome #federation #fediverse #activitypub #diaspora #django #vuejs

0

12.0.0 was just released!

Learn about it in detail in the blog post:
forgejo.org/2025-07-release-v1

We recommend that all installations are upgraded to the latest version.

Check out the release notes and download it at forgejo.org/releases/. If you experience any issues with this release, please report to codeberg.org/forgejo/forgejo/i.

@forgejo My personal highlight of this release: You can now use your handle in documents and it will be marked up as a link to your user profile (or group, etc.).
forgejo.org/2025-07-release-v1
I'm excited about the future, when mentioning fediverse handles will actually be federated and will send notifications everywhere!

0
0
0
0
0
0
0

Meine Deutsch-palestinischen Freunde (ich wusste nicht dass ich so viele habe) wechseln gerade alle zu upscrolled.com/, mit dem Versprechen freisprechen zu können. Ich mache mir Sorgen, dass sie nur in die nächste Falle laufen. Vielleicht kann man sie überreden, dass sie wenigstens Activity Pub einbinden.
-------------------------
My German-Palestinian friends (I didn't know I had so many) are all switching to upscrolled.com/, with the promise of being able to make free calls. I'm worried they're just walking into the next trap. Maybe we can persuade them to at least integrate Activity Pub.
--------------------------
أصدقائي الألمان الفلسطينيون (لم أكن أعلم أن لدي الكثير منهم) ينتقلون جميعًا إلى upscrolled.com/، مع وعد بإمكانية التحدث مجانًا. أنا قلق من أنهم يقعون في الفخ التالي. ربما يمكن إقناعهم على الأقل بدمج Activity Pub

0
0
0
0
0
0
0
0
0
0
0
0
0

If you are new here,

I've compiled this list of posts I wrote with tips for newcomers. I hope these can be helpful to you! Welcome! 🐘✨

Profile Page 👤
infosec.exchange/@Em0nM4stodon

Mastodon Features :mastodon:
infosec.exchange/@Em0nM4stodon

Content Warnings ⚠️
infosec.exchange/@Em0nM4stodon

Alt-Text 📝
infosec.exchange/@Em0nM4stodon

Filters 🚫
infosec.exchange/@Em0nM4stodon

Lists 🗂
infosec.exchange/@Em0nM4stodon

Culture :ablobsmile:
infosec.exchange/@Em0nM4stodon

Fediverse :geodesic:
infosec.exchange/@Em0nM4stodon

Questions ❓
infosec.exchange/@Em0nM4stodon

More Resources 👇

‣ Browse this hashtag to see more of my tips:

‣ Browse this hashtag to see more Mastodon and Fediverse tips:

‣ Follow this great account for regular Mastodon tips in your timeline: @FediTips

0

5/

So, not just Decentralized Social (DeSo), but instead —

Decentralized Social (DeSo), Federated Social (FeSo), Localized Social (LoSo)

The goal is 'social' that is simultaneously — 'Decentralized', 'Federated', and 'Localized', all at the same time.

RE: mastodon.social/@reiver/114551

0
0
0
0
0
0
0
0

If you’re having trouble visualising the power differentials designed into federated systems, think of this scenario:

You have an instance of 1 person. An instance of 1 million people decides to block your instance.

What have they done?

They’ve blocked 1 million people from interacting with you.

Now let’s reverse the scenario: You, with your instance of 1, decide to block an instance of 1 million.

What have you done?

You’ve blocked 1 million people from interacting with you.

0

We've got exciting news! We're federating more of the quality publishers we work with, so you can follow everything from news and tech to fashion and music across the UK, France, Spain, Italy, Germany and Brazil on the open social web!

Read more about it here: about.flipboard.com/fediverse/

If you're curious, here's our full list of federated accounts:
docs.google.com/spreadsheets/d

These are some of our UK publishers now available.

90min—the online leader in global football: @90min

British Vogue—fashion, beauty & celeb news, backstage photos, catwalk videos & supermodel interviews: @BritishVogue

The Evening Standard—London's award-winning newspaper: @EveningStandardThe Evening Standard

T3—gorgeous tech. Smarter living: @T3dotcomT3

What Hi-Fi?—The most trusted tech reviews in the world: @WhatHiFiWhat Hi-Fi?

0
0

At SXSW's Fediverse House, it didn't matter which platform or protocol you preferred — everyone was focused on the singular goal of building a better internet. We've uploaded videos and highlights of key conversations from the event and rounded them up in one post. Here you go:

about.flipboard.com/fediverse/

0

Congratulations to @johnonolanJohn O'Nolan and the team at Ghost on their 12th birthday! Here's John's post reflecting on the idea behind the product, some of the incredible indie publishers who have adopted it (including @404mediaco404 Media, @caseynewton's Platformer, and @drownedinsoundSean | Drowned in Sound) and what's next.

john.onolan.org/12/

1
0
0
0