When that data resides on a third-party SaaS platform, I am trusting their security architecture — which I cannot audit, cannot verify, and cannot modify.

And which was designed by and is operated by dedicated teams of professionals.

Which you are not.

Which would you find easier to explain to a judge - that your client data was part of a larger Google breech and attack or that your bespoke home grown system was misconfigured?

The only things I see it used for are 4chan replacements and crypto bs. This seems to aspire to be the former.

Yeah, “built on ipfs” is a decent red flag.

🤣

Yeah - alt.binaries never worked.

It’s also text-based by design. You can’t upload media directly. If someone wants to share media, they have to link to an external host and the UI just embeds it.

Kids still learning about base64 encoding.

I keep getting the feeling that this is just a massive ad compaign.

“Our AI is so good we need to hold it back!” followed by releasing an incrementaly better model…

In a business with tens of thousands of servers, it makes sense to have long complicated names.

I’m actually not convinced of this approach. It’s one of those things that makes perfect logical sense when you say it - but in practice “DBDWWHORCLHHIP01” is just as meaningless as “Hercules”. And it’s a lot more difficult to say, remember and differentiate from “DBDWWHORCLHHID01”. You may as well just use UUIDs at that point.

Humans are really good at associating names with things. It’s why people have names. We don’t call people “AMCAM601W” for a reason. Even in conversations you don’t rattle off the long initialism names of systems - you say “The <product> database”.

God I hate the “stuff as much information into a server name as you can with no separators in all caps” naming conventions…