Notices by nex (nex@fedi.transgender.ing)

THE INTERNET!

WOW and to think I'm just trying to be funny but sharkey out here calling me ANNOYING 😔

@jessew@mk.cpluspatch.com that is illegal and I am a law abiding citizen of the united kingdom

im BORED

"why do you run like every matrix server implementation" a mild obsession.

i need to do more funny

OH: the specification only defined that libs need to be owned, nobody said anything about not owning everyone else at the same time

Ok my instance is starting to slow down because it's having to sling so much data across the world, but I'm also past the point that I can't move the database closer to the instance because it's so big now 😭

@jessew@mk.cpluspatch.com mama,

hello world i forgot you existed

@jessew@mk.cpluspatch.com registration token for transgender.ing is ekr2QHTMZZsE050iJtFOJBelt0VediNW1 if you want an alt on there for the time being, I've gotta go soon so I can't troubleshoot further 😔
You can use https://cinny.transgender.ing or https://element.transgender.ing to register, whatever tickles your fancy

@jessew@mk.cpluspatch.com Yeah, it should resolve itself within a few minutes, you weren't offline for too long

@jessew@mk.cpluspatch.com Anything?

@jessew@mk.cpluspatch.com give it time, one sec

@jessew@mk.cpluspatch.com It is fixed, you'll just have to wait for servers to stop backing off. Let me see if I can force my Synapse to push

@jessew@mk.cpluspatch.com if you leave it like this, it will eventually fix itself, but it could be two days before people start federating with you again

@jessew@mk.cpluspatch.com my server says the destination for you is supposed to be matrix.cpluspatch.dev:443, but a live resolution says your destination is actually cpluspatch.dev:443. You might wanna switch your well-known/matrix/server back (no idea what your setup looks like)

@jessew@mk.cpluspatch.com matrix.cpluspatch.dev

@jessew@mk.cpluspatch.comChecking if cpluspatch.dev is in the s2s cache. 'cpluspatch.dev' is not a valid IP[:port] literal. Proceeding with well-known resolution. Result for 'cpluspatch.dev' from well-known: 'cpluspatch.dev':443 ServerName object is now ServerName(server_name='cpluspatch.dev', sni=None, port=443, cache_until=1743380791.21113) well-known reported the server address as explicitly 'cpluspatch.dev':443 Final ServerName object: ServerName(server_name='cpluspatch.dev', sni=None, port=443, cache_until=1743380791.21113) Sending a request to https://cpluspatch.dev:443/_matrix/federation/v1/version (but connecting with SNI/Host: 'cpluspatch.dev') Response code: 200 Response headers: Headers({'server': 'Synapse/1.127.1', 'date': 'Sun, 30 Mar 2025 00:26:31 GMT', 'content-type': 'application/json', 'cache-control': 'no-cache, no-store, must-revalidate', 'access-control-allow-origin': '*', 'access-control-allow-methods': 'GET, HEAD, POST, PUT, DELETE, OPTIONS', 'access-control-allow-headers': 'X-Requested-With, Content-Type, Authorization, Date', 'access-control-expose-headers': 'Synapse-Trace-Id, Server', 'transfer-encoding': 'chunked', 'strict-transport-security': 'max-age=15552000; includeSubDomains', 'x-content-type-options': 'nosniff', 'permissions-policy': 'interest-cohort=()', 'vary': 'Accept-Encoding', 'content-encoding': 'gzip'}) Response text: '{"server":{"name":"Synapse","version":"1.127.1"}}' Response: {'server': {'name': 'Synapse', 'version': '1.127.1'}} Response successful!

@jessew@mk.cpluspatch.com what