Based on the server chart, there was a server lost that day (81 -> 80).
Whether that was a tracking change or an error, perhaps someone with more familiarity with Bookwyrm would know.
Based on the server chart, there was a server lost that day (81 -> 80).
Whether that was a tracking change or an error, perhaps someone with more familiarity with Bookwyrm would know.
The “Forkiverse” (theforkiverse.com) is a new mastodon instance that a tech(?) podcast setup and it’s been growing pretty quickly (~10k users in 1 month). Not sure of anything else going on though.
Edit: Podcast is called “Hard Fork”. Added link.
Haha. Yeah, the fediverse seems to have been doing quite well in the last month.


Something to keep in mind is these are the public numbers. The actual numbers may be significantly worse.
That’s a good point. I’d be curious to see the average user’s journey (# of usernames and instances) before they settle. Maybe someday someone will research and write an article about that.
Ah, sorry about that. I should have given better directions to the software graphs (originally took me a while to find them too).
Yeah, Lemmy fluctuates quite a bit from Reddit exodus waves to slow declines until the next wave. It would be nice if it was able to stabilize better between redditor migrations, but all the fediverse softwares seem to have similar wave patterns from what I’ve seen (migration wave -> decline). I think as the fediverse gets bigger and better integrated it’ll get ‘stickier’ and stabilize better between waves.
Welcome :)
I think multireddits (feeds?) are already implemented on the web, but the apps (I’m on Voyager) are quite far behind on implementing Piefed features (equivalent Lemmy features work, but not Piefed specific features like Events or Stack Overflow Q&A style posts).
Lemmy numbers look to have been taking a hit for like a year now (down ~15% in the last year). Though I think they’ll have a nice boost when version 1.0 releases sometime this year (potentially within the next couple months).
If you want to see some pretty nice looking graphs, the fediverse-observer website linked in the post has some good ones for daily stats and monthly stats (active users) for each of the fediverse softwares.
I think it’s probably a few things working together.
There may be more, but that’s all that’s coming to me at the moment.
Haha. Yeah, its a bit much. The graphical view on fediverse-observer is quite nice. Not sure why the numbers don’t match between the daily and monthly views though (perhaps something to investigate in the future).
I think its a combination of holidays and then political stuff that caused some migration from the reddit BuyEU and BuyCanadian subs to the fediverse.
My understanding is that Piefed is getting a much better reception with redditors than Lemmy, and that’s why the significantly greater percent growth compared to the larger Lemmy community.
Thanks for the link.
If I decide to make this a weekly or monthly thing I think I’ll try to incorporate another source.
Thanks for the catch (post fixed).
Yeah, definitely (edited post with the additions).
Thanks for catching that (edited post). Got sidetracked in the middle of making the post and forgot some pieces. Luckily people have been helpfully pointing them out, plus adding additional pieces.
Added the Threadiverse totals.
Agreed. I’m curious to see how big this new wave is going to be.


I would think so, but I’m not sure.
It may show up on today’s sheet. There’s often a day delay in the reporting.


I believe it’s dead, wounded, and captured, for personnel. Damaged, destroyed, and captured, for equipment.


The audit covered every public-facing component of Mullvad’s online presence, including the website, the Tor-only Onion service, the rsync setup, and the internal content management system (CMS). Each of these elements was examined for common attack vectors, misconfigurations, or any signs of hidden data collection.
I believe checking the “internal content management system (CMS)” is what they are using to say there were no logs.
They linked a more detailed report in the article, but I didn’t look at it. It may contain something different than my takeaway from the article.
Yeah, that is weird. I guess we’d have to dig into the code to see how or why that happened.