Hacker News new | ask | show | jobs
by heyoni 879 days ago
This is based on personal experience and user reports where those whose beepers installed displayed errors continued to work, whereas beeper installs configured to refresh registration codes automatically were much more likely to be banned.

It’s important to note that an error in the former config could be ignored for like a month without any actual service disruption; it was 100% aesthetic in some cases.

A week ago I updated my beeper client and it set itself to automatically refresh registration tokens and got banned. I disabled iMessage on all my devices after that.

1 comments

So against the vendor's advice you sort of shot yourself. Appreciate taking one for the team but I don't see any risk to myself here as I have no intention of using Beeper.
Yep. I know I did something that could jeopardize the service but I will never chastise myself for it...and as someone who spends a sizeable sum yearly on Apple product, I'm going to make it my choice to boycott them unless they do a 180.

I won't abide a company punishing its users for wanting the convenience of picking up their text message convos from Linux because it's otherwise too distracting to pick up a phone each time.

Really happy to take one for the team. I mean that. This was going to happen at some point in the future whether or not I liked it, glad it happened now. I can't live in a world this connected where my linux box and 12 years of texting history is totally cut off from it. No thanks.