Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S
Posts
17
Comments
313
Joined
3 yr. ago

I'm just this guy, you know?

  • Not that I'm a fan of Ubuntu here (I generally don't run it when I can run anything else), but I do want to say I think you've missed the point of the Pro tier.

    Ubuntu releases two stable versions a year which are supported for 2 years or so. This is like a slow rolling distribution, and makes the newest software's available. It receives regular security updates from upstream, from Canonical, and from backports, again for up to about 2 years. Most users install this version.

    Ubuntu LTS editions are similar to the above, but receive all the same security updates for 5 years instead of 2. These distributions are generally targeted for Enterprise users who value stability over having the newest software, and for whom upgrading comes with significant time, expense and risk. The 5 year window is customary among other distros, and is largely supported by and throughout the Dev community.

    Ubuntu LTS Pro editions extend the LTS support editions for an additional 5 years, meaning a Pro distro enjoys 10 years of security updates from upstream, backports, and from Canonical where needed. Canonical might even open source their fixes back into upstream for other maintainers and distros to use, depending on the situation. However, since Canonical is providing the work, they charge subscription fees to cover their costs for it from their target audience: Enterprises who can't or REALLY don't want to upgrade

    Why an Enterprise might not want to upgrade has to do with risk and compliance. Corporate IT security is a different world, where every bit of software may need to be reviewed, assessed, tested and signed-off upon. Major software upgrades would need to be recertified to mitigate risk and ensure compliance, which takes significant time and expense to complete in good faith. Not having to do it every 2 or 5 years is money in the bank, especially when the environment doesn't introduce new requirements very often.

    Canonical is meeting a market demand with their Pro tier by allowing these customers to spend a fraction of their recertification costs on a software subscription. It's overall good for the ecosystem because you have what amounts to corporate sponsors pumping money into keeping older packages maintained for longer. This let's them keep using the same software distro all the rest of us can use for free.

    I'm not shy about calling bullshit on ANY distro that operates in bad faith, and they all get into some BS from time to time. Nevertheless, Canonical are acting in good faith on this, and are merely collecting money for their time and skill to provide maintenance on FOSS packages that might otherwise go unmaintained.

    tl;dr: Pro tier is for Enterprise customers who need extra-long term support and are willing to pay for it. Canonical is meeting a market demand so they can remain competitive for use in those environments, which is good for everyone. It's benign. Keep the pitchforks sharp and the torches dry for another day.

    edit: typos

  • That thing has been at or past 5 minute to midnight my entire life. Can't live your whole life in fear.

    Yeah even you, Boomers.

  • I do now. See edits upthread.

  • Yes understood. See edts up thread

  • edit: The following is off topic, but I'll.leave it as a testament to my gray-beardedness. In my defense: Unity isn't Unity anymore. Don't get old.

    I've been using Linux for 30 years now, and for a while I was an advocate for Ubuntu and Canonical (among others, I'm pan-distributive). Then things changed: GNOME 3, Wayland, Unity, something-sonething, Snaps... All too much.

    As an advocate, I'm apt not to emerge with favorites, or to yuck others' yums. Neverthekess, Canonical is a press beyond the pale, many days.

    In the end, I don't recommend Canonical distros. LMDE is solid, as are most of the *bian and redhat downstreams. I don't recommend the others because I don't know them, but more importantly I couldn't help a friend un-bodge a bad installer on them (likewise for "BSD or Darwin).

    But really, no love for Canonical. They went to some Dark Side, and I'll have a hard time forgiving them for it.

  • I think the i5 is Ivy Bridge, but I couldn't tell you what gen that is. My main use of HA aside from the automation is Frigate, which apparently needs the hardware AVX flags. This chip supports AVX512, where my older AMD did not, so that's why I went with it. Its an i5-3470T, if that helps.

    For an older SFF unit, it's a beast for HA.

  • I've got HA with Frigate + USB Coral w/4 cams, FlightRadar24 receiver/feeder, ESPHome, NodeRed, InfluxDB, Mosquitto, and Zwave-JS on a refurbished Lenovo ThinkCenter M92p Tiny, rigged with an i5 3.6GHz, 8GB RAM and 500GB spindle drive. It's almost overkill.

    Frigate monitors 2 RTSP and 2 MJPEG cams (sometimes up to 3 RTSP and 5 MJPEG, depending of if I'm away for the weekend) with hardware video conversion. FR24 monitors a USB SDR dongle tracking several hundred aircraft per hour. I live under one.of the main approaches to a major US hub.

    Processor sits at 10% or less most of the time, and really only spikes when I compile new binaries for the ESP32 widgets I have around the house. It uses virtually none of the available disk. It's an awesome platform for HA for the price.

  • Their Mist platform is one of the better management panes of glass out there. The analytics engine for wireless diagnostics is quite comprehensive. Better than the Aruba offering, at least.

  • I just wanna know what brand of phone case was on that phone.

  • If it's a gas burner then it produces CO2 as it operates, right? You could probably mount an ESP32 kit with a CO2 sensor (SGP30) and passive infrared receiver (AM312) over the range to monitor the CO2 level, and also whether anyone is standing at the stove. I didn't check to see whether these modules were supported directly by esphome, but I'm sure the project either has a compatible module, or you could adapt something from the project to support these modules.

    You could then program HA to alert if long term CO2 is elevated and no motion is detected at the range for some time.

    Just an idea. I might try tinkering with something similar this weekend. I don't have the gas sensor, but I've been looking for an excuse to order one

  • I've been using the Sendled Sengled E11-N1EA bulbs available on Amazon for quite some time now. They have a bit of a cold white edge to them and could maybe be a bit brighter at times, but overall I've been happy with them.

    Mine came in a 4-pack. I have two inside in table lamps, and two outside in coach lamps.