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/)C
Posts
10
Comments
115
Joined
2 yr. ago

  • On Tor dark web domains, you use the .onion domain. Tor is configured as a SOCKS proxy, so it doesn't perform a DNS query. Instead, Tor itself sees you're trying to connect to an onion domain name. Then it takes the URL and translates that into a public key that it knows how to find in its own hidden service directory.

    Only the actual hidden service has a valid private key corresponding to that public key in the URL so cryptography (and the assumption that quantum computers don't exist) ensures you're talking to the right server.

    Tl;dr effectively no DNS for onion hidden services

    https://community.torproject.org/onion-services/overview/

  • Putting the charger circuit inside the battery takes away battery capacity, so I still buy the external chargers

  • Unless you're running VLANs, in which case the inter VLAN is normally handled by the router. I also expose my home lab services over BGP so all my traffic hits the router then comes back to my lab services.

  • https://forum.syncthing.net/t/discontinuing-syncthing-android/23002

    According to this post, it was partly that and lack of maintainers. Given there's maintainers for a fork, I'm curious why they didn't bring them into the main project.

    Reason is a combination of Google making Play publishing something between hard and impossible and no active maintenance. The app saw no significant development for a long time and without Play releases I do no longer see enough benefit and/or have enough motivation to keep up the ongoing maintenance an app requires even without doing much, if any, changes.

  • We're sort of in this situation because the official project decided not to continue providing an official Android app, yet people want to use it on Android forcing unofficial versions to be created and maintained.

    I get that they don't want to deal with Google Play anymore, but somebody has to deal with it and them not owning the app is putting users at risk.

  • I tried that with my KeePass database and then I ended up with different conflict versions if a device didn't sync to my server before I updated on another device. Then I ended up with the conflict versions and old versions I had manually resolve. The Android Syncthing app could get auto killed by the Android OS for memory/battery saving, so I had to go back to OneDrive style syncing where the KeePass Android app would internally merge and resolve conflicts. It couldn't do that using the Syncthing style syncing.

  • How would that work? The use case is for previews for pull requests. Somebody submits a change to the website. This creates a preview domain that reviewers and authors can see their proposed changes in a clean environment.

    CloudFlare pages gives this behavior out of the box.

  • It is for pull requests. A user makes a change to the documentation, they want to be able to see the changes on a web page.

    If you don't have them on the open web, developers and pull request authors can't see the previews.

    The issue they had was being marked as phishing, not the SSL certificate warning page.

  • Some people are asking why other regions seem to be affected when us-east-1 goes down. Why aren't they separated out? I used to work in AWS, but will speak generally.

    First, it's important to understand the concept of a control plane vs a data plane. Amazon and other big scale companies often talk in terms of control plane/data plane separation because those two concepts have wildly different scale and requirements.

    A control plane is the side of your service that handles the administrative functions of a service. For example, AWS S3 service would separate out bucket creation and deletion work from the file create/edit. In Route 53, this would be creating and editing zones. In IAM, it's the creation of AWS access keys for IAM users. IAM Roles, IIRC, work differently and can function more in the data plane.

    A data plane is the side of the service that handles the main meat and potatoes of a service. For example, AWS S3 any object key creates, edits, deletes would all be part of the data plane. In Route 53, these would be any DNS record query. I don't know if updating a record was considered a data plane call or not.

    These are separated out because data plane generally massively dwarf the number of calls for administrative APIs. It's also done because control plane calls often times have some extra complexities. Like in Route 53, to create a zone means you need to go find n different name servers that can handle a given domain name without overlapping with another customer, you need to tell them that they should now handle calls, you need to get the records to those servers running all over the world.

    The fact is Route 53 is globally replicated and they need to have a source of truth and engineering culture pushes Amazon towards a pull based approach. If a user creates a zone in eu-west-1, they still expect it to be on servers all over the world, so how do you get it there? Well, AWS takes the approach that certain services can have a single region dependency for their control plane in the case that it's infeasible technically or to the business to avoid one, however the data plane of the service can't have that dependency.

  • N. California as a region can't grow and it's priced accordingly. Instead, compare US East (Ohio) or US West (Oregon) for a region that's price competitive. A lot of Amazon internal stuff was starting to move to US East (Ohio) because it was geographically close, but a lot less problematic.

  • This is a little misleading. It does not mean that every single region depends on us-east-1 to authenticate every API calls. That would be insane and obviously mean that every region has a dependency on us-east-1.

    Instead, us-east-1 is what's called a partition leader. It holds the secret key material for everything in the commercial partition and regularly it distributes that to other regions. So if it's down for an extended period of time, other regions IAM can be impacted, but then there's some other complexity with STS endpoints. You can actually see the by product of this if you look at how the SigV4 signing algorithm works. Each HMAC layer is expanding the key scope.

    Anyway, this part of IAM is pretty battle tested and from I saw not the cause of today's outage.

  • Small correction. He was impeached by the House. The Senate then decides whether to convict, not whether to impeach.

  • The MinisForum B550 is what I use for my own setup and it works pretty well.

  • I was surprised to see this. I encouraged friends to get the Yellow because of the PoE support that the Green didn't have IIRC.

  • homeassistant @lemmy.world

    Nabu Casa - Ending production of Home Assistant Yellow

    www.home-assistant.io /blog/2025/10/15/yellow-end-of-life/
  • Rebase still means you have to resolve conflicts, but it can be worse because you may have to resolve conflicts across multiple commits that you're rebasing on top of a conflict.

  • That's a safe assumption given the post is about entries in the logbook and that depends on the recorder.

  • This only hides the entries from the logbook, but they're still being saved to database taking up disk space.

    I would go further and exclude them from the recorder.

  • Even if an external company makes it, they can add an open source mandate if they want. The US DoD is starting to mandate the usage of open standards for their contractors to increase inter compatibility and ability to extend those systems.

    Open source software has some value like making it easier for analysts to find security issues and the act of open sourcing software usually leads organisations to raise the quality because they don't want to be ashamed of the code. Plus imagine the clout gained by a dev who got a bug fix merged in that millions of citizens get to use.

  • A newer release, v0.6.30 is already released to fix an issue with OneDrive integration.

    Looks like they finally finally made their slim image tag smaller than the main image:

     
        
    ghcr.io/open-webui/open-webui:v0.6.30-slim    7c61b17433e8   46 hours ago    4.3GB
    ghcr.io/open-webui/open-webui:v0.6.30         c1ac444c0471   46 hours ago    4.82GB
    
      

    Though only saving .5GB of space is not very slim. I use OpenWebUI in my home lab, but this issue just made me question the quality of the project a tiny bit.

  • homeassistant @lemmy.world

    What's your most pointless or silliest automation?

  • homeassistant @lemmy.world

    Companion app for Android: It’s been a while

    www.home-assistant.io /blog/2025/07/23/companion-app-for-android/
  • homeassistant @lemmy.world

    Zooz joins Works with Home Assistant

    www.home-assistant.io /blog/2025/07/15/zooz-joins-works-with-home-assistant/
  • homeassistant @lemmy.world

    Release 2025.6: Getting picky about Bluetooth

    www.home-assistant.io /blog/2025/06/11/release-20256/
  • homeassistant @lemmy.world

    Home Assistant - Deprecating Core and Supervised installation methods, and 32-bit systems

    www.home-assistant.io /blog/2025/05/22/deprecating-core-and-supervised-installation-methods-and-32-bit-systems/
  • Selfhosted @lemmy.world

    Syncthing Android app discontinued

    forum.syncthing.net /t/discontinuing-syncthing-android/23002
  • homeassistant @lemmy.world

    Nabu Casa is joining the Z-Wave Alliance Board

    www.home-assistant.io /blog/2024/09/24/we-are-joining-the-z-wave-alliance-board/
  • homeassistant @lemmy.world

    LNXLink - Link your Linux computer into Home Assistant

    bkbilly.gitbook.io /lnxlink
  • homeassistant @lemmy.world

    HA Voice Chapter 7 - Supercharged wake words and timers

    www.home-assistant.io /blog/2024/06/26/voice-chapter-7/