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/)AB
Posts
0
Comments
1,096
Joined
2 yr. ago

  • I don't know what it's like where you live, but where I live rent in the city works out to about two thirds of my annual income and I have a well paying job (above average for my city).

    So - living in the suburbs is not really a life style choice. I can afford a very comfortable home in the outer suburbs, while in the inner city I could only afford to rent a small bedroom with a shared kitchen/bathroom/living space. And since we have a child, a share house isn't really an option (I did live that way when I was younger).

    And while I love cycling to work I can't do it often, because it takes almost 4 hours (two hours each direction). I can take a bus, but that's even slower (since I have to go to the CBD first, then take another bus across town to the non-CBD area where I work). The bus also costs more than twice as much as driving. Driving, by the way, takes 30 minutes.

    Since I live in the outer suburbs anyway, with nice wide roads, unlimited free parking, I choose to take advantage of it by spending a lot of time outdoors where if you want a cold beer, you need to bring a fridge. If you want a hot meal, you need to bring a full kitchen. If you want to take a canoe out the water, you need to bring a canoe with you, etc etc. So, we have an SUV. And we're not going to give it up. Sorry.

    If my city banned SUVs, I'd probably just start taking taxis instead. I'm not sure that would be better for the environment or local traffic. Definitely wouldn't affect my daily life, since I don't live or work in the CBD.

  • From the article, 79 million IPv4 addresses

    So that's how many IPv4 addresses Amazon has? For comparison, if I ask my server provider nicely they will give me a huge block of IPv6 addresses. For free. The largest block they will give a single customer (again, for free) is a /56 block which is 4,722,366,482,869,645,213,696 IP addresses.

    To give you an idea how big that is... if I had ten billion customers, I could allocate several hundred billion unique IP addresses to each customer. And that's just with a section of the IPv6 address space that networks will hand out for free.

  • it’s just never used or enabled in the software by default

    ...and most people who own those devices have never heard of IPv6 and don't know how to enable it. They just won't be able to access your website. If Amazon dropped support for IPv4, there wouldn't be anything i'd be able to do to deal with the fall out. I'm not going to send a technician to every single home of every customer I have. What I could (and would) do is move all my stuff off Amazon.

  • a lot of sys and net admins really don’t like the idea of every lan device being globally addressable

    Those admins don't know what they're talking about. IPv6 has a region of the address space that can only be reached locally - similar to the 192.168.x.x space in IPv4. The only difference is it's really big (way bigger than the entire IPv4 space).

    As for NAT... there's nothing stopping you from using it with IPv6. It's often unnecessary, but if you disagree you can use it. And in practice NAT is often part of the transition process to IPv6 - my cell network carrier for example gives my phone an IPv6 address on their internal network but routes all my traffic to the regular internet via IPv4. They are using NAT to do that. If you try to ping my phone's IPv6 address, it won't reach my phone.

  • IPv6 is here, and has been for a long time. But if, for example, your web or email server can only be reached over IPv6 some people will not be able to load the site or send emails to you.

    The entire internet is configured to work with IPv4. Some of the internet (less than a quarter) is also configured to also work with IPv6.

    Imagine if your home had two driveways on different streets. Do you tell everyone both addresses, or do you pick one of them? Probably just one right? Now imagine if the second address can only be reached if someone has an off road capable vehicle. And you don't know what vehicle someone has - which address would you give them? Is it even worth having two driveways?

    That's the situation we're in. IPv4 support is required and works perfectly. IPv6 is optional and doesn't always work.

  • Pkl is a hell of a lot easier to work with. Compare this pkl code:

     
            host: String
        port: UInt16(this > 1000)
    
    
      

    To the equivalent in json:

     
            {
          "$schema": "http://example.org/my-project/schema#",
          "type": "object",
          "properties": {
            "host": {
              "type": "string"
            },
            "port": {
              "type": "number",
              "minimum": 1000,
              "exclusiveMinimum": true
            }
          },
          "required": ["host", "port"]
        }
    
      
  • The biggest advantage is IDE integration.

    You can type port = 42 and instantly be told, right there as you edit the file, that you entered an invalid value (port has to be at least 4 digits). It will also flag prot = 4242 as invalid — catching the typo. That's a real advantage - just last week I took a server offline by making a human error in a config file. The server just didn't respond to network requests after the change was applied and it was part of a larger deployment... so it took time to find the mistake. Catching mistakes early is a good thing.

    The second big advnatage is integrated documentation - for a lot of work you won't need to read the manual in a web browser. You can just jump into the config file, hover your mouse over something, and know how it works.

    It has other strengths, but those are the big two. Probably the third is it's just a nice language to read and write (plenty of other options share that, but it's hardly universal).

    I looked through the yaml example a bit. It looks pretty rough.

    Some of those examples are unnecessarily complex to demonstrate rarely used features. I like this example better:

     
            amends "service.pkl"
        
        host = "example.org"
        port = 4242
    
    
      

    The only slightly ugly thing is the amends line, which defines a second config file that defines rules about how to properly configure this one. In that case it's a path to a file on disk, but it could also be a URL such as https://pkl.apache.org/virtualhost if apache were to switch to this format for VirtualHost config files. If you don't need to import rules for use case, it's an optional feature (though it is the main advantage pkl has over other alternatives).

    As far as I know the only widely used config format with support for strict rules is XML, but XML is so complex that almost nobody can actually get IDE integration working. The rules are just too complex. Pkl is simple, these properties need to exist, they have these types (text, number, etc) and these restrictions (minimum 4 digits, etc).

  • Would be interesting to get a fediverse version of Quora

    A Fediverse version of Stack Exchange would be easier - since the content is creative commons you could start with a full catalog of already answered questions...

    But honestly, competing with the real Stack Exchange on one end and Large Language Models on the other end... never going to work.

  • What does that "solve" exactly? Australia wants students. And we want them to work while studying.

    30% of the Australian population are recent migrants and Student Visas make up 39% of all Visas so this affects a lot of people.

    The vast majority of them are genuine students studying at some of the best schools in the world - we don't want to change anything that will hurt those students.

  • This is probably the three layers (three are physical, the rest are digital processing steps):

    The "generate faces" step is well in the uncanny valley territory. There's not enough light inside the headset to do passthrough video so instead they have a very primitive avatar which is recognisably you but definitely doesn't look like you.

    Personally I don't think any of them contribute significantly to the weight of the headset. Probably less than 1% of the weight.

  • What? That's not a fire hazard at all. Your second battery would provide at most 100 watts which is perfectly safe and not going to cause any fires.

    If you submerge the battery in water or stab it with a knife... sure it might catch fire. But that's pretty much the only risk so long as you stick to reputable brands that comply with safety standards.

  • I bet it does have power pass through. Lots of people are going to use this all day at a desk and you'd get to a thousand cycles in just three months if plugging it into the wall just charges the battery. It needs to be passthrough.

  • The USB-PD spec can cover a verity of voltage and amperage combinations

    That's not really true - it maxes out at 5 Amps which is only a decent amount of power if you use (relatively) high voltages. Vision Pro runs at 13 volts, which isn't supported by USB and if it was that would only be 65 watts - nowhere near enough to power this product.

    Running at higher voltages (USB can do up to 48 volts) would likely have problems, it might be less efficient for example (which would mean they have to give it a larger battery).

  • That is so weird, f’ed up and dystopian.

    It's not as weird as the Meta Quest, where you literally have no idea wether the person wearing it is looking at you or not.

    The view of someone's eyes is very low quality - I'll give you that. But it's better than nothing at all. And I'm not sure they could've done better without doubling the price of the product.

  • Why do you need to transition from jpeg to anything else? Just keep using jpeg for old files.

    Chromium is literally the only reason jpeg-xl isn’t being adopted right now

    That's not a "reason" it's a "decision". Their actual reason is pretty good — they don't want to support every image format that comes along. That's a slippery slope, there are several hundred image formats - should they all be supported? How many of them have security flaws? How much work is it to check for security flaws even if none exist?

    The original image formats for the web, jpeg, gif, png, svg, all have major benefits compared to each other. That's why they were successful. There used to be other widely used image formats but they all fell by the wayside because the goal is to try not to have many formats. Ideally we'd only have one.

    And WebP moves a long way in that direction, it does basically everything except vector images. AVIF is still around for efficiency reasons (it's very really easy/fast/low battery consumption for camera hardware to create an AVIF).

    JPEG-XL has advantages but unlike those two they are really small and not worth the effort.

  • It has 24 pins. Power would be two or three pins.

    24 is exactly the number you'd need to have a thunderbolt connection... which could be interesting, though I don't think Apple has said anything about it being used for that.