Mauve 👁💜 @mauve@mastodon.mauve.moe

@serapath it being js only is a major limitation sadly. 🥲

I have no clue how google homes work, but I should be able to just sumkon it by name without extra app poking right?

If only I had a "perfect" p2p protocol that was resource efficient, mutable, and fully local-first. :x Also with http gateways and a url spec.

Considering making some sort of digital beast that I can summon into people's homes via their google assistant. I'd talk to it in code and use pass phrases to access it's true nature.

probs jusr for playing my music and stuff?

@daaain No, I think you're spot on with the ndjson stuff. I'm just too web browser brained with this niche api that barely anyone uses. :P opening a request and piping it into an ndjson parser might need a bit more work dependency wise or code wise, but it's also more likely to have easier implementations accross languages. 😅

I had a dream where @makeworld posted a screenshot of his terminal in a work group chat askong a question but it had some sort of cli command called "ужде" invoked like "ужде -уху | something" and I was in the middle of figuring out wtf it was supposed to do but my phone woke me up. I'm guessing it would have been some common tool used by merveilles.town folks though :P

(the cyrillic letters are gibberish btw and not actual words)

@metasyn An Ottawa band called Skullgate :)

I'm not really in touch with the scene but some of my pals are so I tag along every now and then.

Went to my first hardcore punk show. It was fun.

Lol I was a bit too hasty packing for my move and now all my makeup and medicine stuff is in a jumble in a box 😅😅

@daaain Could you elaborate now how the ReadableStream API applies to this context? Do you mean that folks should parse `fetch()` responses as a binary buffer stream and that that would be used for subscriptions along with a custom NDJSON based wire protocol instead of the EventSource API?

IMO EventSource give us more to work with, but I would agree that NDJSON with a series of Activities would be easy to implement.

@happyborg Maybe if we can figure out how to get SAFE protocol handlers into @agregore ? :ooo

People are always like "what are the financial incentives for #P2P protocols??" but I'm here seeding like 50 TB per month out of the goodness of my heart and my unlimited fibe internet.

All Linux ISOs and copies of Big Buck Bunny.mp4 of course. 😈

Defs gonna set up some sort of TOR and Veilid relays or whatever. Maybe also move my server hosting to be on prem in my living room?

@iatendril@snug.moe Also speaking of scope chain, the `with` statement still works and can help you perform true acts of evil with your code >:P

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/with

@evan Websockets means inventing more wire protocols and is much harder to implement. Server Sent Events are a simple text based standard and have a way to deliniate event types / reconnect logic / etc. Fitting an event stream of AP Activities is a small amount of spec work and implimentation compared to websockets. (cross language too) Also easy browser APIs!