kate! ΘΔ

@shuppy@fedi.shuppy.org but if you wanna do that after you migrate (or in a new repo), then update the issue_index table where the group_id matches your repository id (in the DB) to set max_value as one number less from what you want your starting issue index to be (idk if you can do this in the FE. see 3rd and 4th screenshot for code. forgejo code is the same)

yay!!! finally updated dariox.club to the latest version of mastodon v4.5 :3

mmmmmmmmmmmmmmmmm, so many containers,,,,,,,,,,,,,,,,,,,

RE: https://floss.social/@kde/116487444734779958 HOLY SHIT I HAD NO IDEA THAT KDE HAS A FEMALE MASCOT and we have the same name!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

relay.dariox.club will be down for about 5hr since there's a power outage for my entire suburb THANKS WESTERN POWER!!!!!

im using light mode on rider. does anyone wanna put me down?

I've had 3 or 4 Mastodon accounts made today on my instance all with the same reason and similar usernames. Anyone else experiencing this? The join reason is always "Automated protocol deliverability probe"

@shuppy@fedi.shuppy.org issue numbers are preserved when migrating from github to a gitea fork. (the code is the same in forgejo, see screenshot 1 & 2) just make sure that you select "issues" when migrating to a gitea fork (see 3rd screenshot)

@shuppy@fedi.shuppy.org oh fun lol

@shuppy@fedi.shuppy.org ohhhhhhh so that's why the server upgrade took longer than expected

@mjdxp@labyrinth.zone sadly it happens often :(