Data Science

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

help-circle





  • Nice article.

    why bother? Why I self host

    Most of this article is not purely about that question, but I dislike clickbait, so I’ll actually answer the question from the title: Two reasons.

    First of all, I like to be independent - or at least, as much as I can. Same reason we have backup power, why I know how to bake bread, preserve food, and generally LARP as a grandmother desperate to feed her 12 grandchildren until they are no longer capable of self propelled movement. It makes me reasonably independent of whatever evil scheme your local $MEGA_CORP is up to these days (hint: it’s probably a subscription).

    It’s basically the Linux and Firefox argument - competition is good, and freedom is too.

    If that’s too abstract for you, and what this article is really about, is the fact that it teaches you a lot and that is a truth I hold to be self-evident: Learning things is good & useful.

    Turns out, forcing yourself to either do something you don’t do every day, or to get better at something you do occasionally, or to simply learn something that sounds fun makes you better at it. Wild concept, I know.

    Contents

    Introduction
    My Services
    Why I self host
    Reasoning about complex systems
    Things that broke in the last 6 months
    Things I learned (or recalled) in the last 6 months

    • You can self host VS Code
    • UPS batteries die silently and quicker than you think
    • Redundant DNS is good DNS
    • Raspberry PIs run ARN, Proxmox does not
    • zfs + Proxmox eat memmory and will OOM kill your VMS
    • The mystery of random crashes (Is it hardware? It’s always hardware.)
    • SNMP(v3) is still cool
    • Don’t trust your VPS vendor
    • Gotta go fast
    • CIFS is still not fast
    • Blob storage, blob fish, and file systems: It’s all “meh”
    • CrowdSec

    Conclusion













  • This is a web service that returns the ActivityPub data for any URL that returns an ActivityPub message. For instance this post (https://lemmy.ml/post/19589249) returns:

    {
      "@context": [
        "https://join-lemmy.org/context.json",
        "https://www.w3.org/ns/activitystreams"
      ],
      "type": "Page",
      "id": "https://lemmy.ml/post/19589249",
      "attributedTo": "https://lemmy.ml/u/hongminhee",
      "to": [
        "https://lemmy.world/c/fediverse",
        "https://www.w3.org/ns/activitystreams#Public"
      ],
      "name": "BrowserPub: A browser for debugging ActivityPub and the ⁂fediverse",
      "cc": [],
      "mediaType": "text/html",
      "attachment": [
        {
          "href": "https://podcastindex.social/@js/113011966366461060",
          "mediaType": "text/html; charset=utf-8",
          "type": "Link"
        }
      ],
      "sensitive": false,
      "published": "2024-08-26T11:43:09.033551Z",
      "language": {
        "identifier": "en",
        "name": "English"
      },
      "audience": "https://lemmy.world/c/fediverse",
      "tag": [
        {
          "href": "https://lemmy.ml/post/19589249",
          "name": "#fediverse",
          "type": "Hashtag"
        }
      ]
    }
    

    Prepend https://browser.pub/ to the URL you want to check: https://browser.pub/https://lemmy.ml/post/19589249


  • Some key quotes from the article:

    It’s perfectly reasonable for a consumer cloud storage provider to design a system that emphasizes recoverability over security. Apple’s customers are far more likely to lose their password/iPhone than they are to be the subject of a National Security Letter or data breach (hopefully, anyway).

    I wish that companies like Apple could just come right out and warn their users: ‘We have access to all your data, we do bulk-encrypt it, but it’s still available to us and to law enforcement whenever necessary’.

    So what is the alternative?

    Well, for a consumer-focused system, maybe there really isn’t one. Ultimately people back up their data because they’re afraid of losing their devices, which cuts against the idea of storing encryption keys inside of devices.

    You could take the PGP approach and back up your decryption keys to some other location (your PC, for example, or a USB stick). But this hasn’t proven extremely popular with the general public, because it’s awkward — and sometimes insecure.

    Alternatively, you could use a password to derive the encryption/decryption keys. This approach works fine if your users pick decent passwords (although they mostly won’t), and if they promise not to forget them. But of course, the convenience of Apple’s “iForgot” service indicates that Apple isn’t banking on users remembering their passwords. So that’s probably out too.