235
236

Moderators: markdown auto-linking for r/subreddit and u/username (self.modnews)

tdohz[A] が 投稿

We will soon be adding support for auto-linking r/subreddit and u/username (which the cool kids are calling slashtags) to our markdown library. We will continue to support /r/subreddit and /u/username as well, so there's no changes necessary, just a heads up that if you're using the one-slash version of r/subreddit or u/username anywhere in your subreddit markdown, it'll be auto-linked within the next week or so.

More technical details about exactly will and won't be auto-linked are provided in this /r/redditdev post.

全 141 件のコメント
並べ替え:
ベスト
トップ新着論争中古い順Q&A

[–]JoyousCacophony 162ポイント163ポイント  (35子コメント)

slashtags

Please, no.

[–]AbideMan 42ポイント43ポイント  (7子コメント)

I liked how they linked a post with 2 upvotes (67%) and no comments as "what the kids are saying"

[–]dane83 9ポイント10ポイント  (0子コメント)

They're streets ahead, obviously.

[–]noobit 6ポイント7ポイント  (0子コメント)

From a year ago.

[–]Hedgehogs4Me 4ポイント5ポイント  (0子コメント)

Everyone knows it's only cool with the kids before it becomes "a thing."

[–]Walter_Bishop_PhD [スコア非表示]  (2子コメント)

Pretty sure it's just a joke, haha. Plus Blekko already claimed "slashtags"

[–]noobit [スコア非表示]  (1子コメント)

Plus Blekko already claimed "slashtags"

Ah, welp, you heard it folks. Pack it up, go home

[–]Walter_Bishop_PhD [スコア非表示]  (0子コメント)

Indeed, I'm sure it'd be confusing to the 3 people who use blekko

[–]ifonefox [スコア非表示]  (0子コメント)

I thought it was pretty computers.

[–]DrewsephA 53ポイント54ポイント  (5子コメント)

admins pls

[–]umbrae[A] [スコア非表示]  (2子コメント)

http://i.imgur.com/lle5FcR.jpg

[–]Katana__ 6ポイント7ポイント  (0子コメント)

That's a paddlin'.

[–]Bardfinn 2ポイント3ポイント  (4子コメント)

That's whack. \s

[–]Jrook 6ポイント7ポイント  (2子コメント)

Cool slashtag at the end

[–]Bardfinn 3ポイント4ポイント  (0子コメント)

Itsa whacktag -> \s
Ifitwazzaslashtag itta be /s

[–]starseeker2 [スコア非表示]  (0子コメント)

"well slashed friend"

(which is incidentally what murderers say to each other after cutting down anyone saying 'slashtag')

[–]JoyousCacophony 1ポイント2ポイント  (0子コメント)

That IS whack!

[–]0011110000110011 1ポイント2ポイント  (0子コメント)

One coolkid one year ago called it that.

[–]jhc1415 [スコア非表示]  (0子コメント)

I actually kinda like it.

[–]Ninja_Fox_ [スコア非表示]  (0子コメント)

r/nope

[–]wacrover [スコア非表示]  (7子コメント)

It's weird how often I seem to run into you these days...

[–]JoyousCacophony [スコア非表示]  (6子コメント)

Or am I running into you more? :)

How you been, man?

[–]SkarsgardAbraxis [スコア非表示]  (3子コメント)

https://www.reddit.com/message/compose/?to=wacrover

[–]wacrover [スコア非表示]  (2子コメント)

Or, you know, just ignore us. Either way.

[–]wacrover [スコア非表示]  (1子コメント)

Good - very busy but that's a good thing.

What're you up to for the summer?

[–]JoyousCacophony [スコア非表示]  (0子コメント)

The usual... Too much work, (probably too much) Reddit & gaming where I can.

Never ends. I need to find a way to retire early and focus on the latter 2.

[–]alien122 -1ポイント0ポイント  (0子コメント)

I'm going to make this happen.

[–]allthefoxes 101ポイント102ポイント  (9子コメント)

On one hand, this is pretty cool

On the other, I feel like you guys just gave in.

On my third hand ( ( ͡° ͜ʖ ͡°) ), if you ever say "slashtags" again, I'll personally fly to San Francisco and draw a Dickbutt on your building

[–]ak_hepcat 16ポイント17ポイント  (4子コメント)

The third hand? That's called "the gripping hand"

[–]ArchangelleDovakin 4ポイント5ポイント  (3子コメント)

Upvotes for moties

[–]Manic0892 [スコア非表示]  (2子コメント)

For those that don't understand, read The Mote in God's Eye. It's a good book!

[–]autowikibot [スコア非表示]  (0子コメント)

The Mote in God's Eye:

The Mote in God's Eye is a science fiction novel by American writers Larry Niven and Jerry Pournelle, first published in 1974. The story is set in the distant future of Pournelle's CoDominium universe, and charts the first contact between humanity and an alien species. The title of the novel is a wordplay on Luke 6:41–42 and Matthew 7:3–5, which names a star as seen from a newly settled planet. The Mote in God's Eye was nominated for the Hugo, Nebula and Locus Awards in 1975. Robert A. Heinlein, who gave the authors extensive advice on the novel, described the story as "possibly the finest science fiction novel I have ever read."

Image i

Interesting: The Gripping Hand | N-Space (short story collection) | Larry Niven

Parent commenter can toggle NSFW or delete. Will also delete on comment score of -1 or less. | FAQs | Mods | Magic Words

[–]funfungiguy [スコア非表示]  (0子コメント)

Oh okay... I'm just gonna go to a bookstore and buy a specific book and read it so that I get the reference of a joke that will be two weeks old, which is basically two and a half months old in reddit time, so that I can upvote it and make some Captain America comment implying that I too got the reference in hopes of getting some three-month old stale-ass karma?

C'mon!!!

[–]trollosophy 12ポイント13ポイント  (2子コメント)

Admins

  1. say "slashtags" again

  2. capture u/allthefoxes outside your building

  3. sell the foxes back to the rest of the world at outrageous markup - you've got a monopoly on them

  4. repeat for infinite monies

Problem?

[–]_beast__ 0ポイント1ポイント  (0子コメント)

I mean shit, that would've been cool like 3 years ago but everyone's used to this by now.

[–]nty 23ポイント24ポイント  (3子コメント)

2 upvotes

cool kids

[–]RedSquaree 10ポイント11ポイント  (0子コメント)

Yeah, was expecting something remotely popular.

[–]largenocream 7ポイント8ポイント  (0子コメント)

It's still pretty underground, you probably haven't heard of it

[–]Ultra-Bad-Poker-Face [スコア非表示]  (0子コメント)

only 2 people on reddit are cool

[–]greenduch 13ポイント14ポイント  (5子コメント)

So if I'm intentionally not linking to a specific subreddit (say, coontown) by only using the one slash, that will no longer work? If I use a backslash before it, will it cancel the autolinking?

ninjaedit:

r\/subreddit will work to intentionally not link, apparently. okiedokie.

[–]CosmicKeys [スコア非表示]  (2子コメント)

Yeah, no more passive aggressive username mentions.

"Whoops I forgot the front slashmawhatzit! Soz totally didn't do that on purpose when I was stabbing ya in the back over here!"

[–]nty [スコア非表示]  (1子コメント)

Well you can always just forgo the /u/ entirely, CosmicKeys.

[–]CosmicKeys [スコア非表示]  (0子コメント)

It's true, the half like was useful sometimes though when you wanted to make it explicit you were talking about something on reddit. The tough life of a reddit dev, have other nerds pick apart every change you make :P

Now, back to talking about /u/nty in the other thread.

[–]vikinick 0ポイント1ポイント  (1子コメント)

So, wait, let me test something:

/r/modnews

Edit: I wonder . . . will it be:

\r/Subreddit

or

r\/Subreddit

that will properly escape from linking?

[–]greenduch [スコア非表示]  (0子コメント)

its discussed more here:

Some examples of things that will be autolinked:

  • r/subreddit
  • a r/subreddit
  • foo;r/subreddit
  • \r/subreddit
  • **bold**r/subreddit

Some examples of things that will not be autolinked:

  • foor/subreddit
  • ☃r/subreddit
  • r\/subreddit

A more exhaustive set of examples can be found here.

[–]Kiloku 33ポイント34ポイント  (10子コメント)

This is great for usability and all, but the smug in me can't cringe at the reddit noobs about it anymore :(

[–]atomic1fire 20ポイント21ポイント  (4子コメント)

The reddit hipster in me is bitterly disappointed.

I mean I'll still double slash either way, but single slash just feels wrong.

[–]1point618 3ポイント4ポイント  (2子コメント)

reddit noobs

Some of us were using the single slash long before the linking ability with a double slash was added, and only caved in after years of seeing all these "reddit noobs" using the wrong formatting just because it added a nice little link for them.

[–]Kiloku [スコア非表示]  (1子コメント)

That's an awesome history lesson, actually! Thanks :)

[–]1point618 [スコア非表示]  (0子コメント)

I don't know if it's "reddit history" so much as "1point618's history of being a perpetual curmudgeon", but you're welcome :)

[–]twixtogo 1ポイント2ポイント  (0子コメント)

it's okay

[–]Malcolm_Y 1ポイント2ポイント  (0子コメント)

We surely can find something else to cringe at them about.

[–]allthefoxes 10ポイント11ポイント  (2子コメント)

Does a u/user still get a notification?

[–]tdohz[S] 10ポイント11ポイント  (1子コメント)

Yes, they will get a notification (it'll work basically exactly the same way that /u/username does today).

[–]timotab [スコア非表示]  (0子コメント)

Ugh. Sometimes people use u/user to make it clear they are referring to a reddit user but without notifying them.

[–]Buckwheat469 20ポイント21ポイント  (16子コメント)

Not sure if I like to this change. You've made reconciliations for people who are too lazy to follow a standard. For what reason? What concerns me is how we will escape the auto linking now. It used to be that you would put a single backslash at the beginning, but now that would be like escaping the u or r. The end result my be the same, but with the forward slash in front it made sense where to add the escape character.

[–]ChurchHatesTucker 7ポイント8ポイント  (1子コメント)

You've made reconciliations for people who are too lazy to follow a standard

Eh, this should have been the standard from the beginning. That's what most of us were using.

[–]1point618 [スコア非表示]  (0子コメント)

Indeed.

It's weird that I've been on this site to see this issue come around full circle.

[–]Bardfinn 2ポイント3ポイント  (2子コメント)

\/r\/subreddit

[–]xereeto 3ポイント4ポイント  (1子コメント)

Or just /r\/subreddit

[–]noobit [スコア非表示]  (0子コメント)

Or \/r/subreddit, included for completeness

[–]mattman00000 1ポイント2ポイント  (10子コメント)

What concerns me is how we will escape the auto linking now

Why would you want to?

[–]Buckwheat469 13ポイント14ポイント  (9子コメント)

Sometimes /u/something doesn't mean go to the something user's account, it might just be part of a conversation so it shouldn't be a link, it should show as /u/something instead. You always need a way to escape the algorithms, because sometimes they do things that you might not want.

[–]dakta 5ポイント6ポイント  (0子コメント)

/u/greenduch has the solution: just escape the middle slash.

[–]atomic1fire 0ポイント1ポイント  (7子コメント)

Like this? /u/something

Bro do you even markdown?

use \ to escape markdown formating, like so

\/u/something

\*hi*

*hi* rather then hi

\ will escape any markdown formating, including links and bold and italics.

Just add an extra \ if you want to keep that from being used to escape a markdown.

\\*hi*

\hi

In the future \u/something should work to escape u/something

[–]Buckwheat469 5ポイント6ポイント  (5子コメント)

You must not have noticed my comment.

[–]atomic1fire -5ポイント-4ポイント  (4子コメント)

Your comment was "reddit needs a way to escape the algorithm."

Reddit has two ways, the way I mentioned and if you set up the link/code/whatever in a code block

Just add 4 spaces before it and reddit won't format it at all.

With RES you can see the comment be rendered in realtime, sometimes it's a pain but you can usually manage around the minor issues.

edit: Oh I see what you mean, you already knew about the markdown escape but are now confused about where to put the backslash.

I'd still put it in front of the R as a force of habit.

[–]dakta 5ポイント6ポイント  (0子コメント)

No, you clearly missed what he was saying. He explicitly acknowledged the use of leading backslash to escape username and subreddit auto-linking, and was wondering how to achieve that effect with the new format where the leading character is no longer a slash. He doesn't want to have to separate the unformated part into a completely new block level element, he wants it inline. Your reply isn't helpful because the user you're replying to already knows all of the things you said in your reply.

The solution would seem to be to just escape the middle slash.

[–]Buckwheat469 2ポイント3ポイント  (1子コメント)

My original comment was "we don't need this because we have a standard and people should follow it."

The secondary comment to that was that the change would require a change to the escape sequence documented and described by helpful people (adding more detail to what I said). It's an unnecessary change.

I was not confused as to how you escape strings in reddits markdown, hell I use it everyday.

[–]atomic1fire 1ポイント2ポイント  (0子コメント)

Yeah I get that now.

I feel like they saw that everyone was using r/blahblah and support it going forward. Even though they were using it to break the autolink most of the time.

I agree that it's kinda a dumb change.

[–]andytuba [スコア非表示]  (0子コメント)

Incidentally, RES live preview uses its own port of snudown, so changes like this won't be reflected in RES until its implementation is updated and shipped.

[–]Werner__Herzog 1ポイント2ポイント  (0子コメント)

He wanted to know if the escape character will still work once it's put in front of a letter. And apparently it will. I guess if it wouldn't there'd still be the option to write it as code, since something like /u/someone is used as some example anyway and should be distinguished somehow.

[–]vikinick 9ポイント10ポイント  (0子コメント)

this r/redditdev post

FTFY admin.

[–]ChingShih 3ポイント4ポイント  (8子コメント)

It'd be cool if you could make something like "np/r/subreddit" auto-link to the np.reddit.com/r/subreddit version of the domain.

Might improve the use of np links. Although something like "np.subreddit" would be more visually appealing.

[–]greenduch 3ポイント4ポイント  (0子コメント)

np links are a plague anyway, not sure why they would want to encourage that :p

[–]Pokechu22 0ポイント1ポイント  (6子コメント)

You can always do http://np.videos.reddit.com. (http://videos.reddit.com redirects to /r/videos). Unfortunately this does require including the http://.

[–]ChingShih 0ポイント1ポイント  (1子コメント)

Right, but that doesn't auto-link like /r/videos does.

I figure if the admins want to promote the np link feature, this might be a good way to do it while they're tinkering with other stuff.

[–]andytuba [スコア非表示]  (0子コメント)

The only place I've seen admins using np is linking from the upvoted newsletter.

[–]allthefoxes 1ポイント2ポイント  (3子コメント)

http://np.videos.reddit.com

Dont do this. double subdomains make me sad

[–]Pokechu22 0ポイント1ポイント  (1子コメント)

http://how.about.three.reddit.com?

Being serious, though, yea, they are kinda ugly.

[–]spladug [スコア非表示]  (0子コメント)

Double subdomains also don't work for reddit.com on HTTPS because we only have a single wildcard *.reddit.com certificate.

[–]startacker [スコア非表示]  (0子コメント)

Please don't call them slashtags

I beg you

please

please

please

please

[–]amoliski 5ポイント6ポイント  (13子コメント)

While we're messing with markdown, can you please consider making return do this ->
<-
instead of this-> <-

The double return <p> break or double-space-return <br> only causes confusion for new users and doesn't really make sense.

Maybe just a warning in the editor when someone does a single return?

[–]Deimorz 7ポイント8ポイント  (11子コメント)

But then how would I be able to... ...hmm, actually I can't even think of a single case where I'd want the current behavior.

I just went to look at the markdown syntax page to see why this decision was made in the first place, and it looks like it was to handle "hard-wrapped" paragraphs so that you could do things like this:

> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.

> Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
id sem consectetuer libero luctus adipiscing.

Seems like a strange decision, maybe it made more sense over 10 years ago if you had to deal with a lot of hard-wrapped text from emails or something.

[–]xereeto 3ポイント4ポイント  (4子コメント)

One more question RE markdown: is it possible to get numbering to work properly? At the moment no matter what number you put before the dot, it will autonumber:

420. 

69. 

9001.

gives

Is there any way to get it to display the actual number you typed?

[–]Deimorz 4ポイント5ポイント  (2子コメント)

Yep, that's a fun one too. It's great when people try to write things like "14. He was only 14 years old when he did this." and it comes out as:

  1. He was only 14 years old when he did this.

The "right" way to do it is to escape the period, so you type 14\. He was only 14 years old when he did this. It's another thing you shouldn't really have to do though, no idea why that decision was made either.

[–]amoliski [スコア非表示]  (0子コメント)

Escaping things in general is pretty confusing sometimes. Ex. How would you make **Bold** be bold, asterisks included?

**\*\*Bold\*\*** == **Bold*\*

**\*\*Bold*\*** == **Bold*\*

To be fair, that's a pretty severe edge case, but there's tons of cases where people go This when they mean ^^This (Though "^^This" deserves a downvote anyway.)

Or :) when they want :^) or -^ when they want ^-^

9 times out of 10, people mess up ¯\_(ツ)_/¯ They either don't escape the first arm and the underscore: ¯_(ツ)_/¯

or they escape the arm but not the underscore ¯\(ツ)/¯

[–]xereeto [スコア非表示]  (0子コメント)

...

I feel like a tit. I've been trying and failing to escape the number the whole time, and resorting to either rewriting the sentence or using unicode fuckery to get something to display.

[–]OcelotWolf 2ポイント3ポイント  (0子コメント)

Seriously. One time someone asked me how many dicks I've sucked. I said "345." and it appeared as "1." Made me look like a pussy.

[–]noobit [スコア非表示]  (4子コメント)

Oh! Oh! Markdown discussion!

If you guys do end up doing an overhaul, there's a couple of bugs with markdown, leading to things you literally can't render in markdown as it currently exists.*

The oldest one I remember is

  1. You can't have a superscripted character higher than one level be immediately followed by a nonsuperscripted character. If it's just superscripted once, you can use the trick - e.g. aa - but if it's higher than one level no longer works, making this impossible to display.

I found a couple more a while ago when I found out codeblocks were way more flexible than I thought. (This was the first time I considered making a list, but didn't as the bugs I've found were still countable on one hand.)

  1. You can't have a superscripted codeblock higher than one level contain a space.
    Again, this is still achievable one level up thanks to the parenthesis syntax, but anything beyond one level cannot be represented. This and the above bug can both be fixed by allowing the paren syntax to go more than one level up (which IIRC is daringfireball's suggested implementation anyways? edit nah, can't find it)

  2. You can't strike out an inline codeblock if there is another codeblock after it in the same paragraph.
    (...Don't ask. I spend way too much time playing with this stuff)
    So for instance, this is completely kosher, but

    ~~doing~~ this breaks.

While making this list I remembered another one, heh.

  1. You can't start a properly-formatted numbered list at any value other than one.
    This would be useful for lists such as this one, where outside-of-the-list contextualizing comments are interspersed with the list itself. Sure, you can forego having a proper markdown list and just escape the numbers, but the proper indentation really adds to readability.

Again, it's not so much that these bugs need be fixed - they're corner cases no one's likely to come across (In ~10 years, I seriously doubt anyone's flipped a table over not being able to superscript codeblocks with spaces in them higher than one level. Besides me. :P) but they might help you hunt down whatever implementation bugs caused them to exist in the first place.

(Of course, there are also much more obvious things, like the 'enter' behavior, which people do care about :P)

[–]zimmund [スコア非表示]  (1子コメント)

I think you address some interesting cases there, but I'd stick with the double enter. It's part of markdown, and I use markdown in other places too. And I like it.

[–]TheCid [スコア非表示]  (1子コメント)

Seriously, fuckthe^(multiple superscript ignoring parentheses bullshit).

Seriously, ^fuck^the^(multiple superscript ignoring parentheses bullshit).

I would expect the entire parenthetical to be in the third superscript layer without parentheses, based on how this works:

Single sentence in parentheses

Single ^(sentence in parentheses)

[–]amoliski 1ポイント2ポイント  (0子コメント)

I was thinking it was a throwback to the days of 80 character wide terminals where returns had to be avoided for cleanliness? 

 When wrapping doesn't happen, too much text in a single line makes it really hard to read/edit, especially in terminal windows

Doesn't really make sense on reddit where the editor window and the resulting display automatically wraps the text.

I think changing return into a <p> or a <br> without having to double it up would make a lot more sense, and it shouldn't have too many backwards compatibility issues, because everyone double returns anyway, and the people who didn't in the past certainly meant to, so it would be retroactively fixing those posts.

The biggest benefit would come when you are copying text from elsewhere- currently you need to go through and add another return at every paragraph, otherwise it'll get jumbled together.

(Though, fixing other people's formatting does earn some decent karma...)

[–]ChezMere 1ポイント2ポイント  (0子コメント)

Seriously. This is such a massive boon for usability that it's worth breaking whatever you have to.

[–]TankorSmash 3ポイント4ポイント  (2子コメント)

My gut reaction is to not want the slash to be optional, but after a second you realize how stupid that is.

I'll just wait for r/youtubetitties to go blue.

[–]huehuelewis 2ポイント3ポイント  (1子コメント)

The karma economy will be deflated a bit now that people can't earn karma by explaining to people that a leading slash is required on things like r/spacedicks

[–]OcelotWolf 1ポイント2ポイント  (0子コメント)

But you don't want a link to that subreddit!

[–]mr_abomination 1ポイント2ポイント  (0子コメント)

I am unsure how to feel about this...

[–]TheCodexx 2ポイント3ポイント  (1子コメント)

I have some concerns about this:

Several subreddits ban direct links to subreddits. This is for their own safety, and the safety of their users, because links to other subreddits can be labeled "brigading". Rather than risk being shut down over something innocuous, they will use automoderator to clean up all links to other subreddits. PCMR is a great example of a popular subreddit that got banned because someone once linked another subreddit.

To get around these bans, users can use the single slash form to not link. This is really handy. It's also useful if you want to attach a username without notifying the user that they were mentioned.

Now, this doesn't leave any way to distinguish that something is a subreddit and not link to it. In fact, this is downright inconvenient. This is poorly thought out. Now I have to carefully parse old comments to avoid triggering the bot by accident, and old posts might get flagged by bots.

[–]andytuba [スコア非表示]  (0子コメント)

https://www.reddit.com/r/modnews/comments/37nrf4/moderators_markdown_autolinking_for_rsubreddit/croawr7

Now subs need to update AutoMod to detect r/subreddit links too, and users can learn to use the new format.

[–]crash__bandicoot 0ポイント1ポイント  (3子コメント)

I actually kind of like the term slashtag :(

[–]PabstyLoudmouth 0ポイント1ポイント  (0子コメント)

I never did that in the first place. So, cool with me.

[–]alien122 1ポイント2ポイント  (0子コメント)

We will soon be adding support for auto-linking r/subreddit and u/username (which the cool kids are calling slashtags)

If you guys bring back boosts, for even a month, I'll make sure this dank meme becomes popular.

[–]DarthFarious 0ポイント1ポイント  (0子コメント)

Why not radslashes?

Because they are slashes and rad as fuck.

[–]pencer 0ポイント1ポイント  (2子コメント)

I get that it'll be updated in subreddit markdowns, but will this be retroactive for all comments once it's implemented?

[–]Deimorz 2ポイント3ポイント  (1子コメント)

There might be some oddities with already-rendered versions of some old comments being cached, so they may not all update immediately, but it should be retroactive in theory, yes.

[–]pencer 0ポイント1ポイント  (0子コメント)

I like this in theory. The likelihood of an inbox fart is low then

[–]OmicronNine 0ポイント1ポイント  (0子コメント)

Currently, we can reference subreddits and users in our comments without the auto-linking simply by omitting the first slash. This is convenient for some very good reasons. (Consider r/spacedicks for example. Aren't you glad that's not a link?)

How will we accomplish this after these changes? What if auto-linking is not desired?

[–]Manadox 0ポイント1ポイント  (1子コメント)

Please never say slash tag again.

[–]TownIdiot25 [スコア非表示]  (0子コメント)

oh good another thing to add to automod to remove

[–]Widdershiny [スコア非表示]  (0子コメント)

/u/chocolatemilk67

[–]BlankVerse [スコア非表示]  (0子コメント)

I DO NOT LIKE THIS CHANGE!

Typing r/foobar is a easy way to reference a subreddit without linking to it. For example, I might want to mention r/coontown, but not link to it.

[–]theecakee [スコア非表示]  (0子コメント)

r/SlashTaggin

[–]DubTeeDub [スコア非表示]  (0子コメント)

Okay I guess

[–]captainmeta4 1ポイント2ポイント  (0子コメント)

What about /d/domain.com ?

[–]105Hummel [スコア非表示]  (1子コメント)

After ten years in development, hopefully slashtags are worth the weight.

[–]Jakeable [スコア非表示]  (0子コメント)

They're worth their weight in reddit Gold

[–]tdogredman -1ポイント0ポイント  (0子コメント)

Totally gnarly, reddit admin!

slashtag funny

am I doing this right? Am I a cool kid yet?

[–]TotesMessenger [スコア非表示]  (1子コメント)

I'm a bot, bleep, bloop. Someone has linked to this thread from another place on reddit:

If you follow any of the above links, please respect the rules of reddit and don't vote in the other threads. (Info / Contact)