diaphragm w*rkplace

  • 0 Posts
  • 22 Comments
Joined 7 months ago
cake
Cake day: November 12th, 2025

help-circle

  • I got one of those ARM Chromebooks specifically for this (PostMarketOS, no keyboard cover tho) but now it’s mostly collecting dust since I have a laptop and just use that. Although someone in the house uses it for watching very legally obtained shows in mpv… though “uses” is a strong word since I basically press all of the buttons for them. Shame it’s not getting more use though, as it is about 40x more power efficient than said laptop. Maybe with a USB-C dock that costs 2x more than the thing… My phone also collects dust silently until I need 2fa from it since I don’t even have a SIM card.





  • Noooo, don’t look at the bad, look at the good. We have this place and Gemini (the good one) to express ourselves.

    And besides, the title in this repost is a bit sensational. That specific captcha needs a phone with the Google app. You can just delete data + refresh until you get a different one. Nothing about specifically degoogled phones, people without phones are affected just as much. I am sure MicroG would work just as well (if not now, at least later). Also, ideally you should click the fuck away from recaptcha sites either way. Paradoxically, Google’s own sites don’t have it usually except the search but nobody needs that (at least anyone you would ask on here), DuckDuckGo + StartPage (OR SearXNG) is good enough.







  • Most compromised routers scrape the hostname (both regular and mDNS) and MAC address. What you do is disable mDNS related daemons like kdeconnect and avahi (until you want them) and put this in /etc/NetworkManager/NetworkManager.conf:

    [main]
    hostname-mode=none
    
    [device]
    wifi.scan-rand-mac-address=yes
    
    [connection]
    ethernet.cloned-mac-address=random
    wifi.cloned-mac-address=random
    connection.mdns=0
    connection.llmnr=0
    

    (yes, the mdns bit above is a bit redundant, but systemd has something related that might read it and better be safe than sorry)

    This won’t protect you if the router is a bit smarter and can see your NTP server (usually like “x.archlinux.pool.ntp.org” instead of just “x.pool.ntp.org”), your connectivity check (same as NTP) and other servers your machine connects to (like Tor nodes if you have the daemon running and oftc.net if you have an IRC client). The good news is that none are known to check that (at least to me).








  • What are you actually broadcasting while doing so? That you are using KDE Connect?

    That + device name which is probably pretty unique. Chinese routers scrape all of that. IIRC mDNS is actually disabled on Linux for now because it was conflicting with Avahi which broke some more stuff.

    do not use KDE Connect on other networks

    Last time I used it, I don’t recall a toggle for that in either the Linux or the Android clients.

    Edit: what alternative device discovery solution could be used by KDE Connect to make it more private on untrusted ntetworks?

    Exactly as it is right now but on a whitelist.

    Offtopic but I am really annoyed by how many custom ROMs (especially LineageOS) disable MAC randomization at build time and make zero mention of it on the wiki/forum/whatever page. That’s just as important.