"DasWauto" (DasWauto)
04/10/2014 at 20:45 • Filed to: Kinja Help
4
12|
"DasWauto" (DasWauto)
04/10/2014 at 20:45 • Filed to: Kinja Help | 4
| 12 |
Kinja inserts a related link for bit.ly links now? This is bullshit. I use dozens and dozens of these for each Best of Oppo post.
Being able to get rid of them is nice, theoretically I could stop using bit.ly and just get rid of all the related links but I don't want to click to get rid of every. single. one. That was the entire point of using bit.ly links, avoiding the related insets.
Fuck. This.
Edit - I seem to have sorted out the formatting on the Best of Oppo I was working on but it is a massive pain in the ass to have to remove those links.
Should I use a different link shortener? I'd rather not have to because bit.ly is the quickest and easiest. Techs, please advise.
NoahthePorscheGuy
> DasWauto
04/10/2014 at 20:48 |
|
try is.gd
Blake Noble
> DasWauto
04/10/2014 at 20:48 |
|
Agreed. I had to rip a few links out of my piece I posted tonight because the related highlights kept shitting on my format. I literally poured over all of the HMTL coding trying to get rid of them (I have PTSD flashbacks if I think about the word "aside" right now), and they kept coming back like herpes.
|
DasWauto
> Blake Noble
04/10/2014 at 20:52 |
|
I usually make a few several edits to each Best of Oppo post as I perfect it, please tell me I'm not going to have to do this for each edit...
|
DasWauto
> NoahthePorscheGuy
04/10/2014 at 20:53 |
|
I'll try it but it sees through the link shortener and inserts related links. This is really not cool.
|
Blake Noble
> DasWauto
04/10/2014 at 20:56 |
|
Pouring over the HMTL coding looking for
|
DasWauto
> Blake Noble
04/10/2014 at 20:59 |
|
I clicked the little x at the top of each related link and luckily they seem to have stayed away, even through an edit. No need to look at the html.
What I'm not sure it's gonna with is the related links it puts with my post on the Oppo main page though. I usually format the post so that Kinja adds the top 2 or 4 (depending on whether I enlarge the image) with the post on said main page. We'll see shorty but I have a feeling it'll put the wrong ones.
Ernie @ Kinja
> DasWauto
04/11/2014 at 13:26 |
|
Hey, yeah we made a change to make the inserting of crossheads easier, however I think we may have forgotten about excluding bit.ly. We'll address next week.
|
DasWauto
> Ernie @ Kinja
04/11/2014 at 14:24 |
|
For the moment should I use a different link shortener then? If so, would you let me know when it's fixed because bit.ly is the quickest and easiest and I'd prefer to get back to it as soon as possible if I should switch for now.
|
Ernie @ Kinja
> DasWauto
04/14/2014 at 14:58 |
|
Actually, we're not going to change it. I trust you see the x in the top right corner of every generated inset? Just click those to remove any unwanted crossheads. It creates a bit more work on the user-end, but it shouldn't be too massive a time sink.
|
DasWauto
> Ernie @ Kinja
04/14/2014 at 15:07 |
|
It's a pain in the ass because of the number of links I deal with. I can can handle it but would obviously rather not. Would another link shortener also be linked through as well of are there any that are immune?
|
Ernie @ Kinja
> DasWauto
04/14/2014 at 15:32 |
|
I'm not completely sure. You could do some trial and error, I'd definitely be interested in knowing your result, however I believe all link shorteners will be read through to the source.
|
Ernie @ Kinja
> Blake Noble
04/15/2014 at 10:44 |
|
There's a little 'x' at the top right of a related inset. Click it to get rid of the inset.