| 00:28:00 | <@JAA> | We have a new victi ... I mean volunteer for entering new shorteners into the tracker. May they reveal themselves if they want to be known. :-) |
| 00:58:26 | <flashfire42> | We are thankful for their sacrifice and I will go and find 30 link shorteners to add to the wiki to celebrate |
| 01:12:49 | <@JAA> | Disabled digbig-com as it is looping on redirects. We've been collecting bad data for it for a while, but I don't know for how long. |
| 01:12:49 | <aarchi> | I recently added several shorteners to the wiki, but it looks like they’re still pending mod approval. Can I be allowlisted? |
| 02:06:29 | <@hook54321> | Added cokeurl.com to the tracker and enabled it. It seems to be running ok so far. |
| 03:41:09 | | qw3rty__ joins |
| 03:41:53 | <@hook54321> | Added a.ll.st |
| 03:45:02 | | qw3rty_ quits [Ping timeout: 258 seconds] |
| 04:42:20 | <aarchi> | I just setup the terroroftinytown Docker warrior on my personal machine. What level of concurrency would you recommend for everyday use? |
| 04:42:48 | <aarchi> | i.e. the `--concurrent X` flag |
| 04:47:04 | <aarchi> | Also, is there a way to see more detailed stats for my user on the tracker or locally? |
| 05:27:32 | <aarchi> | On 18 Mar, @tech234a mentioned that Google Go Links, one of Google's URL shorteners shut down on 31 Mar. I didn't see any discussion about it here. Were those archived? https://github.com/codyogden/killedbygoogle/issues/865 |
| 06:36:15 | | Ryz quits [Remote host closed the connection] |
| 06:40:07 | | Ryz (Ryz) joins |
| 11:25:14 | | HackMii quits [Remote host closed the connection] |
| 11:25:35 | | HackMii (hacktheplanet) joins |
| 12:32:16 | | AK quits [Quit: AK] |
| 12:33:09 | | AK (AK) joins |
| 13:32:34 | <@JAA> | aarchi: Go as high as you want, basically (up to seesaw's limit). You're anyway limited to one item per shortener and IP at a time by the tracker. |
| 13:38:04 | <@JAA> | aarchi: Google Go Links probably can't be done. Custom codes on custom domains... |
| 13:46:38 | | OrIdow6 quits [Quit: Quitting.] |
| 13:48:00 | | OrIdow6 (OrIdow6) joins |
| 13:48:54 | | AK quits [Client Quit] |
| 13:51:42 | | AK (AK) joins |
| 13:53:10 | | OrIdow6 quits [Remote host closed the connection] |
| 13:54:41 | | OrIdow6 (OrIdow6) joins |
| 13:58:43 | | OrIdow6 quits [Remote host closed the connection] |
| 13:59:26 | | OrIdow6 (OrIdow6) joins |
| 14:03:19 | | OrIdow6 quits [Remote host closed the connection] |
| 14:03:50 | | OrIdow6 (OrIdow6) joins |
| 14:07:33 | | OrIdow6 quits [Remote host closed the connection] |
| 14:08:17 | | OrIdow6 (OrIdow6) joins |
| 14:57:37 | | Daloader joins |
| 15:41:27 | | OrIdow6 quits [Changing host] |
| 15:41:27 | | OrIdow6 (OrIdow6) joins |
| 16:30:16 | | @Fusl quits [Excess Flood] |
| 16:30:36 | | Fusl (Fusl) joins |
| 16:30:36 | | @ChanServ sets mode: +o Fusl |
| 16:36:09 | | @ChanServ sets mode: +o OrIdow6 |
| 16:56:29 | | @ChanServ quits [shutting down] |
| 16:56:31 | | ChanServ joins |
| 16:56:31 | | ing.hackint.org sets mode: +o ChanServ |
| 17:04:24 | <@hook54321> | asking the person running deb.li if they'll give us the URL mappings |
| 17:20:33 | | Daloader_ joins |
| 17:23:40 | | Daloader quits [Ping timeout: 250 seconds] |
| 19:39:54 | <@hook54321> | red-ht added and running |
| 19:57:30 | | Daloader_ quits [Ping timeout: 250 seconds] |
| 22:04:01 | <aarchi> | So I was testing red-ht manually in my browse and I think I got banned. It displays a Bitly 403 on any shortcode now. |
| 22:04:13 | <aarchi> | s/browse/browser/ |
| 22:18:27 | <@JAA> | Oh yeah hook54321, don't start bit.ly aliases. |
| 22:19:21 | <@JAA> | 1) The codes usually work both on the alias and on bit.ly (with exceptions only on custom codes IIRC), and we're already scanning the latter. 2) Bans. |
| 22:20:40 | <@JAA> | If a shortener domain resolves to 67.199.248.10 to 67.199.248.13, that's bit.ly. (Do a reverse lookup if you're unsure.) |
| 22:21:16 | <@JAA> | red-ht stopped. |
| 22:21:34 | <aarchi> | Is there an easier way to detect whether a shortener is a bitly alias than by getting banned? |
| 22:22:52 | <@JAA> | DNS lookups |
| 23:03:43 | <@hook54321> | JAA: my bad, thanks. |
| 23:09:52 | <aarchi> | I wrote a test that checks all the known bit-ly aliases listed on the wiki. Some don't resolve to a bit-ly IP. |
| 23:09:54 | <aarchi> | https://github.com/andrewarchi/urlhero/blob/main/shorteners/bit-ly/bitly_test.go |
| 23:22:45 | <@JAA> | Yeah, some probably moved away from bit.ly and others switched to it. |
| 23:27:36 | | nepeat quits [Quit: ZNC 1.8.2 - https://znc.in] |
| 23:27:44 | | nepeat joins |
| 23:41:06 | <aarchi> | I just surveyed the alleged bit-ly aliases that aren't within 67.199.248.10 to 67.199.248.13. |
| 23:41:16 | <aarchi> | bitly.com, www.bitly.com, and bitlymail.com: 67.199.248.14 67.199.248.15 |
| 23:41:22 | <aarchi> | j.mp: 67.199.248.16 67.199.248.17 |
| 23:42:38 | <aarchi> | These four share the same 67.199.248.00/24 block |
| 23:43:51 | <aarchi> | Do these three bitly-named ones handle shortcodes? |
| 23:47:06 | <@JAA> | I believe I've only seen .10 to .13 on aliases. |
| 23:55:11 | <aarchi> | j.mp redirects to bitly.com. Maybe .16 and .17 are bitly then |
| 23:58:59 | <@JAA> | All of those are Bitly, yes. I thought this was only about aliases. |