Not needing to be at the top of his game anymore makes anyone lose that sharpness. As you just said, he doesn't need to fight New York politicians anymore.
I stopped coding for the past year or so and I'm considering going back because I definitely feel my own sharpness lost.
Though you have a physical copy of the game, I don't discount a future where a console refuses to load a physical copy of the game because DRM impedes it. Much like when short-lived TLS certificates expire on their own, even by being offline.
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.
I fondly remember Backtrack 2, running as a Live distro. I remember going to university labs where a teacher taught us a couple of techniques or so. Great days.
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.
This reminds me of these enterprise solutions to prevent data leakage, Data Loss Prevention tools (Safetica, Forcepoint, etc.).
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.
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.
Not to kick dirt on their faces, but I also think Discord is just not the proper chat community open source projects should have.
Might be my IRC mind talking, but a proprietary service like Discord, or Slack, or even Telegram at times, is just not suitable for the target community, as there's often a data privacy concern.
I never had a Discord account, and I'm hoping I can keep that streak.