First, make sure the transaction was completed for the correct amount net of monero transaction fees.
Yes, I absolutely made sure of that. Even waited for all ten confirmations.
One ~~secure~~ way to contact them is through matrix.
FTFY. And of course the (still!) embargoed clusterf*ck. Don't roll your own crypto, kids.
Not objecting or disagreeing, but could we get more than a one-line explanation for breaking protocol changes? maker selects arbitrator (breaking change) does not inspire a whole lot of confidence. Is there a discussion somewhere I can read that spells out the options and why this one was selected?
when/why was one ever required?
I think the many competing messengers are a good thing.
If they were backward-compatible (with their predecessors) and interoperable, I would agree. But they absolutely aren't. The lack of backward compatibility in the chat/messenger space is abhorrent.
It seems like everyone is trying to drag me to their favorite messenger
Yes, because people treat messenger choices as a popularity competition.
Look how many people I got to switch to crapware just because they wanted to chat with me! I must be super socially powerful! Woo hoo! Meanwhile, the technical consequences of this strategy are... predictable: crapware.
Opt out of all the noise and just stick to IRC.
Everybody reading this message should also read this, since it gives the details: https://github.com/haveno-dex/haveno/blob/master/docs/deployment-guide.md#register-keypairs-with-privileges
There are no servers in Haveno. Instead, there is a "developer (public) key" hardwired into the client. Instead of the owner of the localmonero.co domain (and TLS certificate, and onion url key), there is the "developer public key". The developer public key you have in your client basically decides "whose Haveno" you want to use. This is a good thing! I always worried about the localmonero.co domain being seized by a simple letter being sent to their registrar. With the developer key system this can't happen. The thugs have to actually go hunt down whoever has this key. The key isn't even kept online (like a TLS key or an onion key).
Whoever has the developer key decides who the arbitrators are. Just like localmonero -- whoever owned the domain name got to decide who the arbitrators were.
I think OP's posting is kind of an unnecessarily-scary way of saying that the client ought to ask the user to type in this key (or several of them!) at installation time, instead of being compiled in. That is a great idea.
I also don't understand why websites are still using bespoke hand-rolled XMR payment frontends -- unless they are exchanges or (like localmonero) super-Monero-gurus... BTCPay server's Monero support is so good at this point... I have used it uncountably-many times and not once had any kind of problem.
Please folks, if you're going to accept Monero, consider using BTCPay Server.