• 1 Post
  • 40 Comments
Joined 2 years ago
cake
Cake day: May 18th, 2024

help-circle


  • AI Summary

    Title: Be Suspicious of HDMI

    • HDMI technology is criticized for being a “money pool” for companies, despite the existence of better, royalty-free alternatives.

    • Companies developing HDMI technology charge significant annual licensing fees and per-unit costs for using the HDMI name and logo.

    • Additional features like HDCP require extra payments on top of existing licensing and unit costs.

    • HDMI actively sponsors tech news articles to promote itself.

    • DisplayPort is presented as a royalty-free alternative that offers similar or superior functionality to HDMI.

    • DisplayPort supports more features, higher resolutions, and higher refresh rates compared to HDMI.

    • The Steam Machine exemplifies the issues with HDMI, featuring a DisplayPort 1.4 connector capable of 4K 240 Hz.

    • The HDMI connector on the Steam Machine is HDMI 2.1 capable but cannot be advertised as such.

    • The HDMI organization does not license HDMI 2.1 for Linux devices, forcing Valve to label it as HDMI 2.0.

    • There’s a call for the display industry to transition away from HDMI to less expensive and more open standards.







  • I know I’m not exactly hitting the mark, have you looked at kagi? You can personalize the weighting of results from certain sites. You can also add lenses which will let you drive results to forums, programming, academia, etc.

    To me it was a bit like reliving the early days of google with the don’t be evil mantra still in tact.

    Let me also say, it appears to be privacy respecting.

    It has been good for me so far. If someone sees a reason I should run away from this, please let me know why and what we all should use instead, I’d appreciate it!




  • My biggest concern with these forks, is do they get the security updates quickly enough as they’re all downstream from either Chromium, Firefox, or web-kit. I’ve tried Zen a bit and had a good experience. From a privacy perspective, cookie management, containers, anti-fingerprinting, and telemetry are probably the biggest categories to address.

    Again, I always have security concerns for the forks getting patches quickly. The smaller the team the more risk likely in this category. Librewolf won my vote. I use it for almost everything. If the page won’t work there, I typically have to use Chromium because the site is just poorly built.

    I’d also recommend doing something to manage privacy at the DNS level for your local network/machine. Piehole or NextDNS would be a good place to start. I landed on NextDNS as it’s pretty cheap, easy, and stable. With internet, it has to “just work” or the family gets annoyed fast. I can still black-hole traffic from my network that is phone-home telemetry from devices more concentrated on collecting info for the manufacture than doing what they were purchased to do.