d0ntpan1c

Its somewhat trivial nowadays to make a chrome extension compatible with firefox. I bet if you bother the dev of that site, they could get it done fast, especially since it's a relatively simple thing to do via an extension and I highly doubt it's using any WebExtension API's that aren't standardized between chrome and fieefox.

I'm switching to OSM, personally.

For android, OsmAnd is really solid and make editing easy. (Organic Maps is good too, but much less featured, depending on preferences.) I've started updating all the places I frequent and anything near me that I notice. Its actually kind of fun, to be perfectly honest. Its a small, somewhat selfless thing to do that has an impact on others around you.

IMHO, helping improve an open alternative for the community benefit is a far better act of resistance than a chrome extension that could easily be a GreaseMonkey script, aside from providing a bit of messaging.

Thats absolutely possible via the underlying WebPayments API. The payment "wallet" is linked in the HTML (at least for web pages, RSS, podcast RSS, etc) so someone could design an app that reads these links as QR codes.

The whole point of WebPayments is that and payment solution that you (the "spender") wants to use which is compatible can be used to send money to any compatible wallet.

Whether the payment solution is via government backed, banking systems, or crypto, all it needs to be is compatible.

A valid concern. However, nothing is stopping people from doing the same right now with a big old forced Kofi/patreon/whatever banner, and I'm not sure that this changes that.

The advantage of this over current options is that like RSS, you can consume/deliver it however best suits you without needing to have different accounts of different platforms.

Ah. I think I jumped to assumptions about interledger based on the wallet terminology.

Looks like it's based on the Web Monetization W3C proposal.

https://webmonetization.org/docs/

Looks neat, ~~though I'm always a little hesitant when the thing involves crypto~~. while Interledger is the main driver of the peer-to-peer payments so far, there is nothing stopping a government or banking service from creating an OpenPayment compatible service, so long run there might be a lot of flexibility and less being tied to a specific cyrpto.

Its basically a meta tag that points at a tip jar that's embedded in web pages... This is the same implementation as RSS and only matters to you if you are looking for it or have the ability to act on it.

That means its entirely opt-in and entirely detached from any one company

Chances are they are doing something similar to URL shortening where a reference to the destination and the tracking info is either hashed into the URL directly or stored elsewhere behind whatever ID is in the URL.

Unshortening tools can fetch the actual URL (with any tracking params) in a private context.

I have no idea if anything exists on iOS, but on Android there are tools like URL Check which replace your default browser and let you un-short or otherwise manipulate URLs before opening in a browser or sharing.

1. License settings are available on the website settings

2. Probably the app. I've actually switched to a third party App (Pixilex on android) because I was experiencing a lot of buggy behavior with the official one. It's definitely not ready yet and seems to be buggier on android.

I have no interest in engaging further with your pedantic hypotheticals. Go move the goalposts with someone else.

I wasn't even trying to argue with you. It was just info that didn't require a response since not everyone lives in a corporate computing environment. You are the one who wanted to tilt at imaginary goal posts for no reason. Not every comment in a thread is an argument.

Touch grass and relax a bit. The corporate environment can be properly maintained another day.

Some people aren't a fan of F-droid managing the signing keys and that sometimes F-droid builds/deployments can take a bit. There is an argument for developer-managed signing keys being better than registry-managed signing keys for trust, but that also doesn't make F-droid "bad". While I'm not fully versed on it, I think the issue here only applies to the main F-droid repo since other repos might have different policies around builds and signing keys.

Personally, I like the experience of managing my most used apps through Obtanium via the devs git releases, but I only use that if the dev is good about publishing their signing key so it can be verified with AppVerifier. Otherwise, F-droid is safer than running an app installed without verifying the signing key.

Not everyone at a company can be managed by group policy or in-tune or whatever. Like if they aren't using windows. You can run into the same situation on macOS or Linux depending on if you have the old and/or new clients installed at the same time.

I was curious too (tho I don't really partake in the community) and this explains the situation:

https://lemmy.blahaj.zone/post/20976989

Prob a highlight of how Lemmy needs to solve community migration cross-instsnce properly as well as how community moderation vs. instance moderation will always be a problem in reddit-like fediverse implementations.