@carlcolglazier It's sometimes a bit slow. But I just tested it and it's still up for me.

My first explorations of the Fediverse started in 2017 and again in 2018 with a data-centric account, but like many others, I lost interest and my accounts were dormant for years. With the announcement that Elon Musk is trying to buy Twitter many people started to post in the Fediverse (again). I updated some of my things like MastoVue, a tool to look at the local timelines of Mastodon instances and search for hashtags, and the visualization of Fediverse instances.

As another experiment, I made this blog subscribeable in the Fedivery by adding the ActivityPub protocol. If you search for @luca@lucahammer.com with your Fediverse account, you can subscribe to it and get the full posts directly in your Fediverse client. (To be honest, I am not sure if it works as intended because old posts aren’t fetched, so I need to write this post to test it.)

The whole process was super easy thanks to the wonderful activitypub-plugin by Pfefferle. Just search for it in your WordPress backend, install it, activate it and you are done. After activating the plugin, you can search for @username@domain.tld and subscribe. In the plugin settings, I changed the shortlink at the end of the entry to a full link, but that’s not necessary.

This blog showed the error “503 remote SSL certificate could not be verified” the first time I tried to search for it and later no error message but still didn’t show it. The issue was my SEO plugin YOAST, where the author archives were deactivated. After changing that setting, it worked.

For debugging I used the webfinger discovery tool, which showed me the link to the author profile. When I visited it, I was redirected to the homepage and knew that something was wrong. That the SEO plugin was the issue was a guess, but I don’t use many plugins. The next step would have been to deactivate plugins one by one.

Search for @luca@lucahammer.com with your fediverse account and let me know if it works.


I fixed mastovue.glitch.me which allows you to peek into the local timeline of other instances. (if the instances allows it)

@oblomov I was able to fix it by using a specific version of the JS.

With the new wave of users and @Luca working again on a #Fediverse visualization, this reminded me that I wanted to discuss a brief exploration of the #network I did some months ago.
In 2018, some researchers took a screenshot of Mastodon instances, I wanted to check how these evolved after 4 years.
I also tried to get a more global picture of the network to see how the different platforms interact.

So I'll talk about how many instances died (and other stuff) in a short thread. ⬇️

That's it for today. Next time, I want to integrate this wonderful script by @tfardet and add more information about each instance and remove or mark the dead ones.


Let me know, if you are interested in something specific.

Show thread

If you want to look for an instance yourself, here is a searchable SVG. It's 12 MB and may crash your browser. And you have to use the browser search or scroll a lot to find anything. lucahammer.com/projects/fedive

Show thread

I removed those nodes (which are all dead anyways).

Let's look at the different areas of the big hairball at the bottom.

Left side in blue, seems to be dominated by friendica instances.

Below them in black are the biggest Mastodon instances like mastodon.social and chaos.social.

Bottom right in orange sound Japanese.

Not sure what the top ones in green have in common. They got many incoming peers as well, but no common theme.

Show thread

@tfardet I tested some of them and they were all dead. beehub returned them as peers.

What's that pink cluster at the top? 31 998 gab[.]best instances. Or just domains? I assume they tried that to circumvent instance level blocks.

The only instance they are connected to? beehub.

(I wasn't involved with the Fediverse for some years. Feel free to explain what's going on.)

Show thread

New day, new try.

as of 2022-04-29.

I found 61 266 instances and 6 217 452 connections (peers). This includes non-functional ones because my script can't differentiate them yet.

1 455 returned info about the instance, 2 547 returned peers. That's an indication for the number of active instances which support the v1 API.

Show thread

@RyunoKi @ColinTheMathmo @artagnon I only used the API endpoints without authentication. No experience yet with authentication and Mastodon.

@spielundzeug Im Vergleich zu 2018. Wie viele Instanzen gibt es, wie sind sie miteinander verbunden, gibt es Cluster, wie viele funktionieren nicht mehr. Sowas.

@oblomov Thanks for letting me know.

That shouldn't happen, but I didn't touch the code in four years. Not sure when I will be able to fix it.

@knoerer @LeaRichter Zugleich gibt es die Möglichkeit Instanzen auszuschließen, wo dies nicht der Fall ist, was verhindert, dass man globale Regeln wie bei Twitter braucht, die für alle gleich gelten.

@knoerer @LeaRichter Auf Mastodon ist jede Instanz strukturell bedingt eine Gemeinschaft, deren Haltung stark von den ersten Teilnehmer:innen bestimmt wird, aber auch später noch durch die Moderation. Da einzelne Instanzen immer kleiner sind als Gesamttwitter, können sich spezifische Regeln und Moderationspraktiken entwickeln, die dafür sorgen, dass der Austausch besser funktioniert.

@knoerer @LeaRichter Ja, innerhalb von Gemeinschaften (auch wenn sie lose sind) gibt es meist wenige Angriffe, weil diese normalerweise eine soziale Ächtung nach sich ziehen. Ausnahmen sehe ich bei "holier than thou", wo man Menschen auf in der Gemeinschaft etablierte Regeln hinweist, und in der Gemeinschaft kontroverse Themen, da diese hitziger Verlaufen können und man durch die Plattformstruktur, auch einmal Menschen etwas an den Kopf wirft, die bisher nicht beteiligt waren.

Show older

vis.social is an open social platform for creative people, especially anyone in SciArt, SciComm, data, visualization, creative coding, and related arts and research. English is the common language of the instance.