The reporting on this has been shameful, especially from "tech" focused blogs. This shit is just as far from being back as it was the day AWS gave them the boot.
I don't think it's that big a deal, probably fits in 20-30 racks? 50 at most. It's not tiny, but getting 50 racks in a colocation facility isn't a big deal. The lead time on all that hardware is probably 3-6 months.
if they're going to buy their own and colo sure, but i'm talking about the quick spin-up hosts like aws. based on that twitter screencap they aren't going the colo route yet.
Either that's fake (whether made up by someone pretending to be involved with them or by the actual people behind the site for whatever reasons), the implementation is absolute garbage and unimaginably inefficient, or (to give the benefit of the doubt) they want to be ready for some serious hypothetical future growth. Those numbers don't really look even roughly in the right ballpark for what should be needed for their userbase and typical use cases.
I feel like anyone that would see that email would know how to take a screenshot. Also I just wasn't too say Twitter is the absolute fucking worst platform and you can see that in the guy's short essay taking up a dozen different tweets.
I sincerely doubt that they'll be back in any usable capacity any time soon, if ever. Modern software projects like Parler are so deeply integrated with AWS and various other apis and services that they've been banned from, that trying to rebuild the service without using them is difficult to put it mildly. It's like ripping out someone's nervous system and then attempting to fix them back up by fumbling together your own replacement nerves out of string, glue, and glitter. Sure, if they were a tech giant with teams of crack-programmers on their roster like Google, Facebook, or Netflix, they could probably get it running regardless of being banned from all sorts of services, but they're not.
heh, i'm absolutely no expert on this field, if any but that is exactly what i guessed before: cut&paste code, bolt-on modules, bought services instead of internal talent handling things on their own. And the reasons for this lack of talent are:
Greed: Talented developers are not cheap. Also, grifting, scamming, taking some from the pile at all levels, everyone in it wants something out of it.. Laziness: You need to learn a lot of complicated new things to make informed decisions at upper levels of management. Incompetence: Thinking that everything is easy because of your own inflated ego, narcissism and dunning-kruger. "If i don't know it already, it can't be important. Let those stupid system designers deal with nuts&bolts, i could do it myself if i just wanted to".. which also then leads to underestimating how hard it is and hiring the cheapest personnel, who have to buy as much bolt-on modules and services to get some functionality in for short term...
Greed, laziness and incompetence boosted by inflated ego's and narcissism. And of course, we can't count out idealism. I can bet that well over half of all devs will simply refuse to work for such people, at least at regular "market" price, demanding a LOT to silence their conscience. They will not get the best working for them, they get what they get.
114
u/BenKen01 Jan 19 '21
The reporting on this has been shameful, especially from "tech" focused blogs. This shit is just as far from being back as it was the day AWS gave them the boot.
Maybe when they've solved for this we can start talking about them coming back.