HN user
My blog at: https://www.ivanmontilla.com/
Yes, but it's nowhere near the maturity of Telegram's Bot API.
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.
It does, but it's not enabled by default; and that's the point.
(Yes, but it expires at 2035-05-20. If you count years by rounding up to integers, there's not enough time room to renew it an additional year. It would make it 11 years.)
But if you check the domain's expiration date, it's far away in year 2035.
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).
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.
I do that too, and meditate if YouTube wounded themselves by adding that feature.
View rates must have dipped for a percentage we don't know of, but definitely made a dent.
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.
That's such an unfortunate name for a good, reputable distro.
For JSON serialization, which doesn't support fixed-point precision it does.
Floating-point precision has too many gotchas for being suitable to store Decimal types, especially for the Currency use case.
A string type. As parent says: it completely bypasses the problem. Save the numbers between double quotes and be done with it.
This.
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.
yeah, but who's to say Fox is gonna screw up this one?
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).
If the spirit of the antitrust law is to protect consumers from enshittification, then yes.
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.
WhatsApp got toxic also.
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.
Adding to the 2nd point: It's one of the most watched APIs for suspicious activity ever.
Anything not from their vanilla app, the littlest dot on their charts will trigger severe alarms and actions.
Big correlation systems. The safest path used to be to automate the app itself, through mobile automation, but they even got too sensitive to that.
I don't doubt the whole app has a behavioural analysis component, full screen size, much like a big "I am not a robot" checkbox.
Also, it's very likely their private APIs are CSRF-protected or similar.
Pray for the organic, pay for the boost.
I realized months ago that social networks are distribution systems. Want acceleration? Pay.
There is little incentive to make anything viral/organically boosted.
Yes! I had to search who Ralph Wiggum is, had I known I'd have undestood the humour hah!
I thought he was some mad Karpathy-tier ML scientist or something.
You still need domain knowledge and a solid understanding of what you're doing/what you want to achieve.
If you don't have that, now that writing code is basically zero-cost now (in terms of time), you'll still be slow.
I did not realize it's possible that AI could engage with a project in such a way that Brooks' Law becomes applicable. Fascinating.
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.
Don't ask the why, ask the how. How did they get acceptance into an incubation stage with what you just mentioned?
For sure Anthropic should be developing a model without these guardrails for your use case? Kinda like Mythos is only available to certain organizations.
Parasitic behaviour. Extractivism.
Argentina doesn't also, you can just buy a SIM card off the newsstand.
I'll be in the thread all day.
Yeah, now that's flagged.
DDOS doesn't destroy websites. It just makes them unreachable until the disgruntled person decides it's been running long enough.
You can be absolutely destroyed if your hosting provider later hits you as a Website Owner with an excess traffic bill.