HASS configuration has gotten a lot better in the past few years. Almost everything can now be done via the UI, including automation and scripting, and it's one of the smoothest scripting GUIs I've used. It even supports cut/paste for visual blocks. And for those 5% cases, there's an inline YAML editor which will open (and validate) only the pertinent block of what I'm sure is a 1000-line YAML file for editing in-browser.
Z-Wave is still dodgy, but the migration to zwavejs has been an improvement and probably is as good as things will get with the state of Z-Wave being what it is.
It's still not perfect, but HASS has become one of my user-facing open-source success stories. Most of the remaining annoyances are out of their control at this point.
And this is an ephemeral key-value store here, which is basically a best-case scenario from a performance standpoint. It's basically the last thing you're going to need to think about sharding, which is why session stores traditionally cohabitate(d) with web servers.
No, session storage doesn't get expensive fast. It's extraordinarily cheap unless you screw up the configuration very badly indeed (Apparently PHP still defaults to writing session data to disk?!)
Twitter still exists. Renamed. Same exact thing. You can create an account and post whatever random things you want. Some people might follow you. Some might not. If you see something that makes you sad, you can block the person who posted the sad thing.
It very much is not. No third-party clients; can’t see threads without an account; owner inserting himself and his ideology at the centre; fewer and less diverse participating people; diminished trust in the platform; more spam; different verification rules… Even the character limit is different.
Not just aggregating data for fun. It made third-party clients like Tweetbot impossible. Similar to non-old.reddit.com, the web interface has been crappy for a pretty long time, but was easily worked around by using better clients.
There are thousands of bluecheck AI bots that just copy-paste/regurgitate or just make up stupid content and post it continuously to get engagement views and money.
You don’t need to follow someone to see their content. When you open the app the default timeline is the “For You” one. Sometimes you don’t even notice that the app has switched back to “For You”, X definitely doesn’t really want you staying on the “Following” tab.
"Popular" tweets (of which these bot accounts often fall into, because they're propped up by bot responses and engagement farming) are pushed into your feed even if you're not following (or engaging) with them.
Tags are crowdsourced. I was tagging games with "always-online DRM" before they declared it on the store page, but only the top few tags are displayed, so there's no point.
They also editable by developers / publishers and it's by design. Any sane developer prune their tags from time to time since Steam recommendations depend on them.
So it's not exactly a reasonable place to put something like that.
String/str are both valid UTF-8 by definition, though. Plain ol' piles of bytes in Rust are generally represented by Vec<u8>/[u8].
Rust could have done better in naming, but a definite design goal of the language (for better and worse) is to not make things that are complicated for the compiler appear simple to the user. Which unfortunately results in: