Kyle Rankin @kyle@librem.one

Update: I gave up and decided just to fix my tags. I used Picard for the first time and it made what would have been a horrible task surprisingly easy.

@Phaserune Yeah I think at this point it's actually less effort to painstakingly fix tags than it is to find/patch a media player.

@iooioio I have cleaned tags up over the years but I haven't gone album-by-album. It's the inconsistency in tags (slightly different artist/album spelling) that ends up being the most annoying.

I have a well-organized but inconsistently-tagged music collection, so it's frustrating that music apps rely so much on tags and infuriating that most remove file browsing entirely.

Update: Kashmir Hill's piece in the NYTimes today describes a US startup that's providing law enforcement the exact kind of facial recognition tech I was warning about in China. China's present surveillance state is becoming our future. #privacy https://www.nytimes.com/2020/01/18/technology/clearview-privacy-facial-recognition.html

Popey suggested I try out yad and I like it! Looks like it supports some more use cases than zenity, is supposed to be lighter weight, plus it's faster to type. Check out the file dialog on the Librem 5!

I discovered today that zenity works as well on this screen as it does on a regular desktop to create basic shell-driven GUI programs on the #Librem5 so you can expect to see some simple apps from me in the future.

@ehowell @setthemfree I don't know. While there are many issuers for credit cards, there are only a few networks (Visa/MC/AMEX/Discover/etc) so even if your issuer doesn't sell your data (the one I built infrastructure for didn't), if the network does (as this thread shows MC does) there's not much you can do.

With a strictly debit card (no CC features) I suppose the issuing bank and/or company managing the card infrastructure could offer #privacy for you.

There's also always cash :)

@daniel The phone doesn't know its location yet (GPS isn't enabled, I don't believe Epiphany browser even supports such a thing if it were enabled). It was a *competitor* to the specific medication I bought but in the same category of drug.

1. Buy medication I never have bought or even searched for before at local pharmacy w/ credit card
2. Go to car, decide to test #Librem5 cellular by visiting my account on mobile.twitter.com
3. Immediately see ad for type of medication I bought!

No location tracking possible on this Librem 5 (used browser, not native twitter app), so either a crazy coincidence, or near-real-time reporting between CVS and #adtech w/ linking between my name, card, and twitter account.

Something I didn't know I was missing but now use all the time on my #Librem5 is writing a shell script to perform a task along with a local .desktop file to run it from the home screen. Adding notify-send commands gives me feedback as the script runs in the background.

This is a fun story describing the security measures Tiffany used when it moved millions of dollars of jewelry down to street to a new location: https://www.nytimes.com/2020/01/13/nyregion/tiffanys-store-closing.html

It's refreshing to see a major vulnerability with vanilla advisory pages and no branding. Anyone but the NSA would have registered ecc.fail or ecception.org to pair w/ their BH submission.

If your app wins this war, maybe you won't care, but history tells me tech giant dominance is temporary. All those devs writing proprietary msging apps today are writing tomorrow's abandoned code. We'd all go much farther if we went together. Thank you for coming to my TED talk.

We still haven't learned the lesson. The next decade promises even more duplicated effort as each org reinvents proprietary e2e encryption protocols on private networks in the name of privacy, but with the effect of making compatibility almost impossible.

Is it really better that FB has three incompatible msging apps they now have to wrangle into one new proprietary protocol? In the 20 year fight to own the market, all we have to show for it are mountains of abandoned proprietary code, dead networks, wasted efforts.

These companies went fast alone, but they didn't go far. The last 20 yrs show few real innovations in msging. How many attempts has Google made? If they all had worked together, you wouldn't have a half-dozen incompatible messaging apps with similar features on your phone.

The buildings full of devs he references all labored over the past two decades to reinvent the same messaging wheel, but w/ a network they owned. Libpurple plugins serve as a graveyard of proprietary chat protocols--failures to capture the market, wasted dev effort.

There's a well-known African proverb: "If you want to go fast, go alone. If you want to go far, go together." What Moxie's centralization talk misses is that the faults in early decentralized protocols came because dotcoms wanted to capture the market.

https://invidio.us/watch?v=Nj3YFprqAr8