Melody Fwygon

[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.

Firefox is open source. It’s not going anywhere; even if Mozilla Co. goes broke and closes down the Mozilla Foundation.

Most reasonable consumers won’t go for this. it’s a greed play.

Give me mice that I own; not mice to rent.

Disgusting. Utterly disgusting. This idea belongs in the garbage bin.

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)

Linux must achieve 100% compatibility. Otherwise the doubters will not shut up.

https://github.com/yt-dlp/yt-dlp/issues/10397#issuecomment-2218346384

Looks like there’s several causes.

https://github.com/yt-dlp/yt-dlp/issues/3766

I don’t know how soon Tubular or NewPipe can fix their app; but it seems like a few simple changes will do.

I should point out that this isn’t always “Google is trying to block adblockers” again!

Google can, will, and does simply change how the YouTube watch pages look, feel and operate behind the scenes quite regularly.

Thankfully we have people like those at the FreeTube, NewPipe and yt-dlp projects to sift through those changes and update the code to cope with the new output.

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]

YT-DLP fixed already; I use it locally in conjunction with MPC-HC.

yt-dlp -U or yt-dlp -U nightly

Or download latest nightly.

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

At least for the turfing-bots; you have the option of a report. IDK so much about the stubborn humans.

In general; I strongly don’t recommend anything on the Google Play Store except the Google Dialer.

If the Google Dialer is not to your liking; I strongly recommend only trying Dialers you will find on F-Droid.org

It’s nice to know that, at least for places with reasonably civil societies, it’s becoming more and more normal to key your pronoun and gendered speaking choices on modifiable cues like clothing, makeup, hair or appearance in general.

That said; lots of women sound pretty deep too. Maybe more are just openly nonbinary about their expression and have taken steps to deepen it; or it’s just how it’s always been and I’m too derpy to notice because I am recently learning that you don’t focus on someone’s vocal range as I’ve only been openly trans and in a civilized place for a few years total now.

At any rate it’s nice to know that even in a service setting they realize how cheap, easy and good for their reputation it is to just simply respect someone’s communicated preference by double-checking their appearance(s) first before locking in on a pronoun and possibly having to awkwardly correct…when possible.

At a drive through speaker it isn’t; so you were probably expecting them to drone on as if they didn’t bother to even take 2 seconds to see at the window what little, if any makeup you wore, or the color of your nail polish or quality of your self-grooming, regardless of it’s deteriorated state, to affirm that you actually were living as female.

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.

Just a general rule that I always personally follow; Block first, ask later.

This isn’t to say that bringing the harassment to the attention of the mods is a bad thing to do; but it does prevent me from seeing/feeding a possible troll or misanthrope their daily dribble of causing misery.

To echo Gaywallet; “Do report this behavior!”; especially if someone is making it a point to follow you around and harass you in other threads; which is totally not okay on any well regulated or moderator maintained instance.

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.

They could certainly “clearly pass the cost” of this on to the user by not offering Audiobooks to users who didn’t pay for the “+ # of Audiobooks” tier of Spotify Premium; instead of this horrible enshittified crap where it cuts you off midsentence like a greedy telecomm provider would. Or perhaps their limitation should be on how many titles you can listen to concurrently in a certain time period. (So if you open X books; that’s it; you have to shelve one or wait it out)

It certainly means that Spotify did a bad job at negotiating their rights to these audiobooks as well. That matters too; because that makes the product worse; and that should never have been allowed to happen. If they couldn’t have offered it nicely, they could’ve just not offered it at all or added it to a higher service tier so that the cost is diverted better.

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.