fo0bar ✅ is a user on You can follow them or interact with them if you have an account anywhere in the fediverse.

fo0bar ✅

fo0bar ✅ boosted
fo0bar ✅ boosted

#Mastodon v2.2.0 is out:

✅ Pretty templates for all e-mails
✅ Welcome e-mails
✅ Improved digest e-mails
✅ Fixed home timeline bugs for returning users
✅ Number of follow requests displayed in a badge
✅ And more!

Upgraded to mastodon 2.2.0 release

Mastodon 1.4.x tagged releases just surpassed the 50% mark of the installed and tracked server base.

The latest tagged release 1.4.4 is also the most installed 1.4.x version in the mastodon-verse ranking 2nd behind unversioned <1.3 releases.

Full hourly updated visualisations can be found at raw data by

The Twitterrific for Mac: Project Phoenix Beta is available to backers!

Jemand in meiner Timeline Interesse an einem Boosted Board V2 Dual+ mit Extended Battery? Soll Ende Juni ankommen (Extended Battery später).

@TheKinrar Any chance to get a version distribution graph on the instances overview? This would show adoption rates.

Updated mastodon instance to v1.3.3

Upgraded instance to tagged release v1.3.1 of tootsuite/mastodon - my ultraconservative Content Security Policy on the server still causes errors for boost buttons - well I know that I just need to click that empty space to boost (:

fo0bar ✅ boosted

Welcoming GNUSocial to the fediverse!

(I'm kidding, of course, I know you guys were here first)

The scraper still needs some work (some GS instances use an infinite scroller page which can mess with it). Overall, though, I'm making progress.

Upgraded instance to v1.2.2

fo0bar ✅ boosted

I don't understand Japanese, so I can't verify if it's all correct, but this diagram explaining Mastodon is *adorable*

fo0bar ✅ boosted

The trouble with following an xkcd RSS bot on a GNUSocial instance is that if I don't understand the comic completely, there's no explainxkcd for it yet.

fo0bar ✅ boosted

dungeonfs, a game you play by navigating a pseudo-filesystem

Okay, streaming container suddenly dies, and wont bind to port 4000 again.

Okay, now problems with the streaming container - websockets returning 502 *argh*

Seesh, upgraded instance to tag v1.2 and then had asset problems. Rebuilt assets, still had assets problems. Deleted assets, recreated assets, still had assets problems (this time 404). Finally trashed web container and had it rebuilt, and all is good again.

@nickfarr ah, my instance lied to me, showing only me as a follower (: please ignore my previous toot (: instance needs to keep up w/ the stuff (: