• 0 Posts
  • 99 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




  • 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.




  • Ear buds where the cost goes to quality and isolation as opposed to gimmicks/Bluetooth/functionality.
    Airpods are amazing for casual use.
    IEMs (with a cable, of course) are amazing for music.

    It’s what musicians use on stage to hear what everyone is doing (iems and individual mixes are so accessible these days, used to be super $$$$ per iem mix).
    They range from budget (1 driver per bud) to decent (3-5 drivers per bud) to esoteric (like 16 drivers per bud).
    Most have modular cables that disconnect at the earbud (so when the cable breaks you are paying thousands for a new set. Or to get custom cable lengths).
    And all decent brands can be custom moulded to your ear, so you go to a hearing specialist, they will cast your ear, and you send that to the manufacturers and they will send you moulded IEMs. They are very comfy.
    Some brands have a DIY moulding process, but I wouldn’t trust myself!

    If you are into live music & loud gigs, even loud clubs, I really strongly recommend you get a moulded set of earplugs with 10db attenuation. They are for musicians and have as flat a response as is possible, and will take the edge off any hearing damage.








  • It’s not a workaround.
    In the old days, if you had 2 services that were hard coded to use the same network port, you would need virtualization or a different server and make sure the networking for those is correct.

    Network ports allow multiple services to use the same network adapter as a port is like a “sub” address.
    Docker being able to remap host network ports to containers ports is a huge feature.
    If a container doesn’t need to be accessed outside of the docker network, you don’t need to expose the port.

    The only way to have multiple services on the same port is to use either a load balancer (for multiple instances of the same service) or an application-aware reverse proxy (like nginx, haproxy, caddy etc for web things, I’m sure there are other application-aware reverse proxies).