5,087 karma · joined October 25, 2007
Interesting discussion there fortunately.
> The Engineering Working Group (EWG) of the OSMF has “commissioned” (I think that’s OSMF language for paid) a longstanding proponent of rules and complexity to, uh, investigate how to add rules and complexity to OSM.
> [...]
> Let us pray that the EWG is just throwing Jochen a bone to go play in the corner and stop annoying the grownups.
It's a "response" to https://blog.openstreetmap.org/2022/06/02/announcement-data-...
Used Gitpod to quickly run the Git command on our two repos prisma/prisma (https://gitpod.io/#https://github.com/prisma/prisma) and prisma/prisma-engines, downloaded the files, then spent 5 minutes to remove some bots and combine some users, and tadaaa: https://www.preceden.com/git/prisma-prisma-contributors/8303... + https://www.preceden.com/git/prisma-engines-contributors/830...
The unresolved foreign keys are indeed unfortunate, I wondered about these myself when I got my takeouts in the past. I explained them to myself as something that is not actually available in the same datastore to query or join, but maybe a constant or some other system that does not include personal data. Still not nice of course.
I think the wait time and many download buttons were discussed extensively in other comments here. With cold storage as explanation for the duraiton, and just no legal need to make the takeout _convenient_, those also have a pretty good explanation I would say.
So valid, but still no scandal.
My last sentence was triggered by having written a comment on another comment first, which insantly went to -3 (but later kinda recovered), so I almost didn't write this one, just not to have to get the negative feeling. It's a nice Sunday after all.
Takes a bit more tapping and scrolling than clicking on desktop, but that is more he fault of the smaller screen and how apps work I would guess.
If that happens, I am sure Amazon will invest the time and money to comply with that. At the same time it will put many smaller business out of business though, as they do not have the resources to do that. Even the current state of having to fulfill data requests is quite a problem for mayn of them.
It starts with finding the page: Amazon -> Customer Service -> Search for "personal data" -> Search result #1 is "Request Your Personal Information" which nicely explains what to do and links directly to that page.
The need to verify or activate a data request via clicking a link? Of course required so some third party can not just request your data to your inbox (and process it along the way) without you actually wanting to do that.
All the mentions that most of the data is available in your Amazon account? Well, what many people are looking for (order history etc) is and even nicely formatted, searchable and cross linked to make it much more convenient.
Clicking "Remove address" only removes it from the list of addresses? Of course, addresses you ordered to in the past can not be deleted as they have to legally be stored together with other order information.
And the list goes on and on.
I get that it is scary that a big company keeps all the data you gave to them. And it is also unfortunate for you that it is not their business goal to make it instant and pretty for you to look at all the data. But there is no reason for them to do that.
If you don't want Amazon to have your data, don't user Amazon. When you use Amazon, the way you can get a lot of data from them is actually pretty good (also compared to other companies which pretent search history does not exist and so on).
(And bye to some Hacker News points. This will get nicely downvoted I suspect.)
You can add issues to the old Projects from the issue view the same way as the new Projects (beta), it just takes 2/3 clicks for both: On the right sidebar in your issue you have "Projects", then a dropdown of your projects, and then you can (optionally) select the column where to place them (without that selection, the land in some kind of inbox inside the board).
I am using CodeTree for the list view of issues in milestones. The new Projects (beta) unfortunately also only offers that via the in between step of manually adding issues to a project and then "tagging" them with the milestone again as an attribute I think :/
> Prisma currently supports PostgreSQL, MySQL, SQLite, SQL Server (Preview). A connector for MongoDB is in the works, sign up for the Early Access program here (https://prisma103696.typeform.com/to/FriDuIeM).
Transactions were actually included in the last release https://github.com/prisma/prisma/releases/tag/2.1.0 (search for `transactionApi`) in a specific form behind a feature flag (batch transactions, not long running transactions).
No reason not to use the older things if they work for you. But if they don't, never choices might help.
> Given your feedback, we have made the decision to roll back all planned changes related to internal use rights and competency timelines that were announced earlier this month. This means you will experience no material changes this coming fiscal year, and you will not be subject to reduced IUR licenses or increased costs related to those licenses next July as previously announced.
The civil side might be different, but that is not what the parent insinuated. (And yes, my question to the parent was obviously meant to show that I disagree.)