Except for 'reader apps' (those that sell digital content, basically) which Amazon is. Plus, Apple's rules are applied unevenly; Amazon is a giant WebView on Apple TV but it's disallowed for everybody else.
As far as I understand, what "reader apps" were allowed to do was to display content purchased elsewhere in the first place, which is orthogonal to being/not being allowed to link to external purchases, no?
These are the changes that Apple was forced to make, specifically referencing 3.1.3 (Other Purchase Methods) and 3.1.3(a) (“Reader” Apps):
> 3.1.3: The prohibition on encouraging users to use a purchasing method other than in-app purchase does not apply on the United States storefront.
> 3.1.3(a): The External Link Account entitlement is not required for apps on the United States storefront to include buttons, external links, or other calls to action.
The bit about the (formerly required in the US) entitlement is:
> Reader app developers may apply for the External Link Account Entitlement to provide an informational link in their app to a web site the developer owns or maintains responsibility for in order to create or manage an account.
They required you use a trackingless, generic URL that was unvarying per user, so you probably didn't run into it super often. Offhand, the Kobo app did use it.
I recently started making the switch from docker (and docker compose) to using podman and quadlet, but holy crap is the documentation for podman quadlets a big f-you wall-of-text mandoc that would make Torvalds proud. I've read thru that and am still not quite sure of how to get from point A to point B.
To replace a single docker compose file, sounds like one needs to manually create a number of .container, .volume, .network, .kube files correctly so systemd can spin up a container pod? Is that what I'm reading? Is there nothing that can generate that from a docker-compose.yml?
I agree. That documentation really needs some love. But if you see the discussions on github issues about quadlet features a common theme is maintainers dismissing requests because "that shouldn't be done in production" or "that won't scale". It seems they can't wrap their head around people wanting to do simple things or someone doing things by themselves at home and not for work at a big company or corporation, and that reflects on that documentation.
Working for one myself, which does have a support contract wit Red Hat, I kinda get where they're coming from--if they make it easy to shoot yourself in the foot, dumb people shoot themselves in the foot in production and they have to fix the mess later. But for that they could have a sanctioned build for clients and a community build for everybody else, just like they have Fedora and RHEL.
You are wrong. Your searches are still sent to the original search provider before the redirect extension takes over. It defeats any privacy Kagi could possibly provide.
Facebook never federated so their implementation was just an API they couldn't control to them:
> Facebook Messages are evolving to allow people to share rich content beyond text: photos, videos, audio and even stickers. We want to ensure the best possible send and receive experience where all these rich forms of content are reliably and consistently available on every platform. XMPP doesn't support all these (and future) content types, and it's difficult to ensure an XMPP client is rendering them appropriately. As such we've decided to sunset the XMPP Chat API.
> XMPP doesn't support all these (and future) content types, and it's difficult to ensure an XMPP client is rendering them appropriately. As such we've decided to sunset the XMPP Chat API.
This is such a lame excuse, and reveals how much they're control freaks. One of the main points of an open, federated protocol is that people can choose clients that behave the way they want and render things the way they want. "Oooohhh, we can't guarantee with an iron fist that our stupid 'stickers' render correctly on all clients, therefore we can't deal with it!"
This same mentality infests the web, and is why companies insist on slathering JavaScript into everything to force browsers to render their pages exactly as designed, rather than just letting the user agent serve the user's needs.
I think this is a pretty great step in the direction of not being wholly dependent on one platform; makes you start thinking about your website as the source and the social media networks as just a representation.
Fish is such a great shell. More often than not it reads my mind about what to do (e.g. with its fantastic history autocomplete), but I’m really excited for this minor breaking change note:
> alt-left and alt-right will now move by one argument (which may contain quoted spaces), not just one word like ctrl-left and ctrl-right do.
I've been doing this on rsync.net since at least February; works great!