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/)F
Posts
0
Comments
193
Joined
3 yr. ago

  • Modern. Net is portable and fast, yes. But .NET framework is (mostly) not portable and it's tied to the version of Windows is on. We'll see when Microsoft decides to EOL it but so far it has not been announced. It's not getting more than security updates now, as far as I know.

    We're converting everything we can (mostly web apps) to modern .Net (formerly core) so it can run on Linux. I may be stuck on Windows at work for the office apps, but my code runs on Linux.

  • Agreed. I don't think I explained myself clearly enough: I want them to have a presence online. Among the reasons being exactly what you're pointing out. However, I think at least for smaller cities with very little staff, it's not realistic to ask them to literally self-host it (as in having a server on-prem running it). I would be fine with them outsourcing it or cloud-hosting it under their own domain. A potential solution for the small ones could be something like a state-level hosted service where municipalities can sign up and get their own accounts, for example. That would work even for something like Rittman, Ohio pop. 6,131.

  • Yep. That's what I meant. I want them to come to the fediverse but I don't necessarily want the city's IT admin to manage it between fighting laser printers.

  • Not so sure I want them to self host, just based on their track record for security, but I would like them to be more visible.

    Also news outlets could benefit from doing this instead of us having to rely on repost automation.

    I would also love to see peertube become more competitive to YouTube. It would probably need some kind of revenue sharing model or donation integration for that though.

  • Your diagram is almost right, but I think it will help to understand more of the details. It's important to understand the difference between DNS (domain name lookup) and IP routing.

    To break your diagram down more, this is what happens when any computer looks up your website:

    1. The device does a DNS lookup of "example.com" using their name server, which may forward it to another DNS server (most home routers do this). I won't go into the multiple levels of DNS lookups and caching here.
    2. Through looking it up by DNS, the device now has the final IP. DNS is now out of the picture and we're doing IP routing.
    3. The device tries to make an HTTP connection to your external IP. HTTP is a protocol that runs over TCP/IP (UDP is used for QUIC/HTTP3). To keep things simple I'll stick with old fashioned HTTP over TCP without SSL. I am also skipping over NAT.
    4. For TCP, it performs a handshake, which the reverse proxy will negotiate. Once the connection is established, the browser speaks HTTP to the reverse proxy. It looks something like:
     
        
    GET / HTTP/1.1
    Host: example.com
    ...lots more headers...
    <blank line>
    
    
      
    1. The reverse proxy then takes that request, maps it to an upstream (if any), and makes another request to it via the configured transport. If that part falls down, you will see a 503 error. Otherwise, you will see the response from the upstream, possibly with some modifications made by the reverse proxy (some will rewrite links and cookie paths, for example)
    2. The reverse proxy sends that response back to the client.

    That's all very simplified, of course.

    As others pointed out, things may seem to work differently from the "inside", if hairpinning is not available or enabled. This is not related to DNS, but to IP routing. The firewall doing NAT can get confused and not know what to do when an internal request goes to an external IP that it itself has. When it turns that around and routes it back to the internal network, that's called hairpinning.

    One "fix" for this, often used in enterprises, is to use so-called split DNS. All that means is that if you're asking your internal DNS server for an internal name, it will give you the internal address (192.168.1.123 for example), but an external client would get an external IP.

    TL;DR: DNS and IP routing are separate concerns and happen at different parts of the TCP/IP stack.

  • Hopefully you both have discussed getting married and have some plans for the future before popping the question. As part of your plans you may have things like saving up for a home or go traveling. Put your money towards your dreams, not the ring. Make it a nice ring, but not too nice. Do not borrow money for it. Try to figure out what she would like.

    As the father of a woman who will probably marry her boyfriend in the next few years: I think it works be a great gesture if my future son in law asked me. I won't be mad if he doesn't, but it shows respect and that he's thinking of me as family as well. I think it sets a good tone for the relationship.

  • Great. Now get people to actually vote in midterms.

  • I see I'm not the only one fighting with CI/CD pipelines.

  • Glad you got it working!

    My hypothesis is that it was DNS (channeling Jeff Geerling here). Since Pihole is your DNS (makes sense), it may have recognized that address as its own and given you its IP. By resolving the naming collision, you fixed the problem because the name is now unambiguous.

    These problems can happen very easily when you're using DHCP and sharing a network and domain name between your clients and upstreams, so I think using home.arpa for one and your other domain for the other was a good idea.

  • What is your DNA setup like? A lot of dhcp clients are set up to register their name in DNS (if allowed). It could be your pihole server is hijacking it.

    If you have multiple DNS servers (eg your home router and your lab) them you may not be getting the full picture.

  • Can you confirm that the DNS actually resolves to the NGINX IP address (and only that address) when you use PiHole's FQDN? It sounds like it's bypassing the proxy because it stopped working when you turned 443 off.

  • My favorite thing about the meeting notifications is that the organizer sets the reminder. So, if their default is no reminder, nobody gets a notification.

    I've been in meetings where several people missed the start of the meeting because of this. And no, there is no way to override it, even with a rule.

  • My company device already has so much surveillance on it that this won't make a meaningful difference to me.

    However, given that they can't even get my activity status right, I don't see it going well. For example It sets me we idle even if I'm typing furiously in my editor, unless I go wave my mouse cursor in Teams for a few seconds. Other chat apps got this right decades ago.

    It doesn't deliver messages or delivers them out of order. Unread status on messages doesn't work right. It crashes randomly. I could go on.

    Fix the core functionality, Microsoft, instead of adding all kinds of big brother bullshit. I don't trust Teams to get anything right and neither should my manager.

  • I had very similar thoughts, but I think now that's is just old fashioned greed and they're doing all they can to collect as much money as possible. They don't care if the American economy crashes because they're not depending on it. A lot of useful idiots are sucked into the maelstrom and will suffer with the rest of us, but the insanely rich will be fine.

    It's also not just one thing. Some may want to bury the Epstein files, but the rest of them just want to be insanely rich. Everyone has a different reason to be in on the grift. And they do it because they believe they can get away with it. I don't think it's much more complicated than that.

  • Just to help people searching, it's actually FATCA (as in FATCAt)

  • They are most likely referring to the PHQ-9 questionnaire. 25/27 is not great, indicating severe symptoms.

  • GodOdin

  • For learning, VMs are fine. Spin up as many as you'd like. Install, duplicate, reinstall, delete at will. I would start there.

    Then, while you're learning, set aside since money to get an SBC or mini pc. That will allow you to keep it running as a server continuously. Phones can work for this, but to act as servers you'll probably need to root them.

    Computers are way more expensive than they used to be but within reach for most people if you can save up for it.

    Check thrift stores, Facebook, eBay, the usual suspects. Watch out for PCs stripped for RAM and other shenanigans, though.

  • Thank you for highlighting that. The example was intended to show the (maybe exaggerated) pathological state of web development and certainly not an example to be followed.

    In seriousnes: yes please use a11y friendly markup. It helps your SEO, but more importantly it helps your visitors that use accessibility tools.

    It doesn't have to be hard. I use component libraries that abstract it out and adds the necessary aria attributes and semantic markup for me.

    As a bonus my web app development is closer to using the rich component libraries I enjoy in desktop apps. Just be aware of the absolute mess of npm packages that come with it.