| ▲ | zahlman 12 hours ago |
| > 00000000-1111-2222-3333-444444444444 = { name = "REPLTreeViews", path = "R/REPLTreeViews" } ... Should it be concerning that someone was apparently able to engineer an ID like that? |
|
| ▲ | ekjhgkejhgk 12 hours ago | parent | next [-] |
| Could you please articulate specifically why that should be concerning? Right now I don't see the problem because the only criterion for IDs is that they are unique. |
| |
| ▲ | zahlman 11 hours ago | parent [-] | | I didn't know whether they were supposed to be within the developer's control (in which case the only real concern is whether someone else has already used the id), or generated by the system (in which case a developer demonstrated manipulation of that system). Apparently it is the former, and most developers independently generate random IDs because it's easy and is extremely unlikely to result in collisions. But it seems the dev at the top of the list had a sense of vanity instead. | | |
| ▲ | KenoFischer 10 hours ago | parent [-] | | You're supposed to generate a random one, but the only consequence of not doing so is that you won't be able to register your package if someone else already took the UUID (which is a pain if you have registered versions in a private registry). That said, "vanity" UUIDs are a bad look, so we'd probably reject them if someone tried that today, but there isn't any actual issue with them. |
|
|
|
| ▲ | skycrafter0 12 hours ago | parent | prev | next [-] |
| If you read the repo README, it just says "generate a uuid". You can use whatever you want as long as it fits the format, it seems. |
|
| ▲ | adestefan 12 hours ago | parent | prev [-] |
| It’s as random as any other UUID. |
| |
