Sort of. Apple's and Google's notifications infrastructure only delivers to signed applications. Even if you run your own IM server, you can't use your own open source client without building and signing it yourself, and then setting up the backend infrastructure, which requires using the developer certificate for the application to generate authentication credentials to Apple's and Google's notification service. IIUC (and I think as you point out) the way it works for XMPP is a client informs the server about its gateway, which will be run by the client publisher; when the XMPP server wants to generate a notification, it contacts that gateway which then pushes the notification through Apple's/Google's service API for delivery to the client. For a nominally self-hosted IM server, notifications are traversing two third parties, either of which might be logging the metadata, which may include the full body of a message, depending on the application's frontend and backend architecture and configuration.
So in a sense it is part of the application, especially if you're a small entity with a single app (as opposed to large entities like Facebook where you have dozens of applications under a complex hierarchy of developer and application certificates).
I can understand why things are done this way. It helps to avoid abuse and spam as there's no way to inject notifications without strict accountability. But it does kind of suck. To fully self-host IM, you need to build, sign, and distribute the client yourself, as well as run a notification gateway with the appropriate credentials. And I'm not aware of any plug-and-play open source solutions for the gateway, at least not for XMPP. (I could be mistaken, though.) Maybe Matrix servers have it builtin, but I wouldn't be surprised if they don't, especially the reference implementation, as this complexity provides a moat for monetization.
> The frustrating part is that it's not a workflow _or_ model issue, but a silently-introduced limitation of the subscription plan. They switched thinking to be variable by load, redacted the thinking so no one could notice, and then have been running it at ~1/10th the thinking depth nearly 24/7 for a month. That's with max effort on, adaptive thinking disabled, high max thinking tokens, etc etc.
So Boris' explanation isn't really an explanation.
While simultaneously drastically reducing the amount of work you can get done even at $200 a month. I've cancelled my subscription, it's not worth it anymore.
It should be noted that they are not just bombing, but using airburst white phosphorus munitions over civilian areas attempting to scorch the earth and give people a lifetime of health problems.
The fighting is concentrated in active Hezbollah controlled areas in southern Lebanon, from which rockets have been indiscriminately fired at Israeli civilians, again.
Hezbollah chose to open and sustain this front. But sure, bot, keep trying to promote your "scorched earth" narrative.
I'm not a bot, my email and website contain my full name and are visible on my HN profile, and my website has pictures and videos of me.
First, collective punishment is not acceptable. Shooting through a baby to kill the criminal holding it hostage is obviously monstrous, so your argument that there's "Hezbollah around" is invalid. Civilians present? Then find another way, Israel. But Israel refuses because terms always include something along the lines of leaving occupied Palestinian territory, which Israel refuses to do for many indefensible reasons.
Second, though, is that Israel has lost all credibility. You say Hezbollah is in the area and the thousand people killed are Hezbollah? I say, Israel once released a picture of a calendar and said it was a list of terrorist cells. Israel has lied too much to be trusted anymore.
There's also horrifying reality that's becoming increasingly clear as more street interviews from Israel are released: it's becoming clear that much of this bloodshed is fed by ethnosupremacy and Islamophobia. Israel is becoming the next Nazi state.
Yes...but let's also be realistic. Very few people are still using this Kindle as their daily driver. They've already upgraded to a PaperWhite or something better.
But there's a very simple reason that Amazon is cutting support for these. Many people (myself included--I have a 4th Gen still kicking around) keep one around because, after Amazon removed the Download option for Ebooks awhile back, having one of these old Kindles is the only way to download ebooks in a format from Amazon that can have their DRM cracked.
All Kindles newer than a certain date use the KFX format, with an encryption scheme that is constantly changing (basically any time someone figures out how to break it, Amazon updates it). Killing support for these old devices is basically Amazon's last step in removing "legacy" encryption schemes that can still be broken.
It would be the equivalent of Nintendo delivering a new firmware update for their Wii and Wii-U systems, in order to patch out a recently-discovered exploit. It serves no other purpose than to demonstrate the extreme contempt for Amazon's end-users and the lengths they're willing to go to combat user-freedom^W "piracy".
I disagree. There's no technical reason why they can't still work. They're perfectly good devices (possibly some needing a battery replacement). Why do we think it's ok to turn working devices into e-waste, because the company behind them needs to make a "business decision".
(Which in this case is likely DRM-related, which drops my sympathy meter below zero.)
14-19 years might be a respectable lifetime for a handheld electronic device, but in most cases (good care assumed) it is not a respectable lifetime for a book.
At some point they got ultra aggressive about "duplicate" questions.
Technology changes at a fast pace .. so new questions would get asked, and then closed by moderators and pointed to similar questions that might be 5 or 6 years old and no longer relevant.. essentially ending the discussion on many topics and actively preventing progress in certain areas.
Absolutely this. Later in the piece I learned that one of the mods in a place I'd occasionally asking questions on SO was from my local town and would occasionally attend industry social events. It was amusing to let a few people know and watch the "why did you close that question as a duplicate? That vendor module was only released 6 months ths ago but the duplicate was from 5 years back. Make it make sense!".
SpaceX made 8 billion in profit last year and xAI is losing 1B per month.
The whole IPO is convincing people that datacenters in space that are orders of magnitude more expensive than ones on earth is a financially viable business model and that tens of millions of people that already have internet are going to give up fiber for starlink.
A 6% overlap is hardly unifying.
The few Trump supporters I know think the whole thing is fake.
reply