Hacker Newsnew | past | comments | ask | show | jobs | submit | watermelon0's commentslogin

You should use a separate WhatsApp account for bot purposes.

Recently, I used a separate WhatsApp account to interact with a group chat that I have with my friends. After about a week, they disabled the account, with no way to re-enable it.


Since WhatsApp accounts are bound to phone numbers, getting a new phone number is a significant hurdle in many legislations.

An easier solution is to just not use WhatsApp at all and look for the alternatives for bot purposes. Telegram explicitly encourages bot usage with no risk of bans.


And what ever happened to tools like jabber ? Or any other open source alternatives

Jabber/XMPP was designed around persistent TCP connections. Push notification support came too late.

> in many legislations

Do you mean “jurisdictions”?


I said "legislations" because the word describes the existence of laws, while "jurisdictions" describes the law enforcement.

There are still some European non-EU countries where you can get an anonymous phone number because laws are not fully enforced.


This is incorrect usage in English I'm afraid, and jurisdictions covers areas with different laws, 'legislations' is not used in this context.

Well, your usage is nonsensical in legal terms. Also, that is not the definition of “jurisdiction”.

Nobody who knows law would use “legislation” in that sense, nor would they recognize it in that context, Humpty Dumpty.


In my case I did, but it's still wasted time and money. And when breaking TOS there's always a chance of getting related accounts also banned, though I don't know if that has already happened with WhatsApp or not.

Seems like it only supports x86_64. It would be nice if they offered a way to bring your own compute, to be able to work on projects targeting arm64.

The main difference is that iMessages count towards iCloud quota, whereas (most?) other messaging services have free storage.

iMessage doesn't require you to store history in icloud, it can just store everything locally if you want. But yes, I'd rather not have stored history, or the option to pay for storage than to have all media crushed beyond recognition.

A few times I've wanted to print something and found it was sent over an IM app and compressed to 100kb rendering it useless.


Cloudflare Tunnel publicly exposes your services, whereas Wireguard/Tailscale are VPNs.

Tailscale (but not Headscale) offers Funnel, which is a reverse proxy, but you cannot use it with your own domain.

Pangolin is the closest alternative to CF Tunnel, but self-hosted NetBird with reverse proxy functionality can also be used.


The intersection of people who can self host headscale or netbird and those who can not set up their own reverse proxy is probably the empty set.

System Settings -> Keyboard -> and toggle Keyboard navigation.

I'm not sure why this isn't the default, but this allows for UI navigation via keyboard on macOS, including Safari.


Huh? I'm not seeing any popups except the cookie banner at the bottom of the screen.

Pricing link is the second one in the top menu, and it shows all prices in a straightforward way.


European Hetzner VPSes have at least 20 TB of bandwidth, and US ones have at least 1 TB.

I don't think there is a cheaper CDN.


Unless I'm missing something, AbortSignal is quite standardized on backend as well.

Of course not all libraries support it, but many do, and support seems to be growing.


From your link:

> Non-commercial use only. You agree that you will not use our Services for any commercial or business purposes and we and our Providers have no liability to you for any loss of profit, loss of business, business interruption, or loss of business opportunity.

There are separate commercial terms for Team/Enterprise/API usage: https://www.anthropic.com/legal/commercial-terms


I suspect you are accessing their website from a European IP address. The clause you quoted is not present for users outside of the EU/UK.

https://news.ycombinator.com/item?id=47590473


That explains it. I don’t see it from my US IP address.


They are supposed to be, but Disney doesn't think so: https://arstechnica.com/gadgets/2026/03/av1s-open-royalty-fr...

Also, let's not forget that the majority of devices still don't have AV1 hardware decoding support. For example, Apple only recently (2023) added support with iPhone 15 Pro and M3 Macs.


> For example, Apple only recently (2023) added support [for AV1].

Apple has been actively obstructing open video formats for a long long time—Apple is the reason there isn’t a baseline format for <video> in the HTML5 spec, for instance. (Or at least there wasn’t when the spec was still a well-defined document with a version number; I see no merit in keeping track of the “living” one.) Incidentally, Apple is a member of MPEG-LA and claims to hold numerous patents covering both AVC and HEVC.

At this point, whatever harms befall Apple’s users due to lack of Apple’s lack of format support are entirely Apple’s fault.


Don't forget their lack of support for FLAC. It's completely mind-numbingly, brain-damagingly stupid.


They support ALAC though, which is also known as "totally not FLAC".


The claims made by Dolby that some H.265 patent claims that are formulated very vaguely also apply to AV1 are probably bogus.

Like many other such frivolous patent lawsuits, Dolby hopes to either scare the other company into making a deal in order to avoid bigger legal expenses, or to establish a legal precedent if their cunning lawyers can convince a technically incompetent jury that the H.265 patents are applicable to AV1.

This is the kind of trial that should have never been decided by a normal jury, but only by a panel of neutral experts in this field.


Is a panel of 'neutral' experts even possible to field in this area? I feel like anyone with sufficiently in depth knowledge of both the AV1 and HEVC specs has almost certainly derived a big paycheck for years from stakeholders on one side or the other of these lawsuits.

I'm no expert, but Google having designed AV1, I can certainly imagine a world where the codec infringes upon HEVC just enough that the lawsuit fees would come out in the wash.


You are right about the danger of non-neutral experts, but there still is an essential difference between a group of experts and a jury.

The experts may be biased, but when they open the mouth and try to argue their position their bias becomes obvious for the other experts and it can be contradicted with logical arguments.

Unless all the experts work for an interested party, it would be very difficult to impose an incorrect verdict, because it is impossible to argue in its favor without the mistakes in the argument being immediately exposed by an interlocutor.

On the other hand, with a standard jury most people will be unable to see what is wrong in the arguments presented to them and they will not be able to distinguish truth from lies in such technical subjects.

The US elections and the elections in many other countries are an eloquent proof of the capacity of average people for distinguishing truth from lies concerning much simpler facts than the details of video compression patents. Expecting a jury to choose the right verdict in such a trial seems too optimistic.


hmm if you know how patents work, "Google having designed AV1" isn't same as "Google 100% sure AV1 doesn't have patent infringes"

even if you're google, you can't be 100% sure if there's some obscure patent lurking around the corner


What I don't understand is why the AV1 pool isn't activating their MAD clause.

Part of the idea with AV1 was that with the constituents also holding such a massive warchest of patents (plus big tech being richer than god), they would countersue and demolish anyone that tries to bully AV1 users. Which would act like deterrence.

Where is all that might? Was it all just saber rattling, and are they basically going to let the AVC / HEVC patent holders make a fool out of them?


For now Dolby has just filed a lawsuit.

If this will reach a trial, it remains to be seen whether Snap will fight alone or it will receive support.


>hardware decoding support.

As a side note this isn't always superior - recently discovered my desktop uses way more power with hardware decode than software. Counterintuitive but issue isn't per pixel efficiency but that it keeps the GPU in a higher power state


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: