GTG3000

…funnily enough, it may actually be better for musicians if people left spotify, considering the absolute pennies they pay per stream.

I’ve seen the russian version before, must be it.

usually russian translation won’t hide the address, but idk if it was the case here.

Man, I love lua, but after switching to a different job on typescript I feel like lua could only benefit with a similar type system. So many bugs avoided just because I know for a fact what a function returns and expects.

In my experience, it was an attempt to prune the stuff in old API that wasn’t useful. A successful attempt, since the backend working on it was in the same room as me and I could yell at him.

So you just gave him an excuse to go have a coffee break and wondered why he didn’t care? :P

“Everyone is using IPv6”

It’s barely supported. Most providers here “offer IPv6”, but each has a different gotcha to actually using it, if it works at all and they didn’t just route you through hardware that doesn’t know what it is.

Well you know how it is. Everyone who knows what’s going on left, everyone else just watches TV and believes them because why wouldn’t they.

Oh I absolutely used to stim with it :D

My fingers do random swipes all the time, so it’s annoying.

Personally hate the change to the swipe. I get that on some huge servers people probably use the “reply” feature a lot, but I definitely don’t have so much use for it as to give up the nice, coherent and logical UX of “channel/server list is on the left, user list is on the right, just swipe to them”.

IMO, swiping should be for navigating UI, not interacting with individual items. Now there’s a useless thing on the swipe and I have to reach to the top of the screen if I want to check who’s online and in the channel. Annoying.

That and the new DM screen doesn’t use swipe right as navigation, it’s just a “back” button now. Can’t quickly look at the DM list and go back to your conversation by swiping right-left any more. Literal lazy design because this is an easier way to program that interaction.

Don’t care super much about the DM button moving, it’s more convenient to access but breaks the UI paradigm. Shrug.

Oh, and the “midnight” theme is not new, you could use it for years now in the old versions.

It’s a departure from the desktop UI and it made the whole thing much clunkier.

I will be fair, moving the button to the bottom row is more convenient if you have a lot of servers to scroll up through and use the DMs a lot, I don’t care about that as much.
What I do care about is how the rest of it changed. Can’t just quickly swipe into the DM list and back any more, if you exit the DM that’s it, you gotta click on it again. Switching between DMs and servers is more clunky, a bunch of UI I was actively using is broken up. They broke the search function, and the new way to check channel participants (click on the title) is uncomfortable as hell compared to old “just swipe to the right”.

Personally I hate the new UX even if some bits are an improvement. It’s just too much stuff to change all at once and not for the better.

I think some people expected their entire community to get up and move.

Well, perhaps that is healthier.

But it doesn’t trap eyeballs.

Well for me, the real content of Reddit was finding an interesting thing and then reading a few dozen comments from people really in the know.

Here it’s going to be a dozen top-level comments and maybe one of them will have a thread longer than three messages.

Less content, that is spread across multiple instances that can have duplicate communities.

You just can’t keep doomscrolling here, the “active” search repeats all the time and the “best of the day” is like two pages.

And then there’s specific communities that just… Stayed on Reddit.

The orient-ness of it all.

Well, there’s a few things I personally think are a must for a config format:

1. It must be human readable and editable, in some way. - in many cases, you may want to go and change something in the config while the application proper isn’t running. That rules out stuff like pickle or binary formats. Although I suppose sqlite and it’s ilk still fulfill it, in a roundabout way.
2. It should be unambiguous, with one way to do something right. - this one’s a doozie. JSON fulfills it since it’s unambiguous about it’s types, but many interpreted language configs will have options. And then YAML will have “no” turn into “false”.
3. It should probably have comments. - handily failed by standard JSON implementations. Although to be fair a lot of parsers I’ve used understand comments. Or you can make a comment stripper real easily.
4. It should have obvious structure. - I’ve dealt with CSV configs before, I do not want to ever again.

Oh god, parsing complexity. I actually tried writing a YAML parser in my free time before and boy was that not worth the headache. So many little things that complicate parsing and are ignored by majority of users!

I really like python, but I can agree that it’s no-delimiters style can be… Confusing at times. I definitely had to hunt down bugs that were introduced by wrong indentation. That and the way it handles global/local variables, mostly.

I do appreciate not having to enclose every key in “”, and being able to copy values - but if we want that kind of logic making our configs, why not just switch to writing configurations in Lua? It certainly has less footguns than YAML and it has the niceties like “I can just write {key = "value"} instead of {"key": "value"}”.

Most comment-aware JSON parsers I’ve seen just use standard // to delineate comment lines.

Python has stricter rules about what can be cludged together and how.

Yaml is… Kind of nebulous, which is not a good thing for a data serialization format.

Fair enough, lol.