kɜ:ʳ @chr@cybre.space

@jamierocks no it's just the mastodon instance

some users have had issues exporting their account backup archives, so to make sure i can communicate with users until all issues are resolved i will be delaying the read-only phase of the cybre.space end of life to january 1st, 2023. (also because there's a lot going on in my life right now and i want to make sure i can respond promptly to issues that might arise)

to be clear: you will still be able to export backups after the site goes read only. i just want to make sure people have a way to reach me if they encounter problems.

@niconiconi @nightpool we have a known issue with exporting archives, i will try and have it resolved by the time the site goes read only

@jollysea the cybre.space modifications will continue to be available indefinitely at https://cybre.tech/cybrespace/mastodon

@devurandom yes

i am shutting down the patreon effective immediately, thank you all for your support over the years, from the bottom of my heart, you've made it possible to run the instance and for that i'm eternally grateful

for a lot of reasons, both personal and practical, i don't think i can effectively run a public mastodon instance any more, and i need to retire cybre.space. i want to do this responsibly and make sure everyone has a chance to migrate and export properly, so here is the plan for the instance retirement (feel free to share this link around): https://cybre.space/~chr/cybre-space-eol

due to ongoing moderation load issues and understaffing, between now and 1 november, the instance may be undermoderated. for other instances, if this poses an issue for you, i encourage you to use federation tools at your discretion. i would only ask that you be clear and public about your decisions so that cybre.space users can figure out where they will be able to migrate their accounts.

thank you

the cybre.space matrix server is down today as our database filled up its storage volume; currently working to free up space to get it back up and running, and submitted a request to our cloud provider to increase the disk size. don't have an ETA but i hope to have it back up by this evening.

hello! it's been a while since i've posted here other than to respond to specific inquiries, but since there's been a steady number of signups to cybre.space through community member invites and word of mouth: welcome!

if you're new here or if you just haven't seen it before, we have a patreon and liberapay which are used to pay for the costs of running the mastodon¹, matrix², and gitea³ services that we provide here.

¹https://cybre.space
²https://matrix.cybre.space
³https://cybre.tech

if you're using these cybre.space services, please consider supporting us through one of these means:

https://www.patreon.com/cybrespace
https://liberapay.com/cybrespace

we do not accept cryptocurrency donations due to environmental, social, and technological concerns. if you were going to reply to this post asking if you could donate crypto, please consider divesting yourself of your cryptocurrency resources and supporting an environmental or social justice initiative instead.

thank you!

@Alamantus @nightpool looked into this. i added the header to our media CDN configuration and it looks like audio is playable now. thanks for the heads up.

@OberstKrueger if it wasn't corrected shortly after the fix, it probably won't be corrected, but missing posts can still be fetched by loading threads that they may have been a part of and pasting direct URLs into the search bar

if you run mastodon on ubuntu or debian with jemalloc and you notice sidekiq crashing frequently, it may be related to this issue with FFI: https://github.com/mastodon/mastodon/issues/15751

the fix in our case was to add LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so to the systemd unit files, so that all native (non-ruby) code could use the same memory allocation system

just fixed an issue with cybre.space's sidekiq worker that was causing it to frequently (30-60s) restart, interrupting longer-running tasks and possibly causing posts to get lost from feeds. hopefully things should be a bit more stable now