Show newer

I'm deeply fascinated how we went from "lol your computer can't do floating point math in specific situations so Intel issues a half billion dollar recall" to "computers (LLMs) can't do basic arithmetic and there's nothing to be done about it" in just 30 years.

(You may have seen a similar poll before, sorry - I set it to the wrong duration back then! So here's another attempt. Please vote and boost again for broader reach! :boost_requested:)

Think of some kind of activist cause - it doesn't matter what, as long as it's something you would like to see improved in the world.

If I could guarantee that there were others who agree with you on that cause, and who are interested in organizing some kind of activism with you, would you get involved?

The biggest remaining issue right now is how the message processing loop is implemented; with the current structure, I need to pick from one of either:
1. Risk of deadlocking when making a query from an event handler
2. Swallowing an error in a number of edgecases, and leaving a client hanging
3. Processing incoming events out of order

None of these are really acceptable, so it's time to rework the message processing loop instead! The new approach will be to split inbound query replies and events; events will be guaranteed ordered, but query replies will not be (as they are tied to a specific query anyway, so any ordering naturally happens in user code).

This way, a query reply cannot be held up by an event that's being processed (case 1), and I also won't need weird error-buffering techniques to make the receiving loop continue (case 2), while still leaving ordering intact for those messages where that might actually matter (namely, events).

Show thread

Project update: my paired network layer library works! Example: gist.github.com/joepie91/4f366

This is a low-ish level network library that uses mutual TLS to implement a peer-to-peer CA-less pairing procedure (only one side needs to enter a pairing code). It's meant for building custom protocols on top of.

It gives you a bidirectional CBOR-encoded pipe with a built-in request/reply mechanism. It doesn't care what you send over it, values that you write (or reply) on one end come out the other end.

It also lets you specify your own protocol negotiation code; and it is client-initiated, so the server does not reveal anything about the protocol it speaks unless the client already knows what to ask for.

Identities are generated and managed automatically; you don't need to hand-generate or set up TLS certificates or anything, all you need to give it is an arbitrary key/value store. It ships with an in-memory and filesystem-based store implementation, but you can add others.

Soon to be published on a package registry near you :)

caffeine 

*inserts caffeine to kickstart refactoring process*

Reminder that people with "mental health issues" are more likely to be the victims of violence than the perpetrators of it.

#MentalHealth #MentalIllness

Over twee weken vindt de tweede Zaanse Woonopstand plaats! Your Local Pirates komen weer zingen en spelen om deze te versterken. Tot dan!

28 april, 13 uur start de demonstratie. Stadhuisplein, Zaandam.

Project update: my paired network layer library works! Example: gist.github.com/joepie91/4f366

This is a low-ish level network library that uses mutual TLS to implement a peer-to-peer CA-less pairing procedure (only one side needs to enter a pairing code). It's meant for building custom protocols on top of.

It gives you a bidirectional CBOR-encoded pipe with a built-in request/reply mechanism. It doesn't care what you send over it, values that you write (or reply) on one end come out the other end.

It also lets you specify your own protocol negotiation code; and it is client-initiated, so the server does not reveal anything about the protocol it speaks unless the client already knows what to ask for.

Identities are generated and managed automatically; you don't need to hand-generate or set up TLS certificates or anything, all you need to give it is an arbitrary key/value store. It ships with an in-memory and filesystem-based store implementation, but you can add others.

Soon to be published on a package registry near you :)

For rainy days we have a treadmill but it's locked into the vendor's subscription service if you want to watch videos.

Except...tap the bottom left 10 times, wait 7 seconds, tap 10 more times, up pops a number, use that as a seed to generate a number with lrand48, reduce modulo 999999 (not 1000000!) and type that number back in, and now you have an Android tablet with web browser and access to YouTube.

Linux people, *please* understand this. Sometimes people need to run Windows.

They’re allowed to complain about Windows ads, or tracking, or any other enshittification problems, without you saying “use Linux” every time.

Update: I regret posting this.

Update 2: I've addressed the most common comments below. I'm muting this thread now. Lesson learned!

rubenerd.com/people-who-need-t

Would people be interested in a blog (with RSS feed) where I make short posts about the new projects/libraries I'm working on or have released, going into what they do and why they exist?

Most of them will be small single-purpose JS libraries that solve a specific problem, with sometimes larger projects and 'end-user software' mixed in.

Hello fellow mastopeeps! We found these flowers sprouting up and down a stretch of boulevard grass on our walk in Saint Paul today. It looks like it was probably a garden flower that got loose and it's spreading up and down the entire block. I'm guessing it's probably an invasive species.

Anyone know what kind of flower this might be?

#Minnesota #MNastodon #flower

there are only 2 genders of tv exploits. one is rce in chromium that works because sandbox is turned off. the other is shell expansion

Would people be interested in a blog (with RSS feed) where I make short posts about the new projects/libraries I'm working on or have released, going into what they do and why they exist?

Most of them will be small single-purpose JS libraries that solve a specific problem, with sometimes larger projects and 'end-user software' mixed in.

@researchfairy 100% I have turned down an article similarly.

I refuse to condone any usage of ChatGPT.

Tip for women in science:

Don't collaborate with men who are not allies in the fight against sexism (unless you have no choice, which happens often of course).

You may think it is worth it, but really, it never is. You will end up mistreated and your ideas likely erased.

Show older
Pixietown

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