Luca Hammer @Luca@vis.social

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.

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.)

New day, new try.

#Fediverse 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.

Just discovered the great project https://www.fediverse.space/, which was inspired by one of my older works. It's an interactive network of the #Fediverse and calculates the edges based on mentions between instances. Currently it contains 2445 instances.

/via @anneroth @sozialwelten

So many error codes. I think I should add that info as well to see if certain parts of the fediverse are broken. (In the past the visualization didn't care if an instance existed or not. Only if another instance listed it as a peer.)

You can now search for #Hashtags with #mastoview and choosing if you want to get only results from one instance or its federated results.

https://mastovue.glitch.me/

#mastodon #search #tools #mastovue

Rebuilt #MastoView with #vuejs and added a Toots per user table.

New URL: https://mastovue.glitch.me/ #mastovue

I started to work on #Mastoview.

Quickly peek into instances.

https://mastoview.glitch.me/

Updated version of the Interactive
Mastodon Hashtag Network.

Warning: 10MB. Desktop computer recommended.

https://lucahammer.at/vis/fediverse/2018-08-30-mastoverse_hashtags/

#mastoverse

- 761 of 2044 instances responded (api/v1/timelines/public?local=true)
- Up to 4k Toots per instance
- 231 510 #hashtags
- 42 900 different hashtags

#Pleroma seems to properly mark hashtags in the text, but not add them in the appropriate field of the API.

(Filed a bug report moments ago. It's not a big problem, but probably easy to fix.)

Most different #hashtags

https://mastodon.beerfactory.org 147
https://mastodon.bida.im 131
https://social.logilab.org 125
https://mastoton.fi 101
https://mastodon.etalab.gouv.fr 98
https://switter.at 93
https://smusi.ch 90
https://vapers.jp 87
https://campaign.openworlds.info 79
https://mastodon.greenpeace.ch 76
https://occitanie.social 75
https://toot.koeln 73
https://photog.social 72
https://norden.social 65
https://post.lurk.org 65
https://status.pointless.one 64
https://humanities.one 64

Clicking on a #hashtag shows the instances it was recently used on.

Clicking on a instance shows the hashtags that were recently used there.

Interactive Mastodon Hashtag Network: https://lucahammer.at/vis/fediverse/2018-08-29-mastoverse_hashtags/

You can search for hashtags and instances.

Core of the hashtag network. Instances are white with fixed size, hashtags colored and size by number of uses.

Most used #hashtags in the collected Toots:
#mastodon 2 825
#nowplaying 2 130
#drawing 1733
#qanon 1356
#気象警報注意報 1283
#vape 1154
#vegan 1067
#funkwhale 966
#introductions 785
#openstreetmap 760
#電子タバコ 753
#photography 722
#fediverse 618

Network visualization: Mastodon Instances - Hashtags

- 2 284 #Mastodon instances from https://fediverse.network/mastodon
- 2 000 public Toots (API) per instance
- Hashtags of those Toots

#mastoverse #hashtags #gephi #dataviz

#Mastoverse #Hashtags #WIP

Small improvement to #mastoviz:
You can now select accounts and see their network within your network.

https://mastoviz.glitch.me/

While I didn't think about mobile use, sigmaJS works nicely on touchscreens. I assume it will quickly become unusable if you follow many people. (Hiding edges helps a lot with performance.)

I narrowed the scope to read:account and read:follows.

Thanks for the feedback @BoF@mstdn.fr and @Gargron.

(The tool has no backend. All secrets and tokens are stored locally. You can copy the code and run it locally if you want to.)