• 0 Posts
  • 103 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle





  • Totally sensible requirement.
    TACO Trump has drastically altered tariffs and reneged on deals within this timeframe. Even previous military announcements have been reneged in this time.
    The US is unreliable.
    It could be 2 weeks, and would likely have the same safety. But a month makes sense.

    Only issue I can see is the absolute tension this will cause in oil prices and the stock market (and the new unregulated predictions market aka pure unregulated gambling with 0 actual net productivity).
    Imagine a massive bet against “the strait opens” 1 hour before trump declares & enacts further hostilities which breaks any truce and keeps the strait closed.
    Cause I’m pretty sure that shit has happened already, insiders know and can make “predictions” with impunity and bank big bucks.

    I don’t know the particulars of who is right & who is wrong in this.
    But Iran have found a big fucking lever they can actually pull, and are using it very wisely. Unlike nukes or projected power, Iran can actually pull this lever whenever they want and absolutely cripple international supply chains from food to microchips.


  • Yeh, it’s an http site. So any browsers that require https will block/warn.

    But also, holy hell is it obvious once you realise.
    Arms up, then swipe down out to the sides, and repeat. Like frantically trying to fly.
    As SOON as they are in trouble, it’s arms flailing in that pattern. Like, look for white splashing water and assess if it’s playing or panic.

    A few you can tell who it is gonna be because they flip off their donut. And a few you can tell cause they are trying to swim but are looking up and aren’t keeping their mouth above the water (I clicked on one of these to be told “it’s fine” only for them to start thrashing and get rescued when I resumed the video)


  • I’ll add that it works on a system of delegation.
    So there are authoritative servers (which own a part of a domain) which can then have actual records or delegate to other authoritative servers.

    So the authoritative server for “com” (yes, as in .com, com is technically a valid domain name) will delegate google.com to a DNS server (likely one owned by Google). And then Google will have DNS records for mail.google.com and so on.

    So looking up mail.google.com, technically you ask com DNS for the mail.google.com. It won’t have an actual record, but will essentially say “go talk to this DNS server to get google.com records”. So your computer asks this new DNS server for mail.google.com and it might have an answer, or it might have delegated the mail.google.com somewhere else.

    What your computer most likely is using, however, is a recursive DNS service. You ask it for mail.google.com and it will “walk the tree” to finally return the IP address.
    And then it will cache the results (for com google.com and mail.google.com) so the next queries are significantly faster.


  • Client -> Reverse Proxy -> Upstream Server

    It’s quite rare these days for a client (eg web browser, video game, phone app… anything that needs an internet connection, really) to directly connect to the server that is actually serving the request.

    It often goes through a reverse proxy which can direct the request to the “best” server (reverse proxies can have multiple upstream servers, either as a cluster that can share the load all dealing with the same service, as a bunch of different services, or both).

    This has a lot of benefits for service admins (at the cost of mild complexity), and has near-zero cost for clients.



  • That’s not a big financial incentive.
    Microsoft will remove stuff when it actually gets in the way.
    If it’s easier to leave in and not have to touch dozens of other programs/services then they will.
    They might mark it as depreciating, and start planning a suitable replacement. They might just mark it as depreciating and kick the can down the road.
    When enough services that relied on that depreciating thing have been touched due to other updates, then they might look at actioning the depreciation.

    But if it doesn’t actively break the thing they are currently working on, the cost overhead or ripping it out is insane.
    There might be other dev teams working on features that now rely/leverage the thing marked as depreciating. But the thing getting marked as depreciating happened towards the end of the other teams new feature development cycle. At which point actually depreciating the thing might invalidate that other teams entire project.
    And maybe the rip it out, and it turns out one of their large clients (or a large amount of the user base) was relying on it.

    Addressing technical debt is always hard to justify, but it always makes a better project.
    If management doesn’t care about a better project, they will prioritise features and things that make money



  • Never used librewolf.
    But it sounds like the conveniences you want are a compromise for fingerprinting.

    Don’t let perfect stand in the way of good.
    The internet has been significantly ruined by large companies.
    There is a loop where companies with the resources to create and maintain frameworks/tooling/whatever are large enough to help define “features” for browsers.
    Browsers don’t make money, not really. To even be considered, they have to be able to run what the big companies are pushing.
    All of this makes it very easy for smaller companies to deliver better websites. Or abuse the features big companies are pushing.

    It’s like: email was awesome, then spam emails happened. Websites were accessible, then SPAs happened. Search engines were useful, the scraping/AI happened.

    I don’t know what I am trying to say.
    Other than browsers do not get the support they deserve to actually be decent unless they are backed by a company that wants to loss-lead them… Which has resulted in the web being pretty fucked