vanity paste IDs

[buhman]

#48 breaks the current vanity paste-id mechanism/hack. There are two ways to un-fuck this (provided we want to un-fuck it):

1. roll our own auto_increment that has the behavior we want (hard, likely slow)

2. make another secondary index (easy, fast, could cause collisions)

[jdppettit]

Can you give me a better idea of the use case of this? Do you mean like making a paste /foo instead of the randomized ID?

[buhman]

In particular, @polyzen among others want something like:

https://ptpb.pw/polyzen

His flow generally involves using only PUT whenever he wants to paste, and then just spitting out the same ptpb.pw/polyzen URL.

---

Somewhat related, I had a similar-ish idea for buhPaste: where instead of URL paths, each paste gets a unique IPv6 address (if a /64 is dedicated to the task, that means 2 ** 64 possible pastes).

The 'vanity' name in that scheme would work something like: you create an AAAA (and optionally A) record for some arbitrary DNS name. If the AAAA is connected to, things proceed as normal; if the A is hit, we look up the AAAA record for the same Host:, then proceed with routing as usual.

The server only keeps track of IPv6->paste mappings, and not vanity names.

This could be combined with buhDNS (and we could work on a nice public TSIG-generation HTTP API for that). If we moved authority of ptpb.pw and/or ppb.io to czar, we could then hand things like polyzen.ptpb.pw.

---

The latter is super nice because we can then accept arbitrary vanity names of any length with no collisions with regular paste IDs.

What do you think?

[jdppettit]

I like the vanity paste idea (the first part). The second part is either ridiculously awesome or ridiculously dumb, can't decide which. I say put the second part on the drawing board for future stuff, the first part sounds good to do now.

[buhman]

18:35:27 jpettit I think we should do post at /yourshit and retain the ability to change with put

[buhman]

These will be their own special kind of paste in a special table.

The route is going to need to be something like /<string(minlength=5):vanity> on both GET and POST.

Shouldn't be hard after that.