Finally a new blog post about all our instances and the finances..

cross-posted from: https://toast.ooo/post/3740832

turns out I did my math wrong, so it’s a little less than 30 days

July 12th, 2024 @ midnight EDT

https://canvas.fediverse.events

✨ this year’s event also supports the entire fediverse not just Lemmy!

(you have to be able to make/receive text posts, like mastodon, lemmy, pixelfed, etc) (peertube accounts will not work)

you can get update announcements on other fedi platforms with @canvas@fediverse.events link

chat about Canvas on Matrix or Discord (they’re bridged)

Woo-hoo today's my cake-day on Lemmy.world.. actually I'm the first here but many will follow the next days. Happy cake day to you all!

Currently we have an images issue. Our Wasabi (S3) account was disabled because of some illegal content that was found, we're working with them to get the account re-enabled and the content removed.

[Update 20240308 14:47 UTC] The issue has been fixed.

There's some unrest because the Open Collective Foundation is stopping.

Don't worry, we use Open Collective Europe as a donations platform, they're going nowhere.

We've added some donation platforms, so if you would like to support us running our .world servers, you can do so here:

• Ko-Fi‬ (Preferred because of low fees)
• Liberapay
• PayPal
• Patreon
• OpenCollective
• Bunq

And for those wanting to donate crypto:

• Monero address: 83tnuFN4f28jRxTBW9qGDad2U23qNE5nfeW4Pfyd85oWMW7J9gqpXi3S8FDbX5uEeCAKcGnSpS2XT5dGwYiELthg8XuDrxH
• Cardano address: addr1v9qv6xvfwcx9ny56uag4umu6238sw2e7ff2kcxl3qe7p9esayjxgu

Thank you!

[Edit] Some of the links were broken, they should now all work! [Edit 20240314: Added Liberapay]

Next to Mastodon.world and Lemmy.world I am also running Calckey.world. This was running Calckey, a Misskey fork. That was re-branded to FireFish (that's the danger of running sites with the software name in the URL... :-) ).

Unfortunately due to circumstances the FireFish software will no longer be maintained. Therefore I was looking for another Misskey fork that could replace it, and I found Sharkey. This looks really nice.

So being who I am, I registered https://sharkey.world and installed it. It still needs some configuring and branding, but it works and you can use it! (As you will see it currently uses the Calckey.world branding)

I will write a brief how-to on migrating from Calckey to Sharkey and hope the calckey.world users will migrate.

I run a server https://calckey.world , which used to be CalcKey, but the software was re-branded to Firefish. Unfortunately, firefish.world is taken. What domain should I use for my new Firefish instance? Preferably a .world domain.

I have remembered these options suggested to me so far:

• dartfish.world (a sort of fish similar to the firefish)
• fedifish.world
• fire-fish.world
• f-fish.world

Any other suggestions? Or do you like one of the above?

I've written a short blog about what happened in August, and the finances.

I did it again.... started another Fediverse service, this time a Bookwyrm instance.

I used Goodreads, but if there's a Federated alternative, why not use that.. So I setup a server and opened registrations.

Enjoy, and please let me know if you find anything that can be improved or changed.

There was another attack going on (as you might have noticed). We're working on a fix. In the meantime, we've blocked the listing of comments, so we at least aren't down, but it did break comments.

Hope to have a fix in the next hour. Stay tuned!

Update OK we've implemented a fix, again many thanks to @sunaurus@lemm.ee for his assistance. This will prevent the outages we've seen last couple of days. Let's see what they will come up with next...

A few days ago I saw some cool JoinLemmy stickers created by @cheeseblintzes@lemmy.world . I asked her if she could also create lemmy.world stickers, and she did!

You can see and order them here, also check the other cool stickers in her shop.

Thanks for creating them!

Lemmy.world has been down between 02:00 UTC and 05:45 UTC. This was caused by the database spiking to 100% cpu (all 32 cores/64 threads!) due to inefficient queries been fired to the db very often.

I’ve collected the logs and we’ll be checking how to prevent this. (And what caused this)