> For my needs unifi was worth it to not have to deal with OpenWRT again...
Amusingly, I was quite willing to put up with a day or two of tinkering and puzzling over the -occasionally godawful- docs to never have to deal with Unfi and the rest of UBNT's software ever again. Even my recent move from my OpenWRT-"powered" UAP-LR/LITE to my OpenWRT Ones required only a little bit of fussing with the configs I copied over from the -LR and -LITE... and that was because of the difference in device names between the UBNT hardware and the One hardware.
One of the first things I look for when trying out software is the "Updates" toggle. If it doesn't have a way to disable them, most of the time I'll go look for another option.
I'm on Zen which is still on FF 150.x right now, and I laughed a little when going to the Adafruit demo page and it says "Sorry, Web Serial is not supported on this device, make sure you're running Chrome 89 or later" across the top without any mention of Firefox 151
It's closed source and chromium based, it's also really ugly looking IMO. The Android version also doesn't support addons so that's a huge fail. I'll stick with Zen.
But really any service (or even on-site hosting) can have downtime, if that's not acceptable then I suppose building/using a tool that can be distributed between multiple hosts located in different geographical areas is the best option.
I've been noticing this type of thing a lot lately, updates that plain don't work because of bugs that would have been caught with any testing, installers that don't work at all..
It's like coding with AI and not testing anything go hand in hand, which I do not understand.
Sometimes the people who set up the email service just forget or don't bother to add the receivers email to the URL parameter when you click unsubscribe, so it'll ask for your email again which is always an annoying step.
I refuse to believe that “someone just forgot” to implement a user-friendly feature whose omission coincidentally benefits their company. It is not a coincidence, and it was not done unintentionally. The same way that it is not a coincidence that the “unsubscribe” link is always in six-point font the same color as the rest of the email footer. Code does not happen in a vacuum. Code does not get pushed to production without vetting and approval. As I say, the assumption of bad faith is baked in.
There are plenty of dark patterns in digital marketing, and you're generally right about the thinking.
But there is a (somewhat plausible) defense here: if someone forwards you an email and you hit the unsubscribe link, then it unsubscribes them; not you. Requiring the user to enter their email helps ensure you don't accidentally unsubscribe the wrong person.
That said — the most impactful thing anyone can do to punish dark pattern digital marketing behavior is to report the message as SPAM in your email client. That'll hurt their delivery rates and damage their sending reputation with email providers.
> But there is a (somewhat plausible) defense here: if someone forwards you an email and you hit the unsubscribe link, then it unsubscribes them; not you.
Pre-filling the address in the field is easy and prevents that. But if I get redirected to an empty address field, I immediately close and mark as spam. I refuse to reward that behavior.
Depends on the type of LiFePo4 cells, ones designed for higher power can easily do 5-10C or more. But that's not needed for a UPS. Most common high energy cells can handle 3C.
3C or 20 minutes of runtime would be in the realm of most UPS ratings (remember the LiFePo4 cells have a lot more energy/runtime in the same space).
For my needs unifi was worth it to not have to deal with OpenWRT again, or worse, stock firmware on consumer APs.
reply