provide a URL shortener dump

notslang commented

2017-01-01 14:44:16 +01:00

(Migrated from github.com)

It would be great if this could provide an on-going dump of short URL mappings for the urlteam project, so once 0x0.st (or other sites using this software) dies we can continue to resolve all the links that will break.

It would be great if this could provide an on-going dump of short URL mappings for the [urlteam](https://0x0.st/QX) project, so once 0x0.st (or other sites using this software) dies we can continue to resolve all the links that will break.

mia commented

2017-01-01 21:25:13 +01:00

Hope this helps.

👍 1

FichteFoll commented

2017-01-01 22:30:18 +01:00

(Migrated from github.com)

Is there any interest in allowing to disclose URLs that are intended to be shared privately and are not linked publicly anywhere else?

Exposing all url redirects in an easy-to-access dump kind of equals to them being publicised.

Is there any interest in allowing to disclose URLs that are intended to be shared privately and are not linked publicly anywhere else? Exposing all url redirects in an easy-to-access dump kind of equals to them being publicised.

mia commented

2017-01-01 22:39:13 +01:00

That is not the purpose of 0x0, and you should not use shorteners for private URLs in general. You can just as well figure out the dictionary and block size, and then proceed to query all URLs sequentially. Or just brute force it.

FichteFoll commented

2017-01-01 22:54:20 +01:00

(Migrated from github.com)

I am aware of these possibilities.

For most information, I classify them in three categories:

Can be public, I don't care.
Ideally isn't public but it doesn't really hurt if it is.
Must not be public.

Of course I won't be using shorteners for the third category, but the second category is still interesting. Since the dump is easy to access but not quite as easy to discover, it is most likely still usable for most URLs in that category. Considering how few URLs are currently being shortened, even brute-forcing them would be feasable and the dump doesn't matter in comparison.
Just raising questions.

I am aware of these possibilities. For most information, I classify them in three categories: 1. Can be public, I don't care. 2. Ideally isn't public but it doesn't really hurt if it is. 3. Must not be public. Of course I won't be using shorteners for the third category, but the second category is still interesting. Since the dump is easy to access but not quite as easy to discover, it is most likely still usable for most URLs in that category. Considering how few URLs are currently being shortened, even brute-forcing them would be feasable and the dump doesn't matter in comparison. Just raising questions.

notslang commented

2017-01-03 15:38:02 +01:00

(Migrated from github.com)

Hope this helps.

Awesome, I'll try to get this included in the regular urlteam dumps. :D

Since the dump is easy to access but not quite as easy to discover, it is most likely still usable for most URLs in that category. Considering how few URLs are currently being shortened, even brute-forcing them would be feasable and the dump doesn't matter in comparison.

Yeah, I don't think it's a good idea to consider it as hard to discover - shorteners (who aren't nice enough to provide dumps) are being actively scanned and published in the Internet Archive on a daily basis because of how much link-rot results from the death of a shortener. If someone wanted to, it would be very easy to search through those and wait till something interesting is found, in the same way that people write scripts to watch pastebin sites.

> Hope this helps. Awesome, I'll try to get this included in the regular urlteam dumps. :D > Since the dump is easy to access but not quite as easy to discover, it is most likely still usable for most URLs in that category. Considering how few URLs are currently being shortened, even brute-forcing them would be feasable and the dump doesn't matter in comparison. Yeah, I don't think it's a good idea to consider it as hard to discover - shorteners (who aren't nice enough to provide dumps) are being actively scanned and published in the [Internet Archive](https://archive.org/search.php?query=subject%3A%22urlteam%22) on a daily basis because of how much link-rot results from the death of a shortener. If someone wanted to, it would be very easy to search through those and wait till something interesting is found, in the same way that people write scripts to watch pastebin sites.

provide a URL shortener dump #1