PierceTheBubble
Spotlight, uh, moonlight, uh, eyesore get your fucking aim right 🎶
‘okay, this is David, remember this person.'
Well, that wouldn't be creepy for someone to say. And the “the cocktail party problem”, really? It's generally much more awkward if a person you hardly remember, greets you like you're their best friend. But I guess you should also start wearing these glasses, right? So we can all be pretentious douchebags, instead of just humbly asking if we've met before. And I can't wait for creeps to give slideshow presentations to these glasses, so they have an arsenal of women to hit on: pretending like they've met these women before...
... drones often alter natural behavior simply because people or animals notice them. The disruption can cause wildlife to scatter and people to behave differently.
Ah yes, humans in their natural habitat: blissfully unaware to the fact that their every move is being monitored, mocking the "tin foil hatter" trying to convince them otherwise.
This is the best possible outcome for Google: providing alternative application stores through the Play Store. So any application, including alternative application stores, are subject to universal app verification rules: allowing it to fully kill "sideloading" (as in: installing an APK from the web); while technically providing alternatives, gatekept by Google. The latter will likely just result in Play Store mirrors, that hardly provide any real competitive advantage over upstream. A purely symbolic, absolute joke of a court case.
I might or might not disagree with you, but I have nothing to go on.
I think there's a distinction to be made between solutions which are client-side, versus those that are server-side, or at least have a server-side component that is functionally necessary.
For the first category, the termination of a subscription shouldn't lead to denial of access to the current build of the software: it should remain functional in the absence of lower-level updates. Ideally this software is sold as a one-time purchase, having life-time free updates bundled, or sell upgrades on a versioned basis; but a subscription fee for future updates seems perfectly reasonable too, if the previously stated conditions are met.
For the secondary category I believe it's in the service's right, to provide it's products on the basis of its own terms and conditions; that is, if it doesn't employ morally questionable practices, like: outpricing other services using venture capital, for the purposes of attracting a user-base for future exploitation (by raising fees, or by turning the user into the product; despite an ever decreasing value proposition: i.e. venture capital enshittification).
Algorithmic feeds are the problem here, which are exacerbated by features like autoplay and infinite scrolling. Users should by default only be served content from channels they explicitly chose to subscribe to. Algorithmic feeds should be separate from this subscription-based feed, and only bleed over if subscribed to said channels; which shouldn't be any different for shorts (only showing shorts from subscribed-to channels, if not hidden altogether when preferred). Simply put: make timelines finite again, by not endlessly resupplying it with spam; which includes the unhealthy amount of "sponsored content".
In the context of spy satellites, (nuclear) weapons and drone bases in orbit, I honestly can't wait for the Kessler effect to materialize. Russia has demonstrated it could destroy a defunct Soviet satellite in orbit using a missile, and with tensions rising, alongside the number of objects placed in orbit, it doesn't seem like a matter of if, but rather a matter of when it unfolds.
Most "name brands" have long been acquired by large umbrella corporations, and shortly after doing so, the "brand recognition" is often leveraged to market white label products; which is increasingly the only differentiator between it and off-brand products. That, and the price-difference: simply paying more for a meaningless "name brand", on an equally inexcusably poor quality product; besides a slightly less shitty customer experience, hopefully.
I really think it's poor design to purely filter on appearance of brands, rather than actual brand reputation. Yes, it might serve as an overgeneralized indicator for questionable reputation, but marketable brands shouldn't be treated as reputable either.
Am I the only one that finds it ridiculous, non-E2E encrypted cloud storage isn't protected from mass-scanning (against opaque cryptographic hashes)? Just because one technically could, and "nothing in the law prevents" a provider from doing so, or a legal basis is explicitly being provided (in case of the EU's Chat Control), doesn't mean one should. You're still preemptively scanning private content, and it should be irrelevant whether or not it's encrypted.
I've frequently criticized Apple in the past, but I can't do anything other than praising them for dodging this privacy-nightmare; unlike services provided by the likes of Google or Meta, that actively encourage the use of unencrypted options by default, while happily "volunteering" in case of the EU's Chat Control.