With notifications disabled APNS push notifications fail for the sending app backend. The device id is rendered invalid if push notifications are disabled at any point. Backends are supposed to handle this and quit sending messages.
Signal has this setting to tell the backend how much information to put into the push message. It can tell the backend to send a simple notification saying “new message” and not send information through APNS or enable it.
I am willing to bet Signal has a notification extension to handle edge cases where there is lag in settings to scrub the message metadata before it dings a screen alert.
EME has been made a bit more affordable and effective by weak signal modes and DSP.
It used to require very high power, expensive transmission lines, preamps and monstrous arrays of Yagis. Now with JT65x, and SDRs, you can use cheaper coax to get transmit power to the antenna eating that loss with more RF, and put SDRs for RX at the array. People running digital modes are getting away with needing less gain.
5650MHz is the only place to do it with this thing. Might want to break out a calculator before the credit card because path loss has to be more than 285dB. But if you can swing it, might want to buy two so you have someone to talk to. I have not heard anyone using 5650.
The backlash is from Meta trying of assign liabilities of their business practices on people who may not even be users.
Yes, this is just the beginning of a huge swath of innocent APIs to identify people on the internet. Meta isn’t going to stop, and neither will governments.
I think those boomer firms are asleep at the wheel and this kind of market engineering will completely blindside them. Vanguard can't even figure out how to show me my cost basis on the same screen as the one where I sell a security. What could they possibly be doing to prepare for this?
You are correct, but the problem was the PC only had 16 IRQs. That required using intelligent multi-port cards from Digi or Rocketport. They worked by aggregating all the ports to a single card IRQ, and managing all the hardware signals, echo.
I wrote the software for a breakout box that could handle 128 serial ports. It was an ISA backplane with an industrial 286 computer and multi-port serial cards. This was our solution for a MajorBBS system.
The BBS software would have to timeslice between all the cards handling each IRQ, then poll the card details to see which ports needed service.
GalactiComm eventually came out with their own around 1993 that could go out to 255 serial ports and did not require the 286 processor.
By the mid-90’s, Livingston PortMasters were the preferred way to aggregate serial connections, which quickly gave way to USR TotalControl.
You are not wrong, except at scale it gets complicated quickly. For starters, to support large user numbers, you’re going to have to process your own grib2 data for radar and turn them into tiles at zoom levels.
It takes about 24 cores with a GPU to do CONUS, Canada, Alaska, Pacific and Caribbean data. This should be 2x for redundancy. Even being cheap with main processing in my basement (gen power, backup internet) the cloud costs to serve it are $200 month plus data transfer. The standby grib machine spins up should it not see the cheap primary or the NOAAPort receiver is offline.
There is no money to be made without whoring out your user’s privacy. People just won’t pay for a privacy focused weather app. I keep this going as a hobby.
Fair enough. Things are always more complicated at scale.
But then again, we don't know whether this company is maintaining this infra themselves, or if they're paying for API access. Besides, if anything, running their own servers is often the more cost-effective option, so the details you mention might not matter in practice.
My incredulity has more to do with the profitability of this type of software, considering that the free options are good enough for the average person, and that the features promoted in the article are hardly innovative.
> There is no money to be made without whoring out your user’s privacy.
Well, I do object to that. It's certainly possible to sustain a profitable business without selling out your users' data. It may not be as profitable as the advertising model, which is often too enticing for companies to ignore. This company explicitly says that their income comes directly from customers, so apparently I'm underestimating the amount of people who find these features valuable enough to pay for them.
In my experience, most people with cancer that I know simply oscillate between having life-threatening active cancer/tumors and remission.
I don't know any case where people have detectable cancer and it's just being managed, I think that's more the exception than the rule.
For my girlfriend, when she was in her last stages they had to do that (try to slow down/manage the cancer instead of remove it), but that was already palliative care and she died soon after. Also, the only reason they didn't try removing the tumor is because the specific location in the brain (pons) is inoperable.
Signal has this setting to tell the backend how much information to put into the push message. It can tell the backend to send a simple notification saying “new message” and not send information through APNS or enable it.
I am willing to bet Signal has a notification extension to handle edge cases where there is lag in settings to scrub the message metadata before it dings a screen alert.
reply