Em Adespoton

  • 0 Posts
  • 89 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle
  • That means the British Indian Ocean Territory will cease to exist, along with the .io domain and countless websites.

    What will happen is that the International Standard for Organization (ISO) will remove the country code “IO.” IANA (Internet Assigned Numbers Authority) which creates and assigns top-level domains, uses this code to determine which top-level country domains should exist. Once ‘IO’ is removed, IANA will start the process of retiring .io, which involves stopping new registrations and the expiration of existing ‘.io domains.‘

    I don’t get this: shouldn’t Mauritius gain ownership of .io? Russia has .su, and it’s been over 30 years since the Soviets existed.

    [edit] also, since there’s .whateveryouwant these days, why not just make .io a non-country TLD? That’s how it’s used anyway.


  • I feel your pain. I have maintainer roles for a few projects where things could be slowed down by a week or more if I didn’t have direct commit access. And I do use that access to make things run faster and smoother, and am able to step in and just get something fixed up and committed while everyone else is asleep. But. For security critical code paths, I’ve come to realize that much like Debian, sometimes slow and secure IS better, even if it doesn’t feel like it in the moment (like when you’re trying to commit and deploy a critical security patch already being exploited in the wild, and NOBODY is around to do the review, or there’s something upstream that needs to be fixed before your job can go out).






  • I’m confused: Kaspersky just finished transferring its endpoint security software in these regions to a different company’s product via a software update. Kaspersky has sent messages out to customers saying that they are leaving this marketplace.

    Given this context, I can see no reason why Google would leave their Android product available when they’re not technically allowed to sell it and Kaspersky has said that they won’t be selling it into these markets going forward. It does, of course, prevent Kaspersky from pulling another bait and switch and “updating” mobile devices to a third party product. That would be the reason for locking out the developer accounts.






  • Yeah; just set your article to 2x speed :D

    I kid; all this video is going to vanish one day, and the text will remain.

    And for most things, text is a highly superior format. Sometimes you need a few images or a video clip to supplement it, but I like to ingest information while my ears are otherwise occupied. I keep my phone and computer muted most of the time. I often watch videos with closed captioning enabled on 2x just to scrub through and find the 10 seconds of actual information in the 15 minute video.



  • You know those “do not lick the flagpole” signs?

    They’re not there because the building owners think YOU will lick the flagpole. They’re there because someone else already HAS licked the flagpole.

    MS adds these things because there is legal consequence to them allowing certain groups to use their software. So they explicitly call out that those groups cannot legally use their software.

    That way if an Iranian arms dealing pedophile is caught using their software, Microsoft doesn’t get sanctioned by the US government.


  • Yes, at the point where the only thing hindering free software from running on a device is the policies of the organization SELLING the device, it should be the policies that change, not the ability of software to remain free.

    I choose iOS because of the walls, but I also sideload software. That sideloading is limited in the number of products I can sideload at a time, and it requires a sync connection with a computer. I kinda sorta agree with Apple’s restricting of sideloaded software to a limited number of apps, but the computer/XCode requirement could easily be solved in other ways.

    The goal is to make it difficult to trick someone into installing a malicious payload; Apple should allow individuals to self-sign software and run it in a sandbox— just like they do with Progressive Web Apps.

    I mean, if I can download and run a PWA of a Palm emulator from a web page, why can’t I do the exact same thing with the same levels of protection with a native app? Only thing stopping me is an Apple App Store policy.