• 1 Post
  • 393 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle



  • The cheap Chinese stuff often uses knock-off ICs tho.
    They can be fairly difficult to detect, and will work for a short time or under very light loads. But they will be nowhere near the spec of the data sheets.
    They might massively overheat, not provide the correct currents or voltages, run at lower speeds. All sorts of corners being cut to turn a $2 IC into a 50¢ IC. Or a 50¢ ic into a 5¢ one

    So yeh, might be the same PCB layout inside, it might visually look the same (or very very close) but the parts are likely to be counterfeit.

    Of course, it’s also probable that name brands might be hit with counterfeit parts inside as well. Hopefully their QA picks that up




  • Because “trickle down” economy was somehow thought to be legit.
    Like, the rich get loads of money, so they do big things to make jobs.

    Except they don’t.

    Rich people hoarde wealth, and pay people to ensure they don’t have to pay taxes.

    Rich companies increase profits, which is about the sole metric of a successful company (and when a metric becomes a target, it fails to be a metric). Then they try to keep increasing profits by cutting costs.

    Oh, and wealth hoarders then bet on companies ability to constantly increase profits.



  • You can do reverse proxy on the VPS and use SNI routing (because the requested domain is in clear text over HTTPS), then use Proxy Protocol to attach the real source IP to the TCP packets.
    This way, you don’t have to terminate HTTPS on the VPS, and you can load balance between a couple wireguard peers so you have redundancy (or direct them to different reverse proxies or whatever).
    On your home servers, you will need an additional frontend(s) that accepts Proxy Protocol from the VPS (as Proxy Protocol packets aren’t standard HTTP/S packets, so standard HTTPS reverse proxies will drop them as unknown/broken/etc).
    This way, your home reverse proxy knows the original IP and can attach it to the decrypted http requests as x-forward-for. Or you can do ACLs based on original client IP. Or whatever.

    I haven’t found a way to get a firewall that pays attention to Proxy Protocol TCP headers, but I haven’t found that to really be an issue. I don’t really have a use case








  • Starting with a pool of all users who use alternative DNS for any reason, users of pirate sites – especially sites broadcasting the matches in question – were isolated from the rest. Users of both VPNs and third-party DNS were further excluded from the group since DNS blocking is ineffective against VPNs.

    Proust found that the number of users likely to be affected by DNS blocking at Google, Cloudflare, and Cisco, amounts to 0.084% of the total population of French Internet users. Citing a recent survey, which found that only 2% of those who face blocks simply give up and don’t find other means of circumvention, he reached an interesting conclusion.

    “2% of 0.084% is 0.00168% of Internet users! In absolute terms, that would represent a small group of around 800 people across France!”

    I wonder how much the court case cost, and if those costs are in anyway likely to be recouped even if all 800 of those convert to a subscription.




  • Yeh, immutable distros… You can install software, it’s just you have to declaratively define what software you want, then apply that as a patch.
    You don’t just apt install cowsay, you have to create a file that defines the installation of cowsay.
    This way, if you have to change how cowsay is installed, you tweak that patch file and reapply it.
    If you have to wipe & reinstall (or get a new computer or whatever) you just apply all your patches, and the system is the same again.