That’s why they renamed it in hopes that people won’t know any better.
chiisana
joined 1 year ago
Sonos’s protocol is also same; if people want to develop on their platform using the protocol it is documented and there are open source solutions:
Finally! My dumb dumb 1TB ram server (4x E5-4640 + 32x32GB DDR3 ECC) can shine.
What’s the resources requirements for the 405B model? I did some digging but couldn’t find any documentation during my cursory search.
I’m inclined to think due to the nature of the platform, contents are constantly duplicated to the eyes of search engines, which hurts authoritativeness of each instance thereby hurts ranking.
It’s not “what if we decide he’s super cool later” but instead “what if we decide later the new name is also bad, so we end up repeatedly changing something that we’ve deemed shouldn’t be changing”.
Somethings in the scientific community should not change — I.e. what we consider as 1 gram should always stay the same so experiments can be reproduced consistently. I’m not sure I agree with them that names should be one of them… but I’m not a scientist studying plants, so the heck do I know?
I’m not refuting that the price is ridiculous, but shat you have there is just one VPS with single point of presence and single point of failure. Hopefully (seeing the provider wants to charge absurd amount of money for 2TB) there’s a much more robust infrastructure distributed globally for better performance and uptime than a single VPS.
You really should have separate services for registration, DNS and hosting. That way you’re not held hostage by a single provider.
You guys have cubicles? I thought we’ve done away with that and mandated all offices to be deprived of walls and dividers since the 2010s in favor of open office floor plans? Someone get the office manager on the line.
Lemmy is bad with money, economics and business, also anti corporate/work, so anything positive towards corporate tends to be slammed with ignorance. I try my best to just ignore those replies / votes and move on.
I’m aware this is the selfhost community, but for a company of 20 engineers, it is probably best to use something commercial in the cloud.
Biggest pain point was for our ops guy, who constantly had to stay behind to perform upgrades and maintenance, as they couldn’t do it during business hours when the engineers are working. With a team of at least 20, scheduling downtimes could get increasingly more difficult.
It also adds an entire system to be audited by the auditors.
The selfhost vs buy commercial kind of bounces back and forth. For smaller teams, less than 5 to 10 engineers, it might be a fun endeavour; but from that point on, until you get to mega corp scale with dedicated ops department maintaining your entire infrastructure, it is probably more effective to just pay for a solution from a major vendor in the cloud instead.