Jason Parker (he/they)

282 Followers
1.2K Following
61 Posts

cybersecurity researcher | independent #journalist | software developer | telephony engineer | #opensource contributor | #infosec researcher

Disclosures: https://govtech.cc

IDNs: Tester and collector of single-character domains that browsers render. See: ꩰ.com, https://ဪ.com, https://የ.com, https://ㆲ.com, https://ㆴ.com

Verifibation™️: https://v.jeltz.org, free Mastodon verification system that allows any user to get a verified link in their profile - no setup/registration required.

Oink: https://oink.ing

Disclosureshttps://govtech.cc
Primary@north@ꩰ.com
Linktreehttps://linktr.ee/northantara
Jeltzhttps://jeltz.org
Can we all agree that April Fool's day is cancelled for the foreseeable future? We already can't trust our eyes and ears.

For all the #Mastodon #selfhosting folks out there, any idea what I should be looking at as far as backoff timers or whatever from other instances coming back down, after something like a week of downtime? Several instances, most notably infosec.exchange, still haven't been sending me new messages, some 18 hours later.

I didn't even get one when I tagged myself in a new post - https://infosec.exchange/@north/116199899292856762 - until I searched for it¹. Any insight maybe, @jerry ?

Curiously, Threads and brid.gy started sending me messages within about 15 minutes of coming back online. That seems bad.

¹ at that point, it became a pull, not a push

Edit: A boost from the other side does not appear to have been correctly pushed.

ꩰ.com recovered! Jason Parker (he/they) (@[email protected])

@[email protected] ey bb u up?

Infosec Exchange
@north ey bb u up?

but most of all, Ololoshka562 is my hero

#iykyk

It'll never stop being funny seeing an AI "actually, wait, nevermind" itself.
Lots of loss around accounts and statuses (most of which is going to be remote), but after some mucking about, only 1 record (sorry person from https://bsd.network/) from the follows table.
Is timeloop.cafe having issues? I can't seem to find @[email protected]. Direct link to their profile on the site works fine and I can hit their profile on , but not here.
Phase 3.

When I'm done, and I find the time, I'm definitely documenting this process.

I guess I can start now.

Step 0: cry

Database recovery for ꩰ.com is looking very good. Every table is intact. Reindexing got rid of a lot of the noise, and while there are still a significant number of bad rows, there are still a very large number that remain. Currently working on copying good rows into new tables that can be exported from the bad DB and reimported in the live DB.

I am extremely happy with this. We could back up as early as tomorrow?