Posts
83
Following
179
Followers
23
moved to @shellbyte@florp.social

@badeline can we stop normalizing all software being fucking massive

0
0
0
hey can we stop normalizing games being FUCKING MASSIVE????

just because storage is getting cheaper doesn't mean everyone can afford it.

also that download's gonna take a hell of a lot of time, consider that not everyone has FUCKING LIGHTSPEED WIFI.
7
15
13
Would you still love me if...
Show content

I did an IPO?

13
5
9

moved to @shellbyte@florp.social

undefined

0
0
0
Edited 1 year ago

hey you. yeah you, akkoma user. i bet you love akkoma 3.12.2-0-g26a91d5

(hint: click view on remote instance)

10
28
13
who's yaseen, you may ask?
Show content
have yaseen deez nuts?
1
5
2

moved to @shellbyte@florp.social

null

0
0
0
neocat_floof__w_ 💭 fedi server written in bash fedi server written in bash fedi server written in bash fedi server written in bash fedi server written in bash fedi server written in bash fedi server written in bash
2
1
3

@eris tried turning it off and on again? :p

0
0
0
:alerta: URGENT FEDIBLOCK
Show content
0
0
1
good morning feds!!!!
0
2
2

Can we tempt you?
neopossum Neopossums

ADD FOR $6.99 >

0
3
6

First it was @sugar, then it was @Bard, now it is @endali

I will not stop turning people genderfucked

You’re next.

14
7
13

@mae 3 billion devices live here???????

2
15
11

Me after I get knocked out:

I’m in a coma btw

1
7
8

moved to @shellbyte@florp.social

You do not follow this user and this post is marked as followers only.

0
0
0
Edited 2 years ago
it's been a bit over a week since the coral castle data loss disaster, so imma be giving some recommendations on how to not fuck up like i did to other server admins.

1. if you're upgrading your server, check the hardware you're using. this was caused by a single bad ram stick that i didn't test after install.
2. allow postgres to safely crash if it detects corruption. openrc automatically restarted the service, causing a loop where postgres would reboot and keep writing corrupted pages to storage
3. consider pg_basebackup and wal archiving. back up the whole cluster in longer intervals (weekly, monthly), and then wal can take care of the smaller changes over shorter periods of time (hourly)
4. check whether your backups work correctly. two issues arose after checking one of my backups. first, i was backing up the wrong database (this being the coral castle neo database), and second, the backups were not encoded correctly (using ASCII instead of UTF-8)

that's all everyone. keep your servers safe.
1
6
7

moved to @shellbyte@florp.social

meow

0
0
0
Edited 2 years ago
sui, ai, funny how bad this shit is
Show content
1
12
4
Show older