Difference between revisions of "User talk:Bwn"

From Archiveteam
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''Can anyone think of any additional fields that would be useful to sort on?
== Researching URL Shorteners ==
'''
Here's what to do when you've come across a new URL shortener that should be archived. At minimum, please follow the first step. Anything beyond that is more helpful. Even if you don't know of any shorteners not on the list, additions, updates or verification of the information in existing shortener entries is very welcome!


{| class="sortable wikitable" style="width: auto; text-align: center"
* Add it to the [[URLTeam#Alive|Alive]] section of this page in alphabetical order and include the current date. Please include whatever information you have, but at the absolute minimum, we need the domain.
! Shortener
** To add a new shortener to the [[URLTeam#Alive|Alive]] section, you can follow this template:
! Last Checked on
<pre>
! Notes
|- 
| shortener url || date (YYYY-MM-DD) 
| information you have gathered on the shortener 
</pre>
* Check the homepage. Is there a public method to create a shorturl? If so, create one and include it in the entry. If not, note that in the entry.
* If you were able to create a shorturl, try making a second. Is it sequential? For example, if the first link was foo.bar/dbE4g and the second link is foo.bar/dbE4h (or very close to it), it's probably sequential. If you get foo.bar/dbE4g followed by foo.bar/g4rTh, it's probably random. Note in the entry whether the shorturls are random or sequential.
* Run <code>curl -I http://url.short/validshortcode</code> and see which HTTP status code is returned. Also note whether it returns the destination in the Location: header. Note both in the entry.
* Run <code>curl -I http://url.short/invalidshortcode</code> and see which HTTP status code is returned. Note that in the entry.
* If the above fails, make a note of it in the entry and try using <code>curl -i</code> instead of <code>curl -I</code>
* Check the homepage, and see if they give a total number of shorturls that their service provides. If so, note that in the entry.
* There are browser plugins/extensions available to make the requests described above from your browser for those without access to <code>curl</code>/command line. (Examples: Advanced REST Client, REST Console)


|-
| 1o2.ir
| 21:05, 15 May 2016 (EDT)
| site is in Arabic (I think); seems alive as of 21:05, 15 May 2016 (EDT)


|-
Was:
| 2tag.nl
| 21:05, 15 May 2016 (EDT)
| seems alive as of 21:05, 15 May 2016 (EDT)


|-
== Researching URL Shorteners ==
| 9en.us
Here's what to do when you've come across a new URL shortener that should be archived. At minimum, please follow the first step. Anything beyond that is more helpful.
| 21:05, 15 May 2016 (EDT)
| appears to charge for creating shorturls; seems alive as of 21:05, 15 May 2016 (EDT)


|-
* Add it to the [[URLTeam#Alive|Alive]] section of this page in alphabetical order and the current date (hint: 5 tildes (<nowiki>~~~~~</nowiki>) will do that automatically). Please include whatever information you have, but at the absolute minimum, we need the domain.
| ad7.biz
* Check the homepage. Is there a public method to create a shorturl? If so, create one and include it in the wiki. If not, note that in the wiki.
| 21:05, 15 May 2016 (EDT)
* If you were able to create a shorturl, try making a second. Is it sequential? For example, if the first link was foo.bar/dbE4g and the second link is foo.bar/dbE4h (or very close to it), it's probably sequential. If you get foo.bar/dbE4g followed by foo.bar/g4rTh, it's probably random. Note on the wiki whether the shorturls are random or sequential.
| pays short URL creators; seems alive as of 21:05, 15 May 2016 (EDT)
* Run <code>curl -I http://url.short/validshortcode</code> and see which HTTP status code is returned. Also note whether it returns the destination in the Location: header. Note both on the wiki.
* Run <code>curl -I http://url.short/invalidshortcode</code> and see which HTTP status code is returned. Note that on the wiki.
* Check the homepage, and see if they give a total number of shorturls that their service provides. If so, note that on the wiki.


|-
| adf.ly
| 01:38, 10 November 2015 (EST)
| incremental, but displays interstitial ads, so requires custom code; Ex: http://adf . ly/bnpYL ; http://adf . ly/1RP4DP (current as of 01:38, 10 November 2015 (EST)) (alias q.gs )


|-
| adfoc.us
|
| displays interstitial ads; appears to block curl; so requires custom code


|-
| asso.in
| 21:05, 15 May 2016 (EDT)
| seems alive as of 21:05, 15 May 2016 (EDT)


|-
''' Official Shorteners '''
| at5.us
| 21:05, 15 May 2016 (EDT)
| seems alive as of 21:05, 15 May 2016 (EDT)


|-
{| class="sortable wikitable" style="width: auto; text-align: center"
| at.cmt.com
! Shortener
|
! Last Checked on
| Country Music Television - Appears to be a vanity domain hosted on ow.ly infrastructure.
! Notes


|-
|-
| b23 dot ru
| ask.fm ||  
| 15:05, 2 January 2016 (EST)
| Ex: http://ask.fm/a/40k05kgp -> http://ask.fm/Q7Niki/answer/42128504404 ; seems non-incremental
| seems alive as of 15:05, 2 January 2016 (EST)
 
|-
| bc.vc
|
| displays interstitial ads ; Example: http://bc . vc/8nCbMs
 
|-
| bernie.to
| 17:24, 21 March 2016 (EDT)
| No public method for creating shortcodes. Homepage redirects to campaign homepage. 307 Proxy Redirect for (vaild) bernie.to/pb and /vol and same status code for invalid shortcode. Seems to all be custom names, according to those used on reddit: http://reddit.com/domain/bernie.to As of 17:24, 21 March 2016 (EDT)
 
|-
| budurl.com
| 02:03, 7 December 2015 (EST)
| Appears non-incremental, apparently all custom names; only paying clients allowed to create URLs (checked as of 02:03, 7 December 2015 (EST))
 
|-
| buff.ly
| 02:03, 7 December 2015 (EST)
| Buffer App ; ex: http://buff . ly/1fPIjQf (301 - existing; 404 - non-existing), non-incremental (checked as of 02:03, 7 December 2015 (EST))
 
|-
| buzurl.com
| 23:40, 19 December 2015 (EST)
| Example: http://buzurl . com/li04 ; link broken, home page is blank as of 23:40, 19 December 2015 (EST)
 
|-
| canurl.com
| 15:05, 2 January 2016 (EST)
| Contains various random essays on URL shortening & spam; not clear if the shortener still exists as of 15:05, 2 January 2016 (EST)
 
|-
| cl.ly
|
| CloudApp ; requires application to create short URLs
 
|-
| cur.lv (CoinURL.com)
|
| Subdomains include: bit, go, in, jump, link, me, my, n, name, now, to.
 
|-
| decenturl.com
| 01:35, 10 February 2016 (EST)
| Makes human-readable URLs from page titles; not at all easy to scrape. Requires one-time payment and registration to create URLs as of 01:35, 10 February 2016 (EST)
 
|-
| del.ly
|
| sprinklr
 
|-
| dfl8.me
| 01:35, 10 February 2016 (EST)
| previously had an archive of created URLs; requires a (broken) captcha to create URLs as of 01:35, 10 February 2016 (EST)
 
|-
| digbig.com
| 01:35, 10 February 2016 (EST)
| no longer accepting new users as of March 1, 2014; site appears to still be up as of 01:35, 10 February 2016 (EST)
 
|-
| dlvr.it
| 01:36, 2 November 2015 (EST)
| Requires free login; then requires connecting to another service; URLs are shortened when sent through. ( as of 01:36, 2 November 2015 (EST))
 
|-
| dogeurl.com
| 00:00, 21 December 2015
| Alive 12-21-2015 Non-incremental, alphabet A-Z a-z 0-9, 6 characters long, with custom option Valid: 301 to destination, Invalid: 302 to https://dogeurl.com/invalid.php
 
|-
| doiop.com
| 01:35, 10 February 2016 (EST)
| Appears non-incremental ; allows unicode in short codes; appears alive as of 01:35, 10 February 2016 (EST)
 
|-
| durl.me
| 22:00, 21 November 2015 (EST)
| appears to allow public creation of shorturls; as of 22:00, 21 November 2015 (EST)
 
|-
| easyurl.net
| 01:35, 10 February 2016 (EST)
| (alias: atu.ca , readthis.ca , clickthru.ca , redirects.ca ) Appears non-incremental; only available to customers of easyDNS.com ; Ex: http://easyurl.net/afd2f ; seems alive as of 01:35, 10 February 2016 (EST)
 
|-
| fav.me
|
| Used by DeviantArt. Ex: http://fav . me/d31sfml
 
|-
| filoops.info
| 01:15, 29 January 2016 (EST)
| Appears to allow public shortening; seems alive as of 01:15, 29 January 2016 (EST)
 
|-
| firsturl.de
| 01:20, 17 February 2016 (EST)
| Appears alive and allowing public shortening as of 01:20, 17 February 2016 (EST)
 
|-
| flip.it
|
| Flipboard
 
|-
| flpbd.it
|
| Flipboard
 
|-
| fnd.us
|
| (See offical shorteners)
 
|-
| fos.hu
|
| incremental alphanumeric, but shares pattern with an image sharing service


|- class="sortbottom"
|- class="sortbottom"
Line 182: Line 49:
! Notes
! Notes
|}
|}
'''G'''

Latest revision as of 02:56, 13 June 2016

Researching URL Shorteners

Here's what to do when you've come across a new URL shortener that should be archived. At minimum, please follow the first step. Anything beyond that is more helpful. Even if you don't know of any shorteners not on the list, additions, updates or verification of the information in existing shortener entries is very welcome!

  • Add it to the Alive section of this page in alphabetical order and include the current date. Please include whatever information you have, but at the absolute minimum, we need the domain.
    • To add a new shortener to the Alive section, you can follow this template:
|-  
| shortener url || date (YYYY-MM-DD)  
| information you have gathered on the shortener
  • Check the homepage. Is there a public method to create a shorturl? If so, create one and include it in the entry. If not, note that in the entry.
  • If you were able to create a shorturl, try making a second. Is it sequential? For example, if the first link was foo.bar/dbE4g and the second link is foo.bar/dbE4h (or very close to it), it's probably sequential. If you get foo.bar/dbE4g followed by foo.bar/g4rTh, it's probably random. Note in the entry whether the shorturls are random or sequential.
  • Run curl -I http://url.short/validshortcode and see which HTTP status code is returned. Also note whether it returns the destination in the Location: header. Note both in the entry.
  • Run curl -I http://url.short/invalidshortcode and see which HTTP status code is returned. Note that in the entry.
  • If the above fails, make a note of it in the entry and try using curl -i instead of curl -I
  • Check the homepage, and see if they give a total number of shorturls that their service provides. If so, note that in the entry.
  • There are browser plugins/extensions available to make the requests described above from your browser for those without access to curl/command line. (Examples: Advanced REST Client, REST Console)


Was:

Researching URL Shorteners

Here's what to do when you've come across a new URL shortener that should be archived. At minimum, please follow the first step. Anything beyond that is more helpful.

  • Add it to the Alive section of this page in alphabetical order and the current date (hint: 5 tildes (~~~~~) will do that automatically). Please include whatever information you have, but at the absolute minimum, we need the domain.
  • Check the homepage. Is there a public method to create a shorturl? If so, create one and include it in the wiki. If not, note that in the wiki.
  • If you were able to create a shorturl, try making a second. Is it sequential? For example, if the first link was foo.bar/dbE4g and the second link is foo.bar/dbE4h (or very close to it), it's probably sequential. If you get foo.bar/dbE4g followed by foo.bar/g4rTh, it's probably random. Note on the wiki whether the shorturls are random or sequential.
  • Run curl -I http://url.short/validshortcode and see which HTTP status code is returned. Also note whether it returns the destination in the Location: header. Note both on the wiki.
  • Run curl -I http://url.short/invalidshortcode and see which HTTP status code is returned. Note that on the wiki.
  • Check the homepage, and see if they give a total number of shorturls that their service provides. If so, note that on the wiki.



Official Shorteners

Shortener Last Checked on Notes
ask.fm Ex: http://ask.fm/a/40k05kgp -> http://ask.fm/Q7Niki/answer/42128504404 ; seems non-incremental
Shortener Last Checked on Notes
Retrieved from "https://wiki.archiveteam.org/index.php?title=User_talk:Bwn&oldid=25787"