Lmst

Hugo Slabbert ⚠️ boosted:

You can tell me this is a bird flying all you want, I choose to believe it's a rabbit on skis in the middle of a long jump. 🐇 ⛷️

Picture of a bird flying that also looks like a rabbit on skis in the middle of a long jump.

Hugo Slabbert ⚠️ boosted:

“Design As Repair - Ron Bronson”

https://blog.ronbronson.com/design-as-repair?utm_campaign=vibe-prototyping-isn-t-solving-any-problems-but-it-s-creating-many-new-ones&utm_medium=referral&utm_source=productpicnic.beehiiv.com

> The loop is clear. Automation without understanding leads to more friction, not less.

@zrail @alexthesortofok I got the same for FF mobile, with a working v6 setup (IPv6-mostly network).

curl etc. work fine.

On regular FF on desktop it would throw up server not found.

BUT this seems to be FF doing "https only mode" even when I tried to force the scheme to http. If I disable the "https only" mode it works fine for FF mobile and desktop.

FF mobile saying "address not found" is a weird / wrong error message here, imho, as I got the same when "https only" was enabled for FF mobile.

@litchralee_v6 for sure.

Docker's networking model and associated concepts are frequently that stumbling block for me. Whenever I would be fighting some part of the networking, invariably that "swimming upstream" was precisely because of the assumptions in the networking design based on the target user base and intended use cases. What I would see as limitations and frustrating constraints were not accidents or chance but the logical outcomes from those starting points.

This is one of those things that should have been obvious, but I just schlepped along with it until it finally got annoying enough to fix.

Docker networking things!

Docker does have some docs for IPv6 networking for a bit now that's been not quite as terrible as it used to be. To be clear: It's still standard docker things so "NAT ALL TEH THINGS," but at least you'll get IPv6 connectivity.

So I'd followed https://docs.docker.com/engine/daemon/ipv6/ to:

enable IPv6 as a whole
add an IPv6 supernet from which new networks will get allocated (IPAM)
add IPv6 for the default docker bridge

Basically:

{
  "ipv6": true,
  "fixed-cidr-v6": "<your ULA base>::/64",
  "default-address-pools": [
    { "base": "172.17.0.0/16", "size": 24 },
    { "base": "<your ULA>::/56", "size": 64 }
  ]
}

However, if you're using compose for things, you still will not get IPv6 by default and will need to create an explicit IPv6-enabled network in your compose specification and then add that network to all of your containers.

The missing bit was actually changing the default settings of the bridge network driver in the Docker daemon config. This took a bit of hunting around, but the option is com.docker.network.enable_ipv6. So, add:

  "default-network-opts": {
    "bridge": {
      "com.docker.network.enable_ipv6": "true"
    }
  }

For a full config like:

{
  "ipv6": true,
  "fixed-cidr-v6": "<your ULA base>::/64",
  "default-address-pools": [
    { "base": "172.17.0.0/16", "size": 24 },
    { "base": "<your ULA>::/56", "size": 64 }
  ],
  "default-network-opts": {
    "bridge": {
      "com.docker.network.enable_ipv6": "true"
    }
  }
}

Huzzah! Any new docker networks, specifically including any networks from compose files, will now get IPv6 by default!

#ipv6

Hugo Slabbert ⚠️ boosted:

To my mutuals (and really anyone nice) living in the #Vancouver area. My wife is being offered a job in Surrey and we're having a miserable time trying to find living accommodations. Is there some secret to finding a home there for those of us who aren't millionaires? Must one abandon most of their worldly possessions and rent in order to live there? Tips and advice are welcome.

Hugo Slabbert ⚠️ boosted:

"We estimate that the Metaverse could generate $4 trillion to $5 trillion in value by 2030."

Happy three year anniversary to McKinsey's "A CEO's Guide To The Metaverse".

https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/a-ceos-guide-to-the-metaverse

An excerpt from a McKinsey report saying "How should CEOs view the metaverse? Is it a big opportunity or a big risk? Our answer: the opportunity is enormous—and the risk is not what you think it is. The companies that are building the metaverse see it as the next iteration of the internet (see this McKinsey Explainer for more). And as with any technology so vast and all-encompassing (it’s similar to AI in its scope), the potential is enormous. We estimate that the metaverse could generate $4 trillion to $5 trillion in value by 2030; see our report for all the details.

On the other hand, there are clear risks. Don’t be distracted by the debacles in crypto and nonfungible tokens (NFTs); those are Web3 technologies that are related but not exactly the same as the metaverse. Rather, the biggest risk is missing the wave of change that breakthrough technologies such as the original internet, AI, and the metaverse can unleash. In our April 2022 survey, some 95 percent of business leaders expect the metaverse to have a positive impact on their industry within five to ten years, and 61 percent expect it to change the way their industry operates.

In this article, we’ll briefly summarize the reasons for optimism and the factors that suggest the metaverse is truly a CEO issue. "

@ariadne but that's the crux, innit? The system demands a manufacturing line; an industrialized process of churning out mid rent, disposable software where "good enough is".

Hugo Slabbert ⚠️ boosted:

#NetworkManager just got #464XLAT CLAT support merged in.
IMHO this is a major step for #IPv6-only/mostly support on Linux, with NetworkManager likely being the most used network tool on Linux desktops out there.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107

Huge thanks to @mary who started the implementation and bgalvani who brought it over the finish line, and of course everyone else who contributed to it someway.

@ariadne honestly that post was near indistinguishable from satire. It felt like a high proof distillation of every "tech people being out of touch with reality" trope all rolled into one.

Hugo Slabbert ⚠️ boosted:

Warning - the algorithms in this device are known to contain bias

#Sticker #stickerart #39C3 #stickerexchange

@mjg59 that just reminded me of...

https://hachyderm.io/@jbcrawford/115551027203380125

@goetz @Tubsta I also wonder how much of this is providers just saying "I'm not going to pin anything because then I have to honour that, and I'd rather just be free to make no promises and shuffle prefixes whenever I feel like it."

There is a certain sense of satisfaction when you can push back on any ISP tech "everything seems fine" with direct time series metrics.

Is that maybe overkill for a home connection? Personally, no.

@glyph confirmed works for my own resolvers (direct from root hints) as well as through both quad 8 and quad 1.

Follows the CNAME chain blog.glyph.im -> writing.glyph.im -> public.glyph.im -> glyph.im A record of 152.70.120.182.

Answer section is the same for all three of those resolvers:

;; ANSWER SECTION:    
blog.glyph.im.          300     IN      CNAME   writing.glyph.im.
writing.glyph.im.       300     IN      CNAME   public.glyph.im.
public.glyph.im.        300     IN      CNAME   glyph.im.
glyph.im.               242     IN      A       152.70.120.182

"If we overlook the social, economic, labour, political, and environmental components..."

Or how about we not?

Lost in a sea of blue