Melody Fwygon

• Kamala Harris

[X] I refuse to rank or vote for any other candidates.

I genuinely hope this works out and can be replicated across the world. Diabetes is quite a problem for some; and most importantly; it’s something you can’t really easily prevent from occurring if you’re moderately predisposed to it.

This. Pull judges directly from the Federal Circuit; run them for 8-10 years; then send them back to the Federal Circuit as a ‘Distinguished’ judge.

Supreme Court Judges should resist political pressure; but they should not be appointed for life.

Info: A ‘Distinguished Judge’ is a former SCOTUS justice who served their complete term and cannot be re-nominated to the Supreme Court ever again. It is a lifetime title granted when they make it to the SCOTUS and complete one term.

Whoof. The burn.

Glad to see some people understand how much more problematic Trump is than anything that Harris would be doing.

[transgirl moment]

OMGGG jhbendlvckhedjohfvajodfhvaleRDKHFILU I FUCKING WISH THIS WERE TRUE!

[/transgirl moment]

But alas, it is not true, and the schools are not providing free surgeries. But Trump sure does like to lie about shit. This is why we should NEVER EVER LET HIM WITHIN 9875093847592798728752347527093847805 MILES OF BEING IN THE OVAL OFFICE

TL;DR: Never Vote Trump. Anyone who does is foolishly ignoring his lying.

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)

Junk science article.

All discoveries use some element(s) of the scientific method.

The entire method in and of itself isn’t required to be 100% rigorously applied 100% of the time. However, the method is a starting point and does lead to discovery over time.

While it helps to apply the method to ensure clean and proper discoveries which can, hopefully, be reproduced and investigated, the fact that not all sciences or discoveries apply it rigorously is largely insignificant.

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.

Looks like the WaPo will probably start to enshittify too. It’s sad to hear; and it doesn’t bode well for them. Undoubtedly their true journalism will no longer exist under the new leadership and everyone will be afraid to be bold or write anything too shocking.

The move reeks of corpo profit-chasing; and was probably ignited by their CEO falling for the usual Trump/Musk/Zuck garbage spew.

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

These are the kinds of cops that should be summarily fired on the spot and not ever given a badge again. Such sickening behavior.

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.