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
8
Comments
108
Joined
3 yr. ago

  • I bet that 1234 is used more often because of the 4-character minimum, like PIN codes on debit cards. It's 4 characters so it's safe. 123, on the other hand, is not safe, because it is 3 characters. /s

    My solar inverter admin interface has a certain 4-digit password. So I wanted to change it to secure it, and found out that it only allows 4-digit passwords. Luckily the access point can be set up with a higher entropy password though (it is constantly advertised and had a very "secure" 8-digit password by default, I think you can guess which one)

  • That's crazy and genius!

    "I don't do cloud computing, I do solar computing"

  • The way I understand it, there's 2 use cases for a VPN, with different concerns and providers:

    • having access to your private home network from anywhere, through an encrypted tunnel (Tailscale, Wireguard on the router, etc)
    • having your outgoing traffic to the internet go through an anonymized exit node so that your ISP can not watch or sell what you are doing (ProtonVPN, Mullvad VPN, etc)

    Is Tailscale fit for the second? I thought not, as the exit node is not an anonymized VPN server but one of your own machines.

  • Just like you! ❤️🥰

  • It is.

    It's also sad that chickens, fishes and shrimps don't look as cute and aren't mourned even though they suffer all the same. They usually don't even get a plural form.

  • Interesting approach but looks like this ultimately ends up:

    • being a lot of babysitting / manual work
    • blocking a lot of humans
    • not being robust against scrapers

    Anubis seems like a much better option, for those wanting to block bots without relying on Cloudflare:

    https://anubis.techaro.lol/

  • It is very different from the usual flat corporate style yes, but this is just their branding. Their blog is full of anime characters like that.

    And it's not like you're looking at a literal ad for their company or with their name on it. In that sense it is subtle, though a bit unusual.

  • Yes it is. It's in Alpha because it's not feature complete yet.

    But not everyone needs a feature-complete Desktop Environment. Some people are OK with a basic window manager.

    Despite known bugs (reproducible crashes), many people are happy with it already.

    Guess some of those use Garuda.

  • They hit all the right Node(j)s!

  • For anyone wondering what "TDS" means:

    Trump derangement syndrome (TDS) is a pejorative term, used to describe criticism of or negative reactions to President Donald Trump that are perceived to be irrational and to have little regard for Trump's actual policy positions.[1] The term has mainly been used by Trump supporters to discredit criticism of him, as a way of reframing the discussion by suggesting that his opponents are incapable of accurately perceiving the world.[2][3] Some journalists have used the term to call for restraint when judging Trump's statements and actions.[4][5][6]

    Despite the usage of the term syndrome suggesting a medical condition, TDS is not an official medical diagnosis.[7] A 2021 research study found no evidence to support the existence of TDS among Trump detractors on the left, but instead found bias among his supporters.[8

    Source: Wiki

  • GitOps + Renovate.

    Tools that allow you to work GitOps (everything is defined in text files in Git) are:

    • Kubernetes
    • NixOS
    • to a lesser degree, Ansible

    Here's a nice starter template for running your own Kubernetes cluster via GitOps with Renovate pre-configured: https://github.com/onedr0p/cluster-template

  • Mostly yes, but there are some closed source services which are still good options for this specific threat model.

    And I just thought the clear explanation of the why combined with the list, makes this an excellent blog to send to people who don't get it yet.

    The list itself is something most of the people in this community know already, but you might want to send this when someone asks "why?"

  • Undervalued comment right there. This is better than the OP

  • Took a look at the specification, this is what I found:

    For federated servers performing delivery to a third party server, delivery SHOULD be performed asynchronously, and SHOULD additionally retry delivery to recipients if it fails due to network error.

    So they should retry. Note that should is not the same as must. So there is no obligation. There is no timeline in the spec about for how long or how often retries should be done. The wording says network error.

    My interpretation: the spec leaves a lot of room for implementations to differ. Network problems don't normally last for days though. I'd guess that if your server is down for 5 minutes, you'll still receive most or everything you'd normally receive. I wouldn't trust on that if your server is offline for more than a day.