If I tried to keep up, I'd be run over. It's too much input for the normal individual I am.

Not necessarily, great engineers do also ship temporary code they didn't have the time to trim.

Our process is of 1) make it work, 2) make it right and 3) make it fast; not necessarily that engineer had time for the 3rd step.

And unlike Telegram, for a WhatsApp bot you need to apply with a bunch of paperwork. If you're an SMB, you got little chances of ever getting access. They'll tell you to go with their Technology Partners and make a chatbot with these other BigTech companies like Freshworks, etc.

To the best of my knowledge, a domain can only be renewed in advance for up to 10 years.

(that could be the reason for that status).

--

[0]: https://github.com/handshake-org/hsd

I stopped coding for the past year or so and I'm considering going back because I definitely feel my own sharpness lost.

View rates must have dipped for a percentage we don't know of, but definitely made a dent.

Physical copies of games have in their EULA that the game is licensed to you, so theoretically they could still disable it.

Precedent? BlackBerry phones refused to connect to WiFi if you didn't pay for your mobile data plan. It became a 2G brick.

Floating-point precision has too many gotchas for being suitable to store Decimal types, especially for the Currency use case.

If you want to be a security vendor reseller, just make sure to sell to orgs that have a compliance requirement, either by law or similar.

Do you sell firewalls? sell them to banks or something. Anti-malware endpoints? Insurances too. SIEMs? payment gateways for their PCI DSS environments.

Price it just below what would be the fine for not complying, that way you maximize the invoice.

I stopped playing the security vendor reseller game because it got too boring this way to make money.

Could this be adapted to inherit DLP policies? I have a sample use case, for example:

- Some DLP customers don't need full name protection but might need to prevent credit card PAN numbers from being leaked, per a PCI DSS compliance standard. Expiration dates don't need protection, and only the first 6 and last 4 numbers of a credit card can be shown; CVV2 is off the table, of course.

By checking out the repo, I know this can be configured manually, but can you make it so that it inherits DLP configuration instead of manual configuration? This could considerably boost enterprise adoption.

Big companies don't want to keep manual maintenance of a separate tool, whereas if they adopt it and "just works" with their existing ecosystem, that's an easy win.

This is easily, easily something you could sell as a business exit to a DLP company, because it's one of the "limbs" of protection they offer.

Like the government saying: "Sorry Fox, you cannot have this one, this one is too good for your dinosaur management."

Since that's a very dangerous government hand meddling, I guess the correct move is to let it happen (to our liking or not).

But as written to the letter of the law, no, as this would not create a monopoly. More consolidation yes, but a monopoly technically not.

Statuses cannot be disabled, so the little notification dot is always there (I solved that by archiving everyone's statuses) and the phone call feature cannot start a recording when you get called. If you need to record a call you need to do so separately.

If for some reason you want to stop using WhatsApp, you just cannot. You socially exclude yourself.

Most people you know are there so you cannot just leave it. Some companies run their business there. Some government services and banks have a WhatsApp chat bot, and don't accept email or phone calls anymore.

I wish I could fully leave WhatsApp, but I can't without paying a social price. The network effects are a straitjacket.