It is never the who say we know everything we need to know but always the or the
Any conversation
At moms house for the holiday weekend so the kids can see Nana. She has a "premium Plex" account on her tv serving a truly massive amount of content. Allegedly the brother of a long time friend is offering the "service". She says that the service will go down when the host is having outages, so the infra is likely local.
I brought my year this weekend. We are going to dig in to this guys operation. Intuition dictates that there is some hand rolled accounting going on. I'd like to see it.
Added it as a company on LinkedIn so it must be 'live' now. Cheltenham-od.uk
โฆ
Microservices.
Not really programming, as this is more on the architectural level.
Microservices is a valid approach when you need to address massive scale. The thing is, I have seen it applied to things that could realistically serve its audience in a handful of modest servers with a less fashionable approach.
It was done under the guise of simplification; each individual microservice was in fact very small. But this at the cost of absolute spaghetti architecture.
"for you" now contains the same message multiple times
โฆ
added two more screenshots to - the "root" post view is incorrect, but when reply-on-reply, information goes up-then-down.
root post view IS correct, sorry.
I understand your confusion, but that's the formatting - quoted parent is below the child post - then that post's replies follow in the discussion view. The top post is always quoting its parent below it, the different bg makes it distinct. Just need to get used to it, same on X.
There really is no other way to include the parent otherwise, you have to break the hierarchy at some point, the other form would need to omit the parent body and show a 'parent' link but we want to include its body.
