• 0 Posts
  • 39 Comments
Joined 3 years ago
cake
Cake day: March 23rd, 2022

help-circle


  • knfrmity@lemmygrad.mltoPrivacy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    The Android private DNS setting is just for a DNS-over-TLS resolver. The only thing about it that’s private is your queries are encrypted en route to the server (traditonal DNS is cleartext). There’s no filtering or blocking.

    Some Android versions also have a hard coded DNS server set to Google, which based on my tinkering uses DNS-over-HTTPS. Not only is it annoying but I find it awfully insecure - even if you think you have stuff locked down it might just not be. I fixed that issue by blocking all DNS-over-HTTPS servers in my router, and also have all outgoing requests to port 53 redirected to my local resolvers (Pihole + Unbound).



  • knfrmity@lemmygrad.mltoPrivacy@lemmy.mlURnetwork?
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 months ago

    “Better than a VPN” but it looks more like some decentralised social and content network. So not a replacement or alternative to a VPN in any way. It just preys on the people who already bought the “VPNs make you private online” marketing.

    Looks like a silicon valley VC cash grab.


  • I use whichever editor is convienient at the moment and which I lile the UX of (Micro on a terminal, Pulsar on desktop, Markor on mobile), and commit the markdown files to a privately hosted git server (Forgejo). The git server is backed up regularly.

    The editor doesn’t matter too much as long as it doesn’t have spyware and/or AI “features” like vscode.

    When I’m on the go and need to read or write notes I have a clone of the repo on my phone, and if I absolutely need to pull/push to origin I connect via VPN.

    I’m not sure how syncthing or similar work with merging different versions of files from different devices, so I’ve just stuck with git for that reason as well as version control (I make notes about homelab configs and issues so being able to go back is handy).



  • Even if it’s as simple as choosing which Root CA’s we want to trust, how many people will know to do that and be able to do that? A couple percent at most.

    Of course we need full ownership of our devices, and trusted computing has always referred to the trust of for-profit corporations, but this in itself doesn’t help the vast majority of people who either don’t know that they’re compromised, think they have nothing to hide, are unable to do anything about it, or a mix of all three.

    Privacy and security are already a privilege. Proposals like eIDAS only make it even more unaccessible.






  • As far as I can tell this just fixes some relatively minor issues the contributor was experiencing deploying the hacky self-host stack on his Kubernetes home lab or private server. It doesn’t bring anything new to the table, and I’m not sure that a full on Kubernetes or similar distributed swarm deployment is really what the average self-hoster needs or even wants.

    It could just be that Omnivore tries to do too much for it to be feasible to self host. It was also conceptualized with certain third-party backend services in mind which makes it tricky to adapt.

    Maybe I’m asking for too much, but I would be looking for a two service stack, one for the app and one database service. The current and forseeable future state of Omnivore is four backend services excluding the database, and like I already pointed out you’re not even getting the full feature set.



  • From their blog post (linked to by the docs page) about self-hosting:

    The following Omnivore features will not be included in this minimal Omnivore setup:
    - The web app (we will use the iOS app from the AppStore as our client)
    - Search of PDFs
    - Saving URLs instead of pages (more on this below)
    -Receiving newsletters via email
    - Text to speech
    

    Not only that, they use a non-self hosted elasticsearch provider.

    Their example docker-compose file in the repo has no less than four containers defined, not including the database server, and you have to build them all yourself, so it’s more of a local dev environment type deployment rather than production.

    Here’s their “make self-hosting more practical” Github issue, coming on two years old with no progress: https://github.com/omnivore-app/omnivore/issues/25

    All of that was more than enough for me to not even bother to try to deploy my own instance. I manage with Wallabag for now, it’s not the greatest implementation either but at least it can be self-hosted. Omnivore looks slick but the backend just doesn’t keep up.





  • As far as I understand, this subscription “option” comes from a couple EU member state data protection agencies saying that the “choice” between give up all your personal information or don’t use the service isn’t good enough.

    It remains to be seen if give up all your personal information or pay and still give up all your personal information will be accepted by those and other regulators. I can’t imagine it will be.

    Also fun fact, it costs more on the mobile apps as Meta passes the Play Store/App Store fees onto the end user.