sem

joined 1 year ago
[–] sem@piefed.blahaj.zone 4 points 1 month ago (1 children)

One country, two nations?

[–] sem@piefed.blahaj.zone 4 points 1 month ago

UN Peacekeeper forces, respect

[–] sem@piefed.blahaj.zone 3 points 1 month ago (1 children)

If wealth is in crypto maybe they think it can't be found to be taxed

[–] sem@piefed.blahaj.zone 1 points 1 month ago

That is pretty cool!

[–] sem@piefed.blahaj.zone 1 points 1 month ago* (last edited 1 month ago) (2 children)

So a problem just came up today that encapsulates why IP addresses are still useful.

I have a webservice at http://jeopardy.local:9981/, but typing that into a web browser gives "Server Not Found".

But if I type in http://<ipaddress>:9981 it works perfectly.

It turns out that the problem is that flatpak Web browsers can't resolve mdns names.

The world is full of stuff like this which unfortunately makes ip addresses the most reliable way to reach selfhosted services.

[–] sem@piefed.blahaj.zone 1 points 2 months ago

Time to drop some particle physics in da club:

https://www.youtube.com/watch?v=j50ZssEojtM

It had a good run!

[–] sem@piefed.blahaj.zone 1 points 2 months ago

All imagemacros are memes but not all memes are image macros there are we happy now

[–] sem@piefed.blahaj.zone 1 points 2 months ago (1 children)

I would like to know more about this mdns.

In my experience, the following are unreliable, and it's unclear which one is supposed to work under which context:

  • ping hostname
  • ping hostname.local
  • ping hostname.<whatever that local domain thing is called>

While pinging the ipv4 address is reliable; if the device is reachable on the network, it should respond.

[–] sem@piefed.blahaj.zone 1 points 2 months ago (4 children)

I'm taking this as a genuine question, so I'll answer for myself personally. My mental model of IPv4 is quite simple. A computer doesn't have an address unless you configure one for it, or a DHCP server gives it one. If you are on the same network and there's no firewall, knowing the ip address lets you reach the computer. The router has one public facing IP address that all your devices have to share, which is inconvenient.

In ipv6, a computer has two automatic addresses from the MAC address, a link local and a real one, but they aren't interchangeable, and don't always work. Instead of DCHP, there is something else that prevents ip collisions somehow, but dhcp also still exists sometimes.

In my limited experience, i can never count on reaching a device by its hostname, but if i know a local ipv4 address, that's enough, and they're easy to remember since only the last part really changes. With ipv6 the address is too long and incomprehensible to remember.

I love that ipv6 works better for computers, that you don't have to worry about NAT traversal, but i don't think it is too hard to understand why humans find using it day to day more confusing if they're used to ipv4.

[–] sem@piefed.blahaj.zone 5 points 2 months ago (3 children)

Dns doesn't always work, and seeing if you can connect via IP is often a troubleshooting step

[–] sem@piefed.blahaj.zone 3 points 2 months ago (6 children)

I really like how ipv6 works; the downside is it's way more complicated for humans to understand. But then again all of networking gets complicated fast. I still don't really get what a CGNAT is.

[–] sem@piefed.blahaj.zone 4 points 2 months ago (1 children)
view more: ‹ prev next ›