Ubiquity only did passive PoE in the very early days. Everything has been 802.11 variants for a long while wow. The injectors that shipped a decade ago with my APs were all 802.11af.
The UniFi line has moved away from passive PoE. The "UISP" line is almost exclusively passive PoE, even for brand new products. Ubiquiti has proven they know how to make devices that support both when they transitioned the UniFi line, but they actively choose not to and to enforce the use of bad nonstandard trash with their new products in their ISP product line.
The majority of UISP devices they sell are all relatively old products. For example the 'NanoStation 5AC Loco' is a great $50 product that continues to work well, but it was released in ~2019. And they continue to sell new models of products that have been unchanged for over a decade.
In the last 2 years they've released very few new UISP products and you're right that they continue to be passive PoE. I suspect this is for continued compatibility with their older product line. Upgrading from passive PoE to active 802.3 PoE requires replacing the injector and maintaining passive PoE makes it easier to upgrade. And the UISP product line is really meant for wireless ISP operators, not consumers, where the risks of passive PoE are smaller.
Anyway, I agree with the sentiment, but I don't hold it against Ubiquiti too much for continuing to use passive PoE for their UISP line, since I think it makes sense for their customers. As so-so work around you can get a 802.3 -> passive 24V converter: https://store.ui.com/us/en/products/ins-3af-i-g
> And the UISP product line is really meant for wireless ISP operators, not consumers, where the risks of passive PoE are smaller.
I'm afraid that's not how it works out in actual practice, it's the other way around:
WISP devices are installed in random people's windows, roofs and chimneys. The injector might end up behind their TV set. If their TV doesn't work, they unplug and replug random things. Which will fry whatever has the unlucky pleasure of ending up on the output side of the injector. I'm unfortunately speaking from experience.
Meanwhile, people buying and putting up a wifi AP beyond their CPE wifi router tend to have a bit of understanding. If you told them to never plug anything other than the given device into the output side of an injector, it'd probably go reasonably well.
What about MiniPCs that support serial console or network connectivity for BIOS / UEFI access? When I looked for a new router, I couldn't find any of the usual "cheap" suspects that supported that. As well, most didn't have anything better than 1 GBit network ports.
I ended up going with a more expensive mini-PC style vendor, but I was surprised there didn't seem to be a ton of competitors.
I was a paying Pocket customer until a few weeks ago. I switched to Wallabag plus https://gitlab.com/anarcat/wallabako/ to sync to my Kobo. It's not polished, but honestly neither was Pocket with their decline in both article parsing and the iOS apps over the last few years.
Hopefully this situation encourages more contribution and improvement to tools like these.
Worse yet is when banks tie authentication notifications to the ability to send you marketing and advertising permissions. My bank's app was sending me weekly marketing messages, and the only way to stop that was to go back to SMS 2FA.
I wish Apple (and Google, I presume) would actually enforce their app store guidelines and at least threaten to ban apps that do this. That seems like the only thing that'd actually have traction.
Are there any ways to do some sort of upscaling for HiDPI displays? I’ve always wondered what MacOS 8 or 9 would feel like with 2x retina style rendering.
> I’ve always wondered what MacOS 8 or 9 would feel like with 2x retina style rendering.
I'm not sure what that would even mean. Most of the UI was drawn from bitmaps - there isn't any higher resolution internal representation of e.g. a window border or a radio button.
What it would mean is something like hq2x, 2xSaI or similar. These algorithms are popularly for emulation of 8 and 16 bit era games consoles. The example image on this Wikipedia page is illustrative of what's possible with a deterministic algorithm:
Imagine what could be possible with a well trained neural network, with knowledge of every icon, every element, and every font glyph at every bitmap size.
This looks to have the effect of increasing the number of PHP versions projects wanting broad adoption of will have to support. Assuming PHP 8.4 comes out at the end of the year, in January libraries will need to support PHP 8.1 to 8.4.
I think that's mostly OK, but I'll be curious to see if other projects like Laravel or Symfony keep to a shorter PHP version support window just to keep support costs down.
