@xuu Are you interested in getting on Signal and swapping contact details and such so we can discuss some ideas in collaboration in more real-time? You have great ideas, I _think_ we could benefit from a bit more real(ish) time 😀

(#flupfna) @xuu I caught AT&T doing this last year. They were also hijacking DNS queries if I remember correctly.

@xuu (#ck25fya) Looks cool!

(#oyi5iua) @xuu Yeah this is a great idea👌 I was just thinking of the storage format and what clients would fetch as a resource 🤔

(#bxxydla) @xuu His private Jet planes whereabouts which themselves are publicly broadcast (because that's how airplanes know where each other is) right?! 🤦‍♂️

(#m37icwa) @xuu Thank you for the info. I definitely wouldn't mind one, despite originally wanting to join, through some other instance. Since they're also promising seamless instance switching, this should hopefully be a non-issue.

(#ensvuua) @xuu Hmmm that is bizarre indeed, its as-if the cached entries for that feed on your pod is stale somehow? 🤔

(#hn4w24q) @xuu Congratulations! That's by far the longest twt I've seen. :-) Working fine in tt. I was a bit worried, that lengths of multiple screens would be hard to read or scroll. But magically it just scrolled line by line. I reckon two `return`s can be saved in `GetUser(…)`. Oh, on further inspection there are even two nested `err != nil` checks. Generics were desperately needed. I'm glad they finally introduced them. I stumbled across them last week and gave them a shot. The syntax is probably not the very best, but I will get used to it eventually.

(#zwpd7hq) Yeah, the lack of comments makes regular JSON not a good configuration format in my view. Also, putting all keys in quotes and the use of commas is annoying. The big upside is that's in lots of standard libraries. I think the appeal with YAML is that is has comments, is kind of easy to write and read and also provides unlimited nesting levels. But it has all its drawbacks, no question. Forbidding tabs, thousands of different string flavors, having so many boolean options (poor Norwegians) etc. I use it, but I don't particularly enjoy it. Among simple key value pairs, I like INI files, but with `#` for comments, not `;`. I never used TOML, read up on it yesteray before writing this question, but it looks a bit weird and has some strange rules. I guess I have to give it a try one day. And yes, as mentioned by several of you, it always depends on the complexity of the configuration at hand. I'm developing something for the scouts at the moment with rather simple requirements on the config. Currently, there are just four settings. Even INI would be overkill with its section. I selected JSON for now, because that's readily available with Go's std lib. But I do not like it. Btw. what's your own config format, @xuu?

(#rg3d75q) @xuu Hope you recover soon 🙏🤗