Joshua Strobl

190 Followers
14 Following
411 Posts

All aboard the migration train! 🚂 Just moved to @JoshStrobl (Fosstodon) from mastodon.cloud. Seems like it's a more active, up-to-date Mastodon instance. Thanks everyone for your suggestions!

Unfortunately given post migration isn't a thing, can't move my history from here to there, so I'm going to keep this as a locked account so folks can at least check the post history if they want but not follow. I went ahead and updated my site to point to Fosstodon as well!

I set up a Fosstodon account and noticed that there isn't an option to re-upload my toots and other data from this tarball, only a subset of my data (which I actually need to export as the CSV). Am I missing something? Would hate to lose out on all my posts.
Anybody have suggestions for actively maintained, reliable Mastodon instances? I've had nothing but problems with mastodon.cloud, constant outages and their use of an old Mastodon release.

Streambits #Collea Alpha 1 deployment going well 🚀 Some early #WebSocket related issues have been resolved, both Pings and automatic connection cleanup working as expected.

Let the testing and even more rapid product iteration begin!

That moment when you're doing the setup for @streambits #Collea Alpha 1 deployment and forget you have to do this stupid dance with Fedora to enforce systemd cgroup hierarchy as 0 to not force cgroups v2 so your Docker container works.
@streambits Oh and as much as I love gorilla mux for HTTP routing / multiplexing, 38.34kB of memory for it is being spent on its use of regexp alone. That is 23.50% out of the 65.81% being allocated for mux router ServeHTTP for a served http *conn. That's no good.

@streambits Out of 16.36kB for a gocqlx Select call, 12.35kB (75.4%) was just go-reflectx. In comparison, the rest of my load funcs in various parts of the stack range from 4.12kB and 8.24kB.

For one of my API handlers, 27.62kB was just json Encode, out of 39.88kB. I performed two calls of my load funcs for the rest of that.

Two things I'm concluding by implementing memory profiling in my backend for @streambits #Collea:

1. JSON encoding is hella expensive, several times more than calling load funcs in Streambits Core.
2. go-reflectx is the devil and I need to kill off my usage of gocqlx.

Why do I get the feeling I'm on a fairly dead Mastodon instance? 8 people using a tag really shouldn't be considered trending 🤦‍♂️

@streambits That just ends up complicating the implementation of that support and product iteration to the point it has little to no ROI, even for myself sometimes. That's shitty, both developers and end users deserve better.

Thank you for coming to my TED talk.