Show newer

@uint8_t@chaos.social @ShadowJonathan@tech.lgbt a Doppio!

@futurebird @pixouls wonder if it'd be enough to have a constant (slow) drip of droplets going down a little plate, with space on the sides for bees, and then a tiny solar powered pump to get droplets that weren't taken back to the reservoir

@vv @Seirdy@pleroma.envs.net @welshpixie there's also much less vertical space between the name and text, compared to the other message blocks

aand we're back. after fighting with mastodon & ruby for way. too. fucking. long.

i've spent so much time trying to mess with shit and literally the only thing that works is pulling ruby 3.0.5 from nixos 22.11

Show thread

fun how the gargron library for blurhashes broke mastodon going from ruby 3.0.5 to 3.0.6

Show thread

oh no i completely forgot the chai tea i made, and now it's cold

@Shrigglepuss i get caught in the machine too often, not sure if screwdriver helps

@tobi this is why we need to bring Luddites back, but they were mocked and dismissed as being 'against progress', instead of adressing very real issues of who that progress is actually for

Well. I've just learned a couple of things about the spec and its process that are giving me serious concerns about the long term.

I'm refraining from sharing details here right now, because they would be extremely easy to misinterpret, and it's not an immediate problem to worry about.

However, I do think that it's time to start seriously thinking about forking the protocol, and I've created a room for talking about this: :pixie.town

If you're interested in working on this (as a developer, as a technical writer, as a spec designer, or something else), then please join the room!

However, it's important to recognize that such a spec fork will impact many existing communities and developers, and so breaking compatibility is not to be taken lightly. If possible, it should be avoided.

So if you feel like burning everything down and starting over, this is probably not the project for you. Also, I do expect everybody *not* to harass Matrix core folks over this.

If those things are not an issue for you, then please join! :boost_requested:

Show thread

@rune CW: work c79b3e9b-e709-466f-9f42-3389d20de651 (please keep UUID when replying so it stays with your ticket)

Instance admins are often targeted by the instances they block, with the admins of the toxic instances emailing them straw man arguments and sealioning questions meant to have them question their decisions and trick them into thinking they're being unfair.

As I'm often asked for advice with how .art deals with these shitheels, in the next toot I'm going to provide a simple guide that anyone can use the next time the disingenuous admin of Another Toxic Instance emails them.

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.