No - I don't want to write inherently buggy smart contracts for your scam. If I wanted to do that, I would have gone into fintech awhile ago.
I don't know what committee of developers "that don't own/trade cryptocurrencies" you imagine exists that has some authority on what marketing terms you can use on twitter, or why a group explicitly disinterested in a topic should be consulted in the creation of those terms...
The reality is that programming work surrounding payments and/or finance is going to be deeply unappealing to most devs as it is incredibly dry and extremely tedious.
Apologies, as an outsider I'm sure I have used some conflated terms. To clarify, I was explicitly referring to smart contracts (and the like). These programmed arrangements carry with them the minutiae and stress of what I imagine programming at a bank or large financial institution would be like. Coding a bug in a smart contract or at a bank can have very severe consequences. It should be done with the utmost care by highly skilled persons, not your average web programmer (which is the position you are taking by calling this stuff Web 3 and when, for instance, Ethereum decides to base its smart contract language on JavaScript).
While this is true for some specific segments of the current internet, it is not inherently true. Or rather, as a programmer, I can choose to avoid such fraught tasks.
I also challenge the notion web3 is a "sucessor" to the web. I wouldn't call web 2.0 (the social web) a "successor", it didn't replace anything. It's just a descriptor for a different user/product relationship.
Web 1 -> read only Web 2 -> read/write (comments, primarily user-generated content) Web 3 -> read/write/own (users "own" the content)
Most of cryptocurrency marketing works that way, throwing jargon at you until you feel stupid for not understanding why it is supposedly so revolutionary. And once the thousands of marks who have already been roped into the scheme discover your comment, they'll be all over it to protect their investment and you'll feel very alone.
Not sure I understand your point. What developers do you need to consult? Some random developers coined that term, as much as some random developers coined the web 2.0 terms. It's up to people to use it or not.
Edit: actually, maybe the justification of the SemVer bump is that people stopped caring about IE5 support :)
You might disagree with the approach, but using blockchain as the backend for an app is very different from previous iterations of the web.
The fact that you build your “web 3” application using Web 2.0 techniques (SPAs, etc) tells me that web 3 is not a thing. It’s another type of backend, and the web is designed to have those appear in perpetuity.
Interesting and constructive.
I kid, I kid … mostly.