how many hosts are still vulnerable to heartbleed

hotter take: if you work in alignment, you should really watch Code Lyoko

Lmao, sure buddy

it has now been ONE (1) day since Mythos released

we are still alive

mythos turn this into a saas

i didnt know you were capable of making python jokes, given our dislike of py

technically x86 is a virtual machine if you think about it

look the only way to patch the world is by making it hot-reloadable, we can approach this by the following industry steps:
- rewriting everything in elixir
- giving me Claude Mythos, and i will give you KernelCare-for-Gays out of it, trust me

we finally did it. we made the T-shaped engineer llm. maybe thats how i would announce that to the linkedin-types

today marks the peak amount of attention a BSD has ever had in its lifetime

i like having my little vm that i can run claude yolo mode on and then go to sleep as it cooks

then wake up to something working one-shot

it passes the turing test...

when compared to any kind of community-level vouch-like system (lobsters, mitchell's vouch) where i HAVE to contact someone first to be invited or to be added to a blessed list, i feel it's much better (and thanks to dids, reusable)

though ofc i dont have control over what ppl do w the graph

the fact atvouch is intended as a "global" thing helps here. you still need persistent identity and ways to build up that identity ofc but i don't need to contact the repo owner if i can find a good vouch path between me and them

ty. absurdly intentional

😭

banger

all of them tell me about how cool gleam looks and yet i havent seen them write a line of it. all of them are scared of the power of hot-reload on prod or some shit

one day ill be able to convince my friends to make things on top of erlang/beam vm. ive been here for years

have you made any prototypes of the design? looks cool!

udon needs to do clock sync, account for clock drift, schedule ~hundreds of objects to be animated, custom throw physics, ratelimits, etc. but the main intended loop is call loadurl every 5sec yea

elixir is just for the server (and a nif in zig for hot path)
world client is all in udon (not on gh)
and yeah string loading is very good. they run on separate 1/5s ratelimits iirc so we could do something really funny if we wanted to

our protocol doesnt rely on any mp4 stream! it actually syncs your clock with server and does delta updates over http. you can call http on vrc but ratelimit is 1/5sec so our design is all about masking that to make it look like a realtime stream

bsky.app/profile/nata...

github.com/lun-4/vrhose

@atvouch.dev has reached over 500 vouches in the network (505 rn)

thats cool! even if its only 70 accounts that created at least one vouch that's way more than i'd expect for this thing so i'm happy

my fedi presence has become much smaller b/c fedi is fedi

either way yeah that's my article

btw im interested to make a demo, i think i can make a pr bot that does code review though dealing with tangled auth and api was difficult. would you be ok with the demo being in elixir so i can copy my good impl over lol

if you want to continue with hmac my preferred ux would be that i create a webhook on the wisp frontend, a secret is generated that's only on your db automatically, and i copy paste it from the browser into my config

then never expose the secret on wisp wh records

from the docs tangled webhooks provide push events which is a valid thing that isn't on the firehose (i think). that's all (and its not something wisp wh could solve either without special-casing and keeping track of knotservers)

as a side note i dont think i would migrate to tangled webhooks! given pr events are already on firehose, i could also replace my 2nd tap with a jetstream filtered to pull records to ensure traffic consumption is low. i wanted to stay on tap for backfill reasons.