• 0 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle






  • According to Halioua’s post, breeding large dogs for their size caused elevated levels of IGF-1, a hormone that promotes cell growth. Though this hormone contributes to the animals’ great size, it also hastens their aging. LOY-001 reduces the levels of IGF-1 in large and giant dog breeds, extending healthy life spans.

    Would that also cause them to grow to smaller sizes? (I suppose that may depend on whether this drug is administered before or after the dog is full-grown though)



  • There are FOSS licenses (notably the GPL) that say that if you do resell (or otherwise redistribute) the software, you have to do so only under the same terms. (That is, you can’t sell a proprietary fork. But you could sell a fork under FOSS terms.) But none that say “no selling.”

    For many companies (especially large ones), the GPL and similar copyleft licenses may as well mean “no selling”, because they won’t go near it for code that’s incorporated in their own software products. Which is why some projects have such a license but with a “or pay us to get a commercial license” alternative.



  • I have a similar setup.

    Getting the DNS to return the right addresses is easy enough: you just set your records for subdomain * instead a specific subdomain, and then any subdomain that’s not explicitly configured will default to using the records for *.

    Assuming you want to use Let’s Encrypt (or another ACME CA) you’ll probably want to make sure you use an ACME client that supports your DNS provider’s API (or switch DNS provider to one that has an API your client supports). That way you can get wildcard TLS certificates (so individual subdomains won’t still leak via Certificate Transparency logs). Configure your ACME client to use the Let’s Encrypt staging server until you see a wildcard certificate on your domains.

    Some other stuff you’ll probably want:

    • A reverse proxy to handle requests for those subdomains. I use Caddy, but basically any reverse proxy will do. The reason I like Caddy is that it has a built-in ACME client as well as a bunch of plugins for DNS providers including my preferred one. It’s a bit tricky to set this up with wildcard certificates (by default it likes to request individual subdomain certificates), but I got it working and it’s been running very smoothly since.
    • To put a login screen before each service I’ve configured Caddy to only let visitors through to the real pages (or the error page, for unconfigured domains) if Authelia agrees.






  • Technically DNS will let you look up a host name from an IP address, but the catch is that it might not work: it’s not automatically configured. And even if it is configured you might not get all of the host names pointing at that address.

    Very many webserver operators don’t bother adding the server’s host name to reverse DNS. For example, lemmy.world’s IP address does not map to any host name in reverse DNS, and google.com’s IP address maps to some completely different name for me, with no mention of Google in the returned name.

    Also, many websites can be served from the same IP address, especially if they are hosted in the cloud. You are correct that someone snooping on the connection would still see the IP address, but if that points them at something like a webhosting company or a CDN (or some other server hosting many different sites) it still doesn’t really tell them which specific site is being accessed.

    But yes, if the site you’re accessing is the only one hosted on that server then the snoop could potentially guess the host name. But even then: how would they know that’s the only site hosted there? If some site they’ve never even heard of uses the same IP address they would never know.


  • Without a VPN every host you connect to can approximate your location down to a few miles.

    I just tried a few geo-IP lookups of my current IP address, and they all point to a location that (as the bird flies) is almost exactly 100 miles from my actual location. This is despite the ISP I’m using being headquartered in my current city, but maybe they have some infrastructure there?

    On mobile data I instead get a location 90 miles away, and if I look up the IP address of another machine I know the exact location of, the result is 60 miles off.

    60-100 miles is a pretty generous definition of “a few”.


  • There’s a bit more to it than captured in the summary, which is why it’s just a summary of the spec and not the actual spec.

    From a bit further down on that page:

    1. Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

    Lemmy is still in major version zero, so it can make breaking changes without incrementing the major version and still be in compliance with the spec. This way, projects won’t have their first “real” version be something like v123.0.0.

    Lemmy still being v0.x also serves as kind of a warning to app developers that changes like this may be made at any time.


  • I assume you mean the table on the last page of the paper, which indeed shows WireGuard is safe against the second attack.

    If you go back one page (to page 17) it has another table for the first attack. That one is less positive about WireGuard:

    • The good: On Linux/Android, WireGuard is safe against that one.
    • The bad: MacOs and iOs WireGuard are marked as vulnerable to that first attack.
    • The ugly: Windows is marked as “local traffic blocked” which presumably means the attack failed but so does the connection they tried to attack.