Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)T
Posts
3
Comments
2081
Joined
3 yr. ago

  • This is already possible using an autounattend file.https://schneegans.de/windows/unattend-generator/ is fantastic.Use Microsoft's Media Creation Tool to create a windows installer USB, add the XML file to the root of the USB disk, reinstall windows exactly how you want it.

    (If you are feeling fancy, download the windows iso, and repack it with the autounattend.xml file in it, then drop it onto a Ventoy USB stick)

  • Please?

    Jump
  • Surely you can't be serious!

  • 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

  • But maybe they have the lowest crash rate?So like, crashes cost money right? Someone is responsible. Someone has to pay.But if everyone dies in an inferno, then nobody is responsible. Who can pay? They're all dead! What medical bills? What repairs? It's all a write off.Sounds like a high mortality rate with low accident rate is an absolute profitable win! Free market baby!

  • Mumble is fantastic.I designed and implemented a very complex voice system for an old guild. Like 100 people, 8 groups of 15, group leader's private chat, priority speech all that. It worked so well, and never failed.This was many many years ago, to be fair.I wish it's positional audio was more supported.

  • Radio stations playing their "push list" so that everyone hears the songs multiple times and eventually begin to like it.

  • Well, non-flammable vents for one thing

  • 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

  • However, the international response to Trump’s call for the dispatch of warships has so far proved vague and reluctant, with countries unwilling to commit to a military response that could prove treacherous for their navies.

    This is the correct response.

  • Yes

    (And all owls are superb)

  • When ctrl+v is disabled to "prevent brute force bots" or something ridiculous

  • Yeh, I have passkeys in bitwarden.I get it. Once they become ubiquitous, you click "login" your password manager prompts you to select account, and you are in.No password that can be leaked, incorrectly stored, brute forced.Corporations can pre-register company service passkeys for new users.It's like mTLS, except staged.

  • I only know how long bald eagles burn for.How do I convert microwave hours to bald eagle burn time (in number of football games including all dead ball times and the halftime shows)?

  • And then some kid buys a used raspberry pi or wipes an old computer and circumvents it all anyway.

  • So these "os reporting age bands" laws are useless then.Cause either the parents are being responsible, at which point there are many parental tools for network and device control.Or they aren't being responsible, and the kid can easily bypass it or just buy their own device.

  • So that means that kids can't buy computers?Can't buy a cheap used raspberry pi or old laptop/desktop in order to set up as a server?

  • It works out as O(regex^n)

  • Illegal: the strap on is unlicense

  • IDK. It puts them at the forefront of this fight.

    If governments successfully prosecute distro maintainers (if they can) for this, then distro maintainers are liable.And distro maintainers would then have to pursue non-compliant users to cover that liability, or fold.Which is a huge loss for open source.

    Or, there would be a huge legal fight and it turns out that the licence of a distro protects it from its users actions.Which would be awesome and a massive win. It also makes sense. Nobody is suing an OS maintainer because it was used for a data breach.And then the governments have to pursue the actual users. Which... is gonna be useless wrt these laws