Mauve 👁💜 @mauve@mastodon.mauve.moe

Looks like Jitsi started requiring accounts to start chat rooms. Anyone have alternatives for open source ish video calls?

- no need for registering an account
- Using webrtc in browsers
- firefox support
- "pretty" urls like "/call/my-cusom-room-name"
- open source ish and self hostable

Reply-guy is out. It's "people with replies" now. Get with the program. 😤 /j

One nice thing about the battery life on my steam deck is that if it gets to the low 20's I know I've been staring at my screen for too long and should switch it up.

I wish the web monetization spec didn't end up breaking down. It'd be really cool if folks could use whatever payment system they wanted and have their user agents and bridges figure out how to route stuff. The single implementation and hard requirements to use Know Your Customer tracking wasn't great though.

Like what if we had a FEP for tying ways folks could pay you with your ActivityPub Actor.

For real we should ditch wallets and password managers and OAuth and instead use public keys + ActivityPub Actors + HTTP Signing. Though I guess it puts a lot of trust into the DNS layer?

Fun fact, looks like our admin registration is going to use the same http auth mechanisms.

Here's how it looks:
- Keep list of admins in webmention format in the DB
- Admins talk to the API using signed HTTP requests
- API verifies requests by verifying the signatures

Cool side effects? No need for storing a password or issuing tokens or actual admin account data. We can also use wildcards in the list like `@*@hypha.coop` to allow any account from a given domain to have access.

Tee hee, just added blocklist importing to the #SocialInbox using Mastodon's blocklist format :P

See my pals in meatspace definitely know I'm a massive tech geek but I feel like they don't always think about the depth to which tech geekery has a stranglehold on my soul. 😅

Every time I need to load a large chunk of data into memory instead of streaming it and processing chunks of it at a time my brain starts buzzing from the code smell.

Also whenever I use blocking IO on a single threaded codebase 😱😱

My poor RAM. It should be caching files instead of buffering!

I feel like humans being persistence hunters carries over in my hunt for making code work. I'm out here tracking the functioning configuration through the potential space of all possible code and sweating up a storm not to overheat.

"aha, the import didn't work due to a version conflict" is pretty much the same as "Aha here's a tuft of gazelle fur on this branch" or whatever

Luckily I am a wizard and have made NPM and Node.js do things so depraved that a mere typescript inconvenience cannot stop me 😈

The stuff I've done to make stuff build for react-native and cordova qualifies for one of those "This Place is not a Place of Honor" signs.

Now some dependency's build system for typescript got busted and it doesn't have the transpiled JS available in the dist folder. And of course NPM decides it has to preemptively update all my dependencies when I try to install an unrelated new one. 🙃

Is this really worth it? Hours wasted dealing with build systems to catch bugs that would be caught by a linter and unit tests anyway?

Gosh typescript brings me so much needless suffering sometimes. 😅

The real pain is when it refuses to run when the equivalent in regular JS would work. Like, I promise you the types match up just trust me bro. I think I'd find it less frustrating if it wasn't wrong so often.

```
Type 'ReadableStream<Uint8Array>' is missing the following properties from type 'ReadableStream<any>': values, [Symbol.asyncIterator]

35 const parser = Readable.fromWeb(response.body)

```