another-dave
Joined 13 years ago
Joined 13 years ago
If every did get UBI, I'd imagine there would still be some who'd choose to attend (or teach at) universities for the love of knowledge.
In the same way there would be book clubs, writers' groups, 5-a-side football teams etc etc
Is it as good as capturing everything for them? No, of course not. But then don't frame the whole thing as "if you're on an enterprise plan we won't train on your data"
There's a whole spectrum of things they could do from most to least aligned with that as a principle.
For example, they could have a thumbs up/down
- just track the metadata of the conversation (e.g. model used, how far through its context it was, how old the session was) - track metadata of the user as a whole (how often they use Claude, how many other "active" conversations they have on the go, how much they've tested other models, if this is their first time using new tweaks to params etc) - have contextual feedback of the chat available for humans to review (alongside the comments you put in the feedback), but not explicitly train on it.
Whereas the option they've chosen is:
> If you explicitly report feedback or bugs to us (e.g. via our thumbs up/down feedback button), or otherwise choose to allow us to use your data, then we may use your chats and coding sessions to train our models.
So literally using your session as training input. They also could've allowed this to be an opt-in on bug reports.
They're comparing the tempo deviation not just in the drums but in literally everything.
Billie Eilish may be singing over a drum machine rather than a live drummer but that wouldn't make _her_ perfectly on time.
It was a bit of "let's not forget this element of application development".
If I record the songs playing & they sell bootleg CDs, I don't have a defence of "but it was played in public, so all copyright was waived". That's not how copyright works.
One suggestion - external contacts won't know that this address will bounce for anyone they add in CC. Maybe have an option where if I include the original whitelisted domain/person in the chain then it will let the mail through even if it's from a non-whitelisted person.
Just thinking of scenarios like, you give out your email address to <[email protected]> who then emails you about a 5-a-side game with a few friends but any messages from any of the other friends bounce.
Or you apply for a job at ACME Inc and then you get a message back from `[email protected]` saying, please coordinate with `[email protected]` who'll arrange the interview but Bob can't contact you
It may be that a lot of it is aesthetics (though aesthetics also matter to usability) but some of it is richer functionality.
For example, a pattern I've been asked to implement multiple times is a requirement like this:
"We should have a 'Country prefix' input for a telephone number on the form. It should be a list, but allow the user to filter. They should be able to search by code (+44, 0044) or by country name (United Kingdom). We want a little flag beside the input".
Now I _can_ do that myself from browser APIs, e.g. using something like a datalist, using emojis for flags. But then I've to handle stuff like Win/Chrome not even supporting the emoji properly. Chrome will autocomplete based on label or value but FF won't. Even though there's a datalist, I can't constraint the input to _only_ select one of those values, so I need to do additional client-side validation on inputs anyway.
Then if a designer said of an 'contact book' look-up (e.g displaying an profile photo of people instead of a flag) I now have to come up with some other custom field anyway, to support that.
I think the browser level APIs and supported tags have come a long way from where they were, but they're still at the level of primitives. The libraries people are reaching for are one level above that.
But we've well established patterns on the web now that there's no reason we couldn't have richer OOTB browser chrome and remove the need for a lot of this stuff getting reimplemented in libraries all the time.
It seems strange to disallow the carrier, have the belt that loops through the adult belt but then if the plane is going down you have to get them into the same position they'll be in in the carrier anyway!
Erling Haaland gets half a million a week. His contract is worth £260m.
These guys take the money because it's on offer to them, and fair play to them.
But I don't think they'd decide not to play football and go off to do something else if he were to "only" get, say £5.2m over 10 years instead (£10,500 per week).
wouldn't have as much funding, sure, but football was massively popular long before they started putting logos on shirts & hoardings.
If there was less money involved in football, then the likes of the free-to-air stations would be in a better position to compete to show more matches, too
what exactly is the 'threat model' that you're trying to protect against here? If you already don't trust John Doe as a credible source, of course then there's a million ways he can frame a scene to tell an unreliable story. That's always been the case.
But to me, what we're looking for now in the age of diffusion models is for someone to be able to say "here is the provenance of this image, it came from John Doe's camera" and that can survive being shared round the internet, provably.
> You could end up loading a gig of data for a single article with 10 images, or even more for larger frames.
I'm not suggesting that the _only_ thing that gets used is a raw image. I'm saying that if you go to the Wall Street Journal, then underneath the photo, beside the credit, they put a link out to some page that hosts the RAW file, the metadata of the camera used and a signature.
If you find the photo unbelievable and think it's bogus, you're able to regenerate the signature from the parts and see that it's valid. (and obviously if they link off to something that's massively different - that isn't just compression, white balance, etc - people hold them to account)
Yes but there's a big difference between "only import electronics that aren't fire hazards" and "you have to pay custom & excise on anything you import".
[ my public key: https://keybase.io/anotherdave; my proof: https://keybase.io/anotherdave/sigs/_k6RGHSRbF90qKa58ejkKAbyWJTd2qQqeMjsx-BBmTY ]