Melody Fwygon

No.

It is hard to have both; but not impossible. You can still be privacy friendly without sacrificing necessary functionality.

It will require that the “provider” of such a dataset constantly scrub, sanitize and remove data that would cause privacy hazards as quickly as reasonably possible however. That in and of itself is a technical challenge; though not impossible.

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)

I like that he is being decisive about it. I wouldn’t be surprised to learn that the feature was only being delayed because of internal project politics or quirky policies that normally make sense, but don’t in this specific scenario.

I’m not being harsh; they bungled that initial transition badly too; despite it being a Google action.

Unfortunately they left a lot of users in the lurch when they left the Play Store as well and that too left a bad taste. It’s not exactly easy to migrate across versions and packages and software differ wildly as they allowed both versions to do their own thing without relabeling them so you could run them side-by-side.

I don’t blame them for Google’s actions; but I do blame them for how they handled it.

You might be confusing my transition into a rant against Google as blaming Termux.

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.

Android rates as kneesocks at best; if you’ve rooted and installed a custom ROM

Even a progression from “Closed Source” to “Source Available” is nice progress I think.

If we assume that the License is not restrictive we may be able to fork Winamp into a codebase that might actually be Fully Open Source Software and track changes of the upstream as we need.

Minimum SDK also does get bumped in Android in general at a snails pace. Given that we’re basically coming up on Android 15; it’s not unfair to assume that, eventually, we will simply see Android intentionally and permanently REFUSE to run the app because it’s Minimum SDK value is considered to be too low and thus Android must assume that the application is completely insecure.

The largest barrier for me in FLOSS and FOSS applications is simply a lack of GUI tools for what is considered to be “Advanced” functions.

Just because I can do it on linux doesn’t mean it’s easy or intuitive. Unfortunately a lot of FOSS and FLOSS applications are, of necessity, extremely limited in what tasks they are targeting. Frequently you cannot rely on the “alternative” to have a relied upon function or feature until deep in it’s lifecycle; when finally enough people have complained and the feature is implemented.

Sometimes a feature is never implemented due to an entirely shifted paradigm in the way the program is implemented and the feature is “impossible” or “inconsistent with xyz”.

One example of this is the number of GUIs and frontends written for ffmpeg; many of which simply are lazy GUI implementations of what the ffmpeg CLI binary itself will helpfully print out in the console when you ask it for help with the correct switch(es). Many are even less thought out than this and will often unhelpfully provide an obtuse box at the bottom for custom commands you wish to feed to the program…which is great if you know the command(s); but make using the GUI unhelpful when compared to just firing up a CLI and reading the output and figuring out the correct command for exactly what you want it to do.

Keep in mind; I am not at all uncomfortable with using CLI interfaces; I just expect that a GUI doesn’t force me to fallback, or become so unusable that I am forced to fall back on an original CLI tool because I cannot possibly discern why it failed to work

Frequently things that would be simply be an option buried deeply in the GUI menus only and are otherwise fairly simple are relegated as being only possible within a CLI interface; and I find that reality quite infuriating most often…as the limitations of a CLI oftentimes make the task I am trying to complete far less simple than it really should have been.

The problem is that this is a Chinese automaker and things aren’t looking good between the Western world and China right now…

There will come a time when becoming Amish will become really attractive again.

I call it the “Google Effect”. If you know you can find information you need by typing “a certain phrase” into a Google search engine…your brain will “encode” those steps; often linking back on your other skills like using a computer and accessing Google.

TL;DR: You didn’t learn how to drive there. You learned how to type a piece of information into a piece of technology to get your answer.

Unless you force yourself to learn the route somehow; you’ll never learn it.

I don’t agree with the assessment of the OP or the original blog article. Grayjay is Open Source software.

It is, however, NOT FREE SOFTWARE and I do know that organizations like the FSF and OSI do not consider it to be free.

The free status of this software was never misrepresented by Louis Rossman. He blatantly explains that there is a cost to this software and that the license is how he plans to enforce his means of collecting this fee on the honor system.

He also outlines how he cannot; and will not…stop anyone from forking this software and basically removing the payment bits of the code and just redistributing it under a different name. I strongly recommend someone does that…and maybe license that work under a much more unrestrictive free license that FLOSS-Only users might find more palatable.

I get that nobody wants or needs to trust Louis to keep his word. He’s gotta run a business at some point…and distributing this software this way on the honor system might not pan out quite the same way he hopes it will. I do hope that at the point where he and his compatriots choose to stop maintaining the application; that they do immediately retcon this restrictive license; and re-release it under a new, free, and unrestrictive Open Source Software license.

To be honest. any company that purchases such a place should be required by law to either: rent it out within 3 months of purchase or sell it to another interested individual and not a company or other legal holding entity.

I’ve always felt the FSF has had no idea what they were doing. Therefore I do not always agree with or support 100% of what they do.

I do feel that sometimes code should be able to carry reasonable restrictions. Just not sweeping restrictions.

An example of a reasonable restriction would be a clause that prohibits commercialized use of free software without first obtaining permission from the project in question. Another reasonable restriction would be a clause that prohibits governmental use or use by military entities.

An unreasonable restriction would be naming only specific companies that are not allowed to use the ‘free’ software. It would also be further considered unreasonable for rights to use ‘free’ software if it expires, goes away, or is revoked if you commit a specific crime, or fall under suspicion of committing said crime.