my article is not really about web3, just using the analogy to touch on "layer 2" and introduce the idea of querying your interactions with a website _over time_ : hence the "temporal web"
interesting, didn't know about the booking experiment
but as i was trying to explain, they missed the point and just created frustration for users
didn't want my article to sound like bullshit, that's why i built a poc to try and explain that it's not about having chatbots, but having entire components in a chronological order of the interactions with a website
in your case the booking details would be easily accessible just by scrolling up for instance
totally understand the hassle of figuring out how to pay taxes etc.
we definitely want to champion this idea of having fiat and crypto side by side, and how to do it properly.
going all crypto might be too brutal and we think the hybrid approach makes more sense: work for a company that pays you in fiat (for bills and legacy stuff ;)) and crypto.
agreed, payroll is hard - we actually mean only the payment part of payroll right now. we'll experiment on ourselves first by paying salaries in fiat+crypto to get a better idea of all the implications.
paying vendors is simpler indeed, and it's even better with crypto because you pay low fees (and not based on the amount you're sending)
we're totally aligned with what you're saying about the "secret sauce" - we actually released a feature called "direct transfers" that aims at doing that (except that it's not with a card atm) https://medium.com/multis/introducing-direct-transfers-a-new...
we need to go deeper in this "corporate bureaucry friendliness" though and have more levels (right now only owners/guests)
cool to see that you get what we're trying to do :)