Melody Fwygon

Beehaw alt of @melody@lemmy.one

@fwygon on discord

  • 0 Posts
  • 51 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle

  • We can no longer trust anything that is specifically sent to us via digital means.

    Technologies like the Document Scanner and even the Photocopier will now have to encode secret data to authenticate that a real, functioning machine has digitized the document.

    This can in fact, cause a great amount of trouble for people.

    People will be required to never digitize themselves handwriting all letters of the alphabet; lest their handwriting be vulnerable to an AI learning it.







  • Ideally there’s not a whole lot of data that needs to be kept.

    Legitimately all that needs to be stored is a few things:

    • Location (GPS)
    • SSIDs (Wifi APs only)
    • Cell ID & MCC/MNC (Cell Towers only)

    and things they MUST NOT STORE OR SHARE like:

    • IPs of contributors for longer than a few days
    • un-hashed BSSIDs (Wifi/BT)
    • MAC addresses (Wifi/BT)
    • IMEI/IMSIs (or other cellular identifiers derived from them)
    • APs that don’t exist in a fixed location (Think mobile hotspot SSIDs) for longer than a fixed amount of time.
    • BT devices
    • Non-unique SSIDs or IDs that may indicate no user config took place and manufacturer did not differentiate device ID. (Things like “SETUP” with no unique number (SSIDs like"SETUP-be3fd34d" would be valid) or “[ISP]@HOME” or “[ISP]Wifi” which provide no meaningful discriminators)




  • Freetube does work; it simply requires you switch to the Invidious API or have “Fallback to non-preferred API on Failure” enabled. (which honestly you always should have this setting ON).

    Personally; I refuse to change my preferred API; so the “Fallback to non-preferred API on Failure” just works.

    also yt-dlp does work but you need to upgrade to latest nightly/build.

    yt-dlp version nightly@2024.07.09.232843 from yt-dlp/yt-dlp-nightly-builds [d2189d3d3]





  • I stopped using Termux in general because of this inanity where they moved off and stopped supporting the Play Store Version; now this happens where they’re unable to keep things from conflicting across the different APK sources?

    Yikes. Seems like a good time to continue staying away from Termux and not recommending it.

    It’s a shame since I really love the concept of the app; but each increment of Android has been rough on it and I can’t imagine it being useful with Google being stupid about their policies.

    …Unfortunately they’re often quick to blame apps they dislike for problems in the ecosystem, and they often directly attack them through nerfing APIs and system calls that the apps tend to use; which I think is absolutely a dogshit thing to do.

    Please, stop enshittifying our phones Google.



  • Unless there’s some kind of bug where Discord enables the in-app setting without actually having the permissions to access contacts

    That’s the bug exactly. It’s kind of a UI glitch; but I found out through Samsung bungling my permissions preferences through a One UI (OTA System) update, that it actually does enable the in-app setting by accident and that this is going to access your contacts if the permission is presently GRANTED, but not throw up a prompt asking for permission if the permission is already DENIED.



  • What’s true is that primary sources don’t count towards notability, so if an article mostly just uses primary sources it’s likely to get deleted.

    Which is absolutely absurd. Counting secondary sources and deciding if something is “Notable” from that is completely arbitrary. Furthermore, there’s legitimate reason for secondary sources not to exist on the topic; and the Notability guidelines of the local WikiProject on Roads, which probably contained the people leaving, should have been taken under advisement as notable roads don’t always have secondary sourcing due to lack of local newspapers or publications.

    Specifically a highway may be notable because it never appears in the news… often because it rarely if ever sees auto accidents. A source is a source, and I think attacking primary sources and excluding them is problematic if the source in question never was causing issues with NPOV.

    Now if someone can prove that a website from the DOT is actually doing some weird POV pushing or is legitimately not behaving like a neutral source; then sure, challenge that citation for that article and get it struck.

    But it’s otherwise a waste of time to pretend that roads and highways aren’t notable and not of encyclopedic interest for good reason.