mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

3.2K
active users

#hachyderm

0 posts0 participants0 posts today

Morning #Fosstodon and #Fediverse ☕

Today's luxury problem: I've made an initial selection from our volunteer offers, but that still leaves us with at least 29 strong candidates 😅 Ugh can't believe we have so many qualified, enthusiastic people! I'm discussing a training plan with @joel and @mike , Mattermost invites will follow soon.

I had a nice call yesterday with the admin of #Hachyderm, to learn about their moderator rules & appeals, how they handle certain situations etc. Very useful. 🔥

Goodmorning #Fosstodon and #Fediverse ☕

I'm omw home from a nice bouldering trip. 🧗‍♂️ We've seen such a high amount of volunteer offers (🔥🔥) that we'll have to make a first selection through a survey; I'll send this to our potential mods tonight. I've included a question about the importance of diversity & inclusion.

I've had time to think about a statement, tbc. I also have calls with admins from other servers this week, incl #Hachyderm, to learn from them. More info soon. Enjoy your day! 👋

I didn't realize my username would be permanent when I first joined #fosstodon, so the instance's uncertain future gave me the final push to start over from scratch at #hachyderm with the username I wanted. I should've switched sooner since I appreciate that Hachyderm's moderation policy is much more clear cut and exhaustive.

Hi #Mastodon / #hachyderm

Just a quick re-#introduction after moving instances.

I'm a software developer based in the Netherlands. I'm passionate about Software, HAM Radio, Electronics... and I love blogging (although it has been a while 😅 )

From now on, this is going to be my central hub, where I will be publishing blog posts, project updates and anything I consider interesting for the community.

Looking forward to chat with lots of people!

OK, seeing the stuff that is going on w/ #fosstodon, it seems that if I were to move it would probably be #Hachyderm or #Floss. W/ that said anyone know if you could "slurp" your posts over? I'm not in the mood to spend time/money in firing up my own instance, & honestly social media seems to continue spiraling into a cesspool anyways.

If other servers are "defederating" (if I understand that correctly), I don't want to miss out on reading posts for the hashtags I follow. Thoughts? Ideas? Thx!

Greetings #Hachyderm

I just migrated from Fosstodon so figured I'd do a quick #introduction

By day, I'm a data platform engineer for a medium-ish tech company.

When I'm not increasing shareholder value, I love swimming and running, rock climbing, and anything outdoors. Indoor hobbies include video games, reading scifi/fantasy.

I think Haskell looks cool and I want to actually learn it this year.

I have one cat. He has one orange brain cell and he is a sweet boy.

Hey #hachyderm, are we just going to sit around while cybersecurity companies are cowed into submission? Is this how it all really goes down? President takes away clearance and everyone is just quiet about it? I hope you realize that if we don’t hang together we will hang apart. #Infosec as an institution is being attacked the same way as Education, Science, Health, and the Law are under assault. Guys everything that is good and true is under attack by literal evil doers this is your time get off your asses get to work we have a big job ahead

After I make this post, as announced yesterday, I am defederating #hachyderm over #nivenly (their parent company) endorsing transphobic death threats against me, using the name of their deceased transgender founder to disparge me. Details here: https://fedi.aria.dog/notice/AstMFfVyR64yThXUlU

I will continue to make noise and raise awareness about their values, but I have no need to stay federated to do it efficiently.

This will only affect a very small amount of people. You are not welcome in my home.

Hello, hachyderm! we've been working hard on building up our ansible runbooks and improving hachyderm's overall resilience. Recently, we've been focusing on is database resilience.

We're getting close to retiring our original database server (finally!) and preparing to move to a fully ansible-managed set of databases servers, primary and replica on new hardware. We'll send another announcement when we do the cut over. The team has done excellent work to make this highly automated, quick, and painless! :blobfoxscience:

Done:

✅ author ansible roles for managing postgresql, pgbackrest (backups), pgbouncer, and primary/replica failover
✅ decide to continue with pgbouncer and *not* use pgcat
✅ rotate database passwords
✅ order new replica database hardware
✅ order new future primary database hardware

To do soon:

🟨 rebuild replica database with ansible scripts
🟨 prepare primary database with ansible scripts
🟨 start replicating to new database replica
🟨 cut over to new database server 🎉

We're also planning on open-sourcing our ansible roles in the coming weeks - just a little housekeeping & tidying up before we do!

Hello again Hachyderm! :hachyderm:

As promised, here is the announcement blog post regarding the Pixelfed vulnerability, outlining the impacts to our community.

Our blog post outlines the data behind the decision and steps for admins to reach out to us to refederate after they patched the vulnerability.

Although the number of following relationships was low, the number of instances was high relative to that number. Basically: we're still in the process of reaching out to impacted instances as of this publication. Thank you for your patience!

community.hachyderm.io/blog/20

As a reminder: we're happy to answer questions and engage with the Fediverse community. We're here to help :blobfox:

Hachyderm Community · Pixelfed Vulnerability and Impacts to FederationPixelfed CVE-2025-30741

howdy, #hachyderm!

over the last week or so, we've been preparing to move hachy's #DNS zones from #AWS route 53 to bunny DNS.

since this could be a pretty scary thing -- going from one geo-DNS provider to another -- we want to make sure *before* we move that records are resolving in a reasonable way across the globe.

to help us to do this, we've started a small, lightweight tool that we can deploy to a provider like bunny's magic containers to quickly get DNS resolution info from multiple geographic regions quickly. we then write this data to a backend S3 bucket, at which point we can use a tool like #duckdb to analyze the results and find records we need to tweak to improve performance. all *before* we make the change.

then, after we've flipped the switch and while DNS is propagating -- :blobfoxscared: -- we can watch in real-time as different servers begin flipping over to the new provider.

we named the tool hachyboop and it's available publicly --> github.com/hachyderm/hachyboop

please keep in mind that it's early in the booper's life, and there's a lot we can do, including cleaning up my hacky code. :blobfoxlaughsweat:

attached is an example of a quick run across 17 regions for a few minutes. the data is spread across multiple files but duckdb makes it quite easy for us to query everything like it's one table.