I would say specifically the hardest part for self hosting is the grok'ing of how SSL works and setting it up right with automatic renewal.
There's a lot of extra steps involved often.
Id also say understanding how routing works and why you need a reverse proxy is the other big one.
No, twitter just shit the bed is all and thats where the scams were primarily spread, but now that so many people have dropped twitter you don't hear about it as much.
Pretty much 1/3rd of the ads I get on Reddit, for example, are still crypto scams.
I will agree though that it lost the crypto-bro sheen, thank god, and companies stopped trying to shoehorn it into everywhere it had no use case for.
There are use cases for it but they are extremely specific and most of the time a normal database is the right tool for the job. You need to satisfy multiple conditions for a blockchain to be the right tool for the job over a normal DB.
Furthermore, even if you do satisfy the requirements and use blockchain tech, its annoying to try and market that. Just as an example, how often do you see video game companies or gambling companies or other websites touting the fact they have, I dunno, a Redis mem server on their backend as a "selling point" of their service?
No one. No one does that, no one cares. No one tries to market what database their backend uses as a way to make their product sound better, because no one gives a shit what your backend is built on top of. They care about the actual features and functionality of your product, not the tech your developers used.
So hopefully we have now entered the era where some services do use blockchain on the backend when its the right tool or the job, but they don't bother to try and market it and no one gives a shit if its MSSQL, Blockchain, Mongo, or whatever else that is used to store data.