I was at a trampoline park last weekend (regular kind of place, everything padded for safety, as you'd imagine).
A ten year old kid left in an ambulance, neck injury, one side of the body paralyzed at the time of the event.
I really hope the kid recovers... but I don't think I'll ever forget that image.
Yes, everything in life has risks, but I don't even want to imagine how I'd feel if my kid, or my kids' friend had a life-changing injury on a trampoline at my home.
There are many other factors to consider however. Such as time spent with friends, doing something physical, etc. Plus, there’s a spectrum of ways to use trampolines. You’re still allowed to parent…
> The tendency of Wikipedia editors is that, when an article is many years old, they would rather flag it for improvement rather than simply throw away years of fellow editors' work.
That's not been my experience, tbh - in my view the deletionist fraction of the editors has essentially "won", if one can put it in those terms. I _think_ there is a (maybe small) group that have decided it is their mission to guard Wikipedia against what they view as cruft or non-notable, regardless of how many years of work these articles may have accumulated. They do not need to be paid for this - they enjoy it. Destroying is always easier than creation.
I seem to recall some study showing that the vast vast majority of edits/deletes on Wikipedia are the work of just a few hundred long-standing editors (citation needed) - which to me confirmed my gut feeling that most new editors bounce off and give up on contribution in short order.
I contributed for a few years, but gave up eventually - it was exhausting to spend time collating sources, collecting information, editing, rewriting, and then having someone come along and propose discarding your work with very little investment from their side.
Stackoverflow has gone through similar calcification - it's nearly impossible to contribute now, or build reputation as a new user, as posts get closed as duplicates or not-relevant.
> I seem to recall some study showing that the vast vast majority of edits/deletes on Wikipedia are the work of just a few hundred long-standing editors
I'm fairly sure I've seen statistics that say the opposite of that (citation needed), so I'd like to see that study.
Hmm, that seems to contradict the article directly - insecticides were used to try to battle screwworm initially and were not really effective - the solution was using sterile male flies to stop reproduction - which would work in South America just as well as it did in North (with sufficient scale)
Lemma 1: you want to protect your users privacy, and are also beholden to regulation enforcing that commitment (GDPR).
Lemma 2: you are obliged by other regulation to offer equal access to user data to third parties, so others can build equivalent functionality (DMA).
Lemma 3: malicious third parties will absolutely try to abuse the access and trick the user into sharing their data by all means possible. You will be held responsible in court of public opinion at minimum and legally at maximum if/when a malicious third party abuses said access.
This is a hard, possibly technically unsolvable problem no matter how much money you might have, because the root issue is not technical, it's the fact that you legally have to give third parties access and no way to control what they do with it - and as others have mentioned in the threads, it's exacerbated by the fact that the regulation doesn't say "this is okay and this is not", it is vague and judges things "by outcome", so you may spend all the time in the world implementing a solution you think will work, and then get hit by fines/lawsuits because the implementation is judged as not sufficient after the fact.
I am not sure this is as much of a tension as you make it sound: where is the obligation that a marketplace administrator will be blamed for any and all breaches of data privacy trust from a participating (likely malicious) third party?
According to GDPR, the app developer is the "data controller" and thus ultimately responsible. Only in the case where Apple knowingly participated in unlawful behavior is it likely to be held accountable, and even then, in addition to the app developer. Obviously, if we are not talking about leaks from the actual App Store system (eg. Apple account logins and user data).
So while it sounds plausible, the legal framework is exactly not what you describe here — Apple can claim to want better protection for customers by not allowing third party apps, but EU rejects that (it can similarly extend to app store itself) and pushes for competitive landscape with DMA instead.
Like they now hand over all your contacts, your location, calendar entries, microphone access, camera access. If you choose to do so.
Nothing holds them from having designed this as an API that others can use where the user has permission toggles of what data they want to share with the LLM provider.
This is clearly very different from usual permissions and access.
This would be unprecedented access to user data, enabling the most complete user profiling ever.
Ad companies, like Meta and Google, are going to spend huge amounts of money getting agents ready, because there will be a ridiculous amount of money behind all the data they're going slurp up, and the profiles they'll build for you.
Unless, Apple can figure out how to keep the leaches, that have consistently proven to be so, with court cases for receipts, at bay.
Interestingly, they claim to have done this and offer it as an API layer (Trusted System Agent) for other agents to use.
There is just this minor point that their own agent simply doesn't use it and goes directly to lower level interfaces nobody else gets access to: exactly the thing DMA was designed to stop.
1: If you want to protect user's privacy, you collect no personal information, so GDPR doesn't apply.
2: You do that.
3: Since your platform collects no private information, they get nothing from you. If they collect private information on their own, it's their job to comply with GDPR.
What you should do in case (3) is ask the user for permission to allow the 3rd party access to private data on their device. It's their choice (not yours) to allow it or not.
Very interesting - I just installed pg_hint_plan [0] extension a few months ago to get around a query that was confusing the planner too much. Edge case, but when you need it you really need it.
Time to revive my account... (scrobbling since 2003, heh) - started in audioscrobbler days, before last.fm
My usage has gone way down since switching to streaming services, this made me search for ways to backfill the data...
For anyone using Apple Music, looks like you can request an export of your data from privacy.apple.com, then use https://github.com/nerveband/Apple-Music-Play-History-Conver... to convert it for Last.fm import (haven't tried it yet, but looks promising).
Would be nice but it can't be done. I stopped scrobbling in 2011, then found out the site was still alive in 2024, one email to support later and I was back in.
I wanted to import my Spotify listening history from the intervening years, but found that the LFM API limits scrobbles to no earlier than two weeks ago. A shame, because my current listening history is now very skewed between the two "eras".
Yes, they are duplicates, although the links themselves are distinct. The current post points to my website, whereas the other points to my Git project. But they are indeed duplicates, in the sense that both refer to the same project.
Further, this post is from a new account with no posting history that has copied my submission (along with the exact wording) from <https://lobste.rs/s/hjipba/>. Copying the wording is no problem at all. I appreciate the visibility this post is bringing to this rather little project of mine. But I am not sure whether this post was made by a genuine user or by a bot. Any clarification from the poster or the moderators would be helpful.
I am also worried that one or both of these submissions may get flagged as duplicates. I had submitted the project myself earlier today at <https://news.ycombinator.com/item?id=47422759> but it did not gain any traction. I have emailed the moderators to ask whether it would be possible to merge the multiple stories into one.
A ten year old kid left in an ambulance, neck injury, one side of the body paralyzed at the time of the event.
I really hope the kid recovers... but I don't think I'll ever forget that image.
Yes, everything in life has risks, but I don't even want to imagine how I'd feel if my kid, or my kids' friend had a life-changing injury on a trampoline at my home.