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/)ON
Posts
15
Comments
228
Joined
2 yr. ago

  • My parents drink mediocre pre-ground coffee. I left a single-cup French press at their house so I can have better tasting coffee whenever I visit. It doesn't require advanced prep like cold brew.

  • It's interesting that the glass is still full of beer. Presumably its contents must have all been accelerated at an identical rate, or else they would have spilled across the cosmos.

    Did it emerge, fully-formed, from the primordial energies of the big bang, or is it a probe sent by alcohol-based life forms?

  • Despite what the length of their privacy policies might suggest, first party sites are a lot stingier with their user data now than they've been in the past. The value of knowing who someone is and what they want is derived when you convince them to pull out a credit card, at which point you need to collect their data anyway.

    Thus, I think we'll see two tiers of data collection: Deep first-party info shared between retailers and data brokers to target advertising on their first party site, and less granular banner advertising based on privacy sandbox, taking the place of drive-by cookie drops. If privacy sandbox is as good for random blogs as industry is expecting (ie, not as perfect as third party cookies, but less impactful than Apple's ITP was), I don't think we will see a wave of email signups.

  • I don't quite understand the leap from "No third party cookies" to "You need to create an account".

    If you're visiting a site and they drop a cookie, that's a first party cookie. You don't need to log in for that to happen, and they can track you all the same. Taking identifiers from a first party cookie and passing them to advertisers will still be a thing, it'll just require closer coordination between the site and the advertiser than if the advertiser dropped their own cookie.

    Now yes, that first party cookie won't follow you around to other websites and track your behavior there, but creating an account wouldn't enable this anyway. Besides, Google's Privacy Sandbox product suite is intended to fill this role in a less granular way (associating k-anonymized ids with advertising topics across websites).

  • But the emperor isn't paying for this circus. The plebs are. The Superbowl is not a loss-leader to keep the poors from rising up, it's a profitable enterprise that keeps generating wealth. The money is what keeps it going, not some plan to keep people down.

    I fucking wish it were bread and circuses. Except instead of bread I'll accept healthcare, and instead of circuses we get cable news.

  • Rest of the sentence (emphasis mine)

    This ridge was climbed by a Polish expedition in 1983 using fixed ropes while making the first ascent of 7,531 m (24,708 ft) Batura V and VI

    They ascended the Batura VI peak next door, which I guess happens to be almost as tall as Muchu Chhish (Batura V). Interesting that the wiki article claims they ascended Batura V and VI, but their linked references by the American Alpine club says it was Batura IV. Probably a scrivener's error, since 7,531 is the height of Batura VI.

  • Sorry, what's .Net again?

    The runtime? You mean .Net, or .Net Core, or .Net Framework? Oh, you mean a web framework in .Net. Was that Asp.Net or AspNetcore?

    Remind me why we let the "Can't call it Windows 9" company design our enterprise language?

  • I guess it would depend on whether or not the project spawns a dedicated community that lasts for a long time. Without a wide pool of knowledgeable contributors, I think it would be hard for an original team to both support the one design while also developing the next iteration.

    Not to bring it up as a whipping boy, but let's take the case of Wayland, which is "just" a software protocol. It was started back in 2008, and is still under active development. As more projects support it, more edge cases are coming up, which is why new features are added to the protocol all the time. In those 15 years, they've had to adjust to technologies that didn't exist back in 2008, like widespread adoption of 4k HDR displays, or Vulkan. Now imagine that, but with every aspect of a computer. In 2008, DDR3 RAM was just a year old. Today we're on DDR5 and you (probably) can't buy a new machine that takes DDR3. PCIE 2 was the latest shit in 2007. Now I see that PCIE 7 is planned for next year.

    A global corporation can support old products while also developing new technologies because they have unfathomable labor and capital at their beck and call.

    I think that free software can keep up with proprietary offerings because the barrier to entry is relatively low. You just need free time and a source control client. I think it would be different if your project toolchain involved literal tools that cost millions of dollars.

  • I think because such an undertaking would require a wide breadth of extremely specialized knowledge. It would require intense coordination of many experts to work together over many years, all to design something that:

    1. Will eventually be obsolete within a few years
    2. Is outside the realm of replicability for individuals (I never heard of anyone with a nanometer-scale photolithography room in their house)

    Item 1 is OK for hobbyists, who might value open source over new-ness, but item 2 all but guarantees that only big corporations can actually get involved. They don't care about free and open source. They just want a computing platform that their engineers can develop a product for. As long as there's enough documentation for their goals, open source is irrelevant.

    The power of modern computing comes partly in how it enables abstraction. You don't need to understand the physics of electrons through a transistor to write a video game. Overall, the open source community has generally converged on the idea that abstracting away the really hard stuff is an acceptable tradeoff.

  • Firstly, discord is entirely the wrong medium for documentation.

    Secondly, documentation should be at least as accessible as the code. That is to say, if I can view the code without creating an account for some service, then I should also be able to read the documentation too.

  • What are people's thoughts about the children's size urinal? Never use it if there's another option? Only use it if the other option would place you adjacent to another person? What about if you have a choice between adult and child's urinals next to each other, but using the child's urinal would allow space for another person to optimally avoid neighboring persons?

    I feel like this is a variant of the trolley problem that's woefully unexplored.