Back to the channels

#java

04:26 NeXeN yes, i just had a eureka moment!
04:27 NeXeN stupid and as silly as it sounds, it actually works. a very complex thing i've been building from a vision for months (man maybe year and a half now) and it can make a boolean value upper or lower case, as designed!
04:27 NeXeN man that's why i love coding, fsck them llms they make you lazy
04:30 NeXeN small accomplishments give me energy
04:39 jreicher Umm, huh?
04:39 NeXeN working on a gui app and just testing. doing simple stuff
04:40 NeXeN but you know, it's nice after putting a lot of effort into a thing, even a simple accomplishment makes things fun
05:01 jreicher Oh I absolutely know the feeling. It's one of the reasons I like using Emacs. Tiny tweaks have a big impact, and always feel simple in a way. But I'm curious what the thing is you're working on.
05:07 NeXeN oh, it's a library
05:08 NeXeN lets you provision a pipeline. has a schema code generator (not an llm, think boilerplate reduction) and a gui that lets you essentially do some of the design work visually instead of with json or xml, though you could i guess
05:09 NeXeN the code schema is used to enforce type safety across the pipeline no matter the language. there will be a TS library so can pass via protobuf or classic serialization
05:10 NeXeN but to get to the point where i can simply drag and drop a thing and see that it's type safe and doing it's thing is kinda cool. i had doubts if i had the stamina to stay with a personal project
05:15 deebo isn't protobuf typed already?
05:16 NeXeN yeah that's why i wanna use it
05:17 NeXeN i have become a fan, but it's not always straightforward you know....most people just serialize
05:19 deebo protobuf could be interesting to use instead of json over rest for internal data
05:19 deebo think netflix does it like that
05:19 NeXeN it's definitely more efficient. but i'm supporting jackson and gson as well just because
05:19 deebo apis would have to be more explicit about errors etc as well which would be beneficial
05:20 NeXeN yeah
05:20 NeXeN i mean you know, i can build tools to inspect protobuf as easy as json. but i'm hoping to keep it at a lower layer where i don't ever have to think about it
05:22 deebo our end user apps log all http traffic currently (even most bodies) for debugging etc, would be easier to filter protobuf too, http json has too many gotchas and "non-trivial" parsing to do that
05:22 NeXeN oh yeah no joke!
05:22 NeXeN hrmm you gave me an idea
05:23 deebo maybe time to let claude prototype something :)
05:24 NeXeN i have built a filter to filter out pii in logs, i bet it could be adapted to do a similar thing
05:25 deebo we use zalandos logbook, it can easily do header and property filtering, like "password": "hunter2" -> "password": "xxx"
05:26 NeXeN yeah. i dunno why you gotta log everything, but it sure is handy in a pinch
05:26 deebo but what it couldn't do (well), was when given a massive blob of data, like {"id": 5, ... hundreds of nested props ... }, we couldn't just log: {"id":5}, since that's the only important bit
05:28 deebo we use MDC with user session ids etc, so it's really easy to see what an user did that lead to an error, or check their claims of some problem that supposedly happened to them
05:28 deebo RUM could achieve the same, IF everyone agreed to third party scripts etc, but they don't :)
05:33 NeXeN couldn't you change from a full dump of the req/resp body just filter with something simple to parse the stream and just extract top level keys and full parse just for things i dunno diagnostic, like /id or /status and such and drop the rest, just keep what you need?
05:34 NeXeN maybe you could even populate the mdc at the gateway/filter layer with userId, sessionId, etc and the extracted entity's id?
05:34 NeXeN then you don't really need the raw request, i mean ...you know to figure out what they did
05:35 NeXeN maybe you got plenty of space. you know that's always a thing
05:36 deebo that would mean reading the streams going in and out into a buffer, trying (and sometimes failing) to parse into json, filter via code and then output to logs
05:37 NeXeN yeah, probably better to just rely on the route bindings instead
05:37 deebo we tried it but it didn't really work, would probably be easier with protobuf
05:37 NeXeN selective field extraction is cheap
05:39 NeXeN i like protobuf. i'm trying to push it into my personal projects. you know it sucks doing that at work....using a new shiny toy just because
10:33 hassoon 'morning
11:35 jreicher javabot is napping on the job again.
12:51 dreamreal I dunno why it's so inconsistent lately, I don't think anything's changed in the code
13:05 jreicher I thought it was "consistent" in its behaviour of not reconnecting? Maybe the change is in external factors causing more frequent disconnections?
13:20 dreamreal No clue, not watching the logs
13:20 dreamreal not my server, not my bot :/
13:36 Para libera servers don't allow immediate authentication either, so if the bot's too quick to authenticate, it can fail
15:23 hassoon 'afternoon
15:23 sbalmos what isn't "immediate authentication" about authenticating on connect with SASL?
22:01 * NeXeN shrugs
22:31 jreicher Para: what do you mean? I'm still learning about how IRC works but I thought only nickserv auth mattered, and if the nick is still in use you can use REGAIN. (That's how I have my IRC client setup for when I have a network glitch; it reconnects ASAP)
22:53 nimaje you should use SASL auth with a client certificat if the irc network supports it, like libera does https://libera.chat/guides/certfp
22:53 nevet Login With a Certificate (CertFP)
23:07 NeXeN some people don't use sasl, and you auth a moment later. i dunno i think the bot might have other troubles
23:07 NeXeN but also the network kicked my znc off, which hasn't happened before. like two days ago