feels like poisoned nul byte attacks are due for a comeback again
@tef
- 4.1K Followers
- 422 Following
- 7.9K Posts
former main character. they/them is fine
i''ve been idly asking two questions "how do i handle 'any' in golang" and "how do i handle something like json.RawMessage"
i ended up doing something nominative, where types on the wire have names, so 'any' is easy but 'raw message' means carrying around type headers
only to then bump into "how do you embed things with a name clash" or "how do you deal with anonymous types" and "what about unknown types" and i've started to question all my choices
CuTELAhoy!
We will be operating ADSL, VDSL and GPON services at EMF in a limited trial area in Camping C2.
You can even wholesale your own service over the top!
Docs on getting connected are here - https://docs.cutel.net/events/emf26/internet_services/
Ret
haven't had an opportunity to say "keep this up and i'm going to file a jira ticket with your polycule" but i know it's only a matter of time frankly
jwzRE: https://indieweb.social/@laurenshof/116720287681995824
New AGENTS.md just dropped
i have tried out several different designs and all i have now is a code base where all the good names are taken
have been idly killing brain cycles trying to work out what the equivalent of json.RawMessage would be for a more gob-like format
if you're wondering what that means, json.RawMessage is a thing that lets you say "decode some of the json, leave the rest as bytes"
the problem is that gob style things have a header, so taking some random subset of the encoded message doesn't make much sense
but it would be super nice to build up things ad-hoc like you can in json, so here i am whirring