kɜ:ʳ @chr@cybre.space

hey y'all, i'm no longer reachable on discord if you had my info there previously. if you need to get in contact with me, i'm @chr:cybre.space on matrix, @chr1x on wire, or you can email me at chr@cybre.space (or admin@cybre.space if you want to reach @nightpool as well)

hi i'm chr and its my life mission to boost every dragon

got quite a few new folks here today, welcome! your admins here at cybre.space are myself and @nightpool, you can read the instance rules at http://cybre.space/about/more, and likes ⭐ are florps here. if you have any questions, feel free to ask! happy pinging!

the ghost in the machine sounds like a pretty spooky guy

maintenance is complete, and the matrix server is back online. thanks for your patience!

maintenance is ongoing; i'm migrating the database to its own server node and upgrading it to a new postgres version in the process. the matrix database is quite large so this is slow going.

the cybre.space matrix server will be going down for maintenance at 2pm PDT (in 3 minutes) for a bit, hopefully not longer than an hour

hey folks --

this doesn't affect anyone already here, but i've decided to stop doing semi-open registrations on cybre.space via patreon/liberapay donations.

this was originally put in place as a way for us to keep getting funding even after wide open registrations were closed. however, we've been okay on funding for a while now and the community has grown pretty large over time.

the patreon registrations aren't a huge volume of new users but cybre.space has nonetheless steadily grown over the last year or two. at this point we're about at the maximum size we're comfortable with moderating.

we will continue to allow registration by personal invite, so if you have a friend you'd like to join fedi you can still feel free to invite them here

your continued support is much appreciated. thanks, and have a wonderful day!

since viomi was unwilling to listen to the people most affected by the situation with Mint and admit that shiv was causing further harm with ver actions earlier today, ver account here has been locked. being nominally anti‐racist or having some BIPOC in support of your actions doesn’t give you a free pass to ignore the voices of the BIPOC most affected by the events at hand, and in this case those people were not being listened to.

please reach out to @LadyKIBI, @nightpool and myself if you have questions about this decision

just use tusky folks. if you're reading this and you wanted to use husky because the upstream app blocks gab / spinster, let me know and i'll swiftly escort you to our blocklist

boop

the internet had our old phone number, i'm trying to give it the new one but it takes a really long time to write it down

decided to move off of cloudflare DNS due to centralization and single point of failure concerns, as well as minor privacy concerns

we used to use our own DNS server, which worked fine, but while we were on cloudflare i moved that DNS server to a new host (with a new IP) and forgot to update the glue records

so the glue records are pointing at the old IP, which means that until the .SPACE authority's cache is refreshed, DNS queries for cybre.space and subdomains will have a bootstrapping problem and be unable to resolve

...i may have spoke too soon

depending on your dns caching settings cybre.space might have been unavailable there for a little bit

if it wasn't, don't worry about it

if it was, i think i fixed it

phew

hey anyone who uses Matrix through the cybre.space homeserver from the web client (https://matrix.cybre.space), heads up that we just upgraded to the latest version of Riot where they rebranded as Element. it's the same thing as Riot, just with a different name (they wanted to be able to trademark the name to prevent use by bad actors).

so other than the name and icon (and some minor UI changes) Element is Riot. nothing else changed.

netdata on the cybrespace matrix server has been reporting the following alarm at a steadily increasing rate over the last couple months: ip.tcp_accept_queue, "the average number of times the TCP accept queue of the kernel overflown, during the last minute"

this seems like the symptom of another problem, but i can't find much information about what it might be a symptom *of* (other than, possibly, a slow application not accepting connections fast enough).

can anyone advise? what should i be looking for to further diagnose the cause? what, if anything, could i do to mitigate this at the system level?

cybre.space users: apologies for recent federation delays, it seems during times of peak activity we've outgrown the number of sidekiq workers we've been using. i've scaled them up and hopefully the instance will perform better under load, but i'll be keeping an eye on things over the next few days to be sure.