• 4 Posts
  • 149 Comments
Joined 1 year ago
cake
Cake day: March 3rd, 2024

help-circle




  • Nougat@fedia.iotoMemes@sopuli.xyzBa dum tiss
    link
    fedilink
    arrow-up
    13
    ·
    14 days ago

    You can turn this into a kind of shaggy dog story by starting with something about a shepherd having such a large flock - he keep careful track of how many sheep he’s supposed to have, and he knows there are 789 (never mention this again) - that sheep kept getting loose and wandering off, so he decided it was time to get a dog to help him.

    Fill out the middle with various adventures of acquiring different dogs from different places, each one ultimately standing on a ridge overlooking the flock, and being commanded to “round up those sheep.” Of course, each dog fails in some spectacular or ridiculous way, leading into the next dog acquisition adventure. Lather, rinse, repeat.

    This can go on for as long as you can manage. Finally, some “unexpected” dog (or cat? fish?) is gotten and commanded to “round up those sheep,” the animal pauses, crouches as though ready to run, and says “800.”











  • I feel like the functional differences between instances are:

    • Interface and mobile apps (Lemmy vs mbin vs Piefed vs other)
    • More populated instances are going to have more “extra-instance” content federated to them, because more users means more subscriptions to comms/mags/whatevers at foreign instances
    • Instance uptime and reliability (which depends heavily on the number and attentiveness of instance admins)
    • Different instances will choose to defederate with other instances in different ways

    When I first immigrated here, the most popular platforms were Lemmy and kbin. I liked the kbin interface more, so I started on kbin.social - which folded after a while. So I switched to fedia.io, which runs mbin, a kbin fork.

    None of this has anything to do with “aligning a personal identity with an instance.”




  • No matter where I am, I always have a sketch in my head as to what “leaving” would be like. How long it would take in total, then for each leg:

    • Stand up
    • Pick up coat
    • “Welp.”
    • Put on coat
    • Walk to door
    • Open door
    • Make one last witty comment before closing door behind me
    • Walk to car
    • Open car door
    • Sit down
    • Foot on brake
    • Turn key to START
    • When engine is running, release ignition key to ON position
    • Seatbelt
    • Steering wheel
    • click Reverse
    • Release brake
    • Rear view while backing up
    • Steer onto street
    • Apply brake
    • click click Drive
    • GO

    This is obviously different if I’m somewhere where I have not taken my own car and have to depend on alternate transportation, whether that be:

    • Public transit
    • Catch a ride with someone else
    • Rideshare/taxi
    • Walking
    • Rental bike/e-bike/e-scooter
    • Canal boat
    • Slip-N-Slide
    • Pneumatic tube
    • Quantum tunnelling
    • Window
    • Magic[k]
    • Hiding until everyone else leaves
    • Go to sleep

  • That’s not what I was talking about.

    Technitium does not (necessarily) use a third-party service, but sends all queries directly to the root nodes.

    By default, any DNS server will look to the root servers for any query. The root servers only know what DNS servers are authoritative for top level domains (TLDs), and tell the client querying “Hey, go ask the “.com” (for example) server.”

    That server knows what DNS servers are authoritative for the zones under .com, and says “Hey, go ask the “querieddomain” server.”

    Then your machine asks that server for the “www” (for example) host, and that DNS server says “Here’s the IP.”

    Unless the DNS server your machine is pointing at is configured to use a forwarder, wherein queries for any records that it isn’t authoritative for or aren’t in its local cache are resent to whatever DNS server is configured as the forwarder. The recursion like above is done between your DNS server and its forwarder, finally returning you an IP address when one is identified.

    There’s a bit more to it than that, but that’s what I was talking about. Out of the box, a DNS server uses root hints, which are IP addresses of the root DNS servers. You would need to configure forwarder(s) in your DNS server if you desire them.



  • For the record, any DNS server you choose to employ should default to only using the root servers. You would need to configure your own forwarder IP(s) to point to a general purpose resolver.

    … censorship-free …

    You should also be aware that even if you use root servers, a DNS server which is authoritative for the domain you are querying may well return different results depending on where in the world you are. This can be in order to direct you to an IP that is closer to you, or because “different global locations get different content” for any reason, including censorship and malicious goals. The latter is definitely less likely than the former, but it’s just as possible.