Sexy Trust levels are a-changing!
-
-
You might have, I certainly haven't
-
Arantor told me that Luhmann has a disappointingly tiny
Hmmm. I do wonder how @Arantor came to that conclusion. He wasn't complaining last night.
wut the...
Clearly they're talking about the "leader" title.
Luhmann has a disappointingly tiny leader (the blank bit of tape that appears at the start of a cassette)
Filed under: obviously
-
Clearly they're talking about the "leader" title.
Luhmann has a disappointingly tiny leader (the blank bit of tape that appears at the start of a cassette)
Filed under: Well played, sir!
For great justice!
-
Move zig, move zig!
-
I've heard this, but it's never worked for me. I buttumed that I had remembered it wrong.
It works on asterisks, but not on > or <. You gotta type those as entities, just like good ol' Community Server.
-
I hear this change was done so blakey could get both leader and veteran badges while the rest of us can only have leader for another 100 days.
-
I wouldn't be at all surprised actually.
-
It works on asterisks, but not on > or <. You gotta type those as entities, just like good ol' Community Server.
That makes sense, < and > are the only things I ever tried it on.
-
That's just it, it doesn't actually make sense to do that
-
-
It works on asterisks
unless it doesn't:
@Kuro said:\*Test\* → Test*
*Test\** → Test
WAT? Markdown doesn't make sense to me again
-
I'm past caring about what does and doesn't work in Markdown. I use HTML if I need to do something
fancypretty standard.
-
That is fine unless you want to put * or _ somewhere in your message.then you gotta remember how this whole escape-thing worked. also &lt; to write < if you want to show people how to make < escaped. Because thats when \ doesn't escape the &
Unless there is an easy way that doesn't involve putting [code]-blocks around everything you say that I didn't discover, yet.
Filed Under: Yay, Markdown!
-
-
unless it doesn't:
Oh right I actually came across that once when I ended up with weird italics I couldn't figure out where they came from.
-
I'm past caring about what does and doesn't work in Markdown. I use HTML if I need to do something fancy pretty standard.
Yeah, so this forum is a big improvement over Community Server where you had to... use... HTML... to...
Well, shit.
-
It's a battle of man vs. (RE-matching state) machine!
I've been using MD for years so it's not too much of a problem. Most of the time. But DC's handling of unbalanced tags bothers me a lot…
-
Yeah, so this forum is a big improvement over Community Server where you had to... use... HTML... to...
Where if you used Chrome, you had to do it entirely by writing HTML. Including <p> tags. Because CS was ancient and didn't realize that Chrome actually existed and knew what Javascript was…
-
Where if you used Chrome, you had to do it entirely by writing HTML. Including <p> tags. Because CS was ancient and didn't realize that Chrome actually existed and knew what Javascript was…
Stop trying to be a pedantic dickweed on purpose. Jesus it's fucking irritating as shit.
-
Stop trying to be a pedantic dickweed on purpose.
Sorry, but my personality is pedantic dickweed. Can't help it.
-
I find shit to be most irritating when it's inside my bowels. The best way to get shit to stop irritating you is to just get it out. Do you feel better now @dkf?
-
I think I'll save talking about that for the Status thread.
-
Except in cs, you could wrap your whole post in paragraph tags, and it spit out basically what you put in with no further fuss, discourse on the other hand. ..
-
Can the admins actually configure it in the first place?
There is no web interface for changing them. They're hard-coded in the config/locales/server.*.yml (i.e. the I18N files.)
[pjh@sofa discourse]$ grep -r veteran . ./config/locales/client.it.yml: elder: 'Utenti veterani (livello d''accredito 4)' ./config/locales/server.en.yml: If you can see this topic, you were recently promoted to [trust level 3 (veteran)][trust]. ./config/locales/server.en.yml: Here's the [current list of users who made it to trust level 3](/badges/3/veteran). Be sure to say hi! ./config/locales/server.en.yml: title: "veteran" ./config/locales/server.en.yml: leader_requires_days_visited: "Minimum number of days that a user needs to have visited the site in the last 100 days to qualify for promotion to veteran (3) trust level. (0 to 100)" ./config/locales/server.en.yml: leader_requires_topics_replied_to: "Minimum number of topics a user needs to have replied to in the last 100 days to qualify for promotion to veteran (3) trust level. (0 or higher)" ./config/locales/server.en.yml: leader_requires_topics_viewed: "The percentage of topics created in the last 100 days that a user needs to have viewed to qualify for promotion to veteran (3) trust level. (0 to 100)" ./config/locales/server.en.yml: leader_requires_posts_read: "The percentage of posts created in the last 100 days that a user needs to have viewed to qualify for promotion to veteran (3) trust level. (0 to 100)" ./config/locales/server.en.yml: leader_requires_topics_viewed_all_time: "The minimum total number of topics a user must have viewed to qualify for veteran (3) trust level." ./config/locales/server.en.yml: leader_requires_posts_read_all_time: "The minimum total number of posts a user must have read to qualify for veteran (3) trust level." ./config/locales/server.en.yml: leader_requires_max_flagged: "User must not have had more than x posts flagged by x different users in the last 100 days to qualify for promotion to veteran (3) trust level, where x is this setting's value. (0 or higher)" ./config/locales/server.en.yml: leader_promotion_min_duration: "The minimum number of days that a promotion to veteran lasts before a user can be demoted." ./config/locales/server.en.yml: leader_requires_likes_given: "The minimum number of likes that must be given in the last 100 days to qualify for promotion to veteran (3) trust level." ./config/locales/server.en.yml: leader_requires_likes_received: "The minimum number of likes that must be received in the last 100 days to qualify for promotion to veteran (3) trust level." ./config/locales/server.en.yml: leader_links_no_follow: "Do not remove rel=nofollow from veteran links."
Except in cs, you could wrap your whole post in paragraph tags, and it spit out basically what you put in with no further fuss, discourse on the other hand. ..
Backticks seem to do much the same, no?
-
There is no web interface for changing them.
So I was correct in saying that the names are "being held to the whims of the developers" instead of letting the community decide what they want to call them.
And considering they're anguishing over heatmaps/coldmaps and the TL names instead of, you know, making the search work better and making the site more efficient... they don't seem to have any priorities that make sense.
-
they don't seem to have any priorities that make sense.
It's really hard to tell. I don't have a problem with them discussing stuff with their users. Most of the topics on meta.d are not started by discodevs (I think). But what is an actual priority? There's an occasional mention of how important something is to one of them, but unless it's Jeff directing someone to do something now, that's as systemically ineffectual as a compliment from blakeyrat.
There's no way to look at their official issue tracker and tell work priorities from shooting the bull.
-
That'd be why it'd be nice if they used a real issue/bug tracker that they could specify priorities or severity and/or had milestones laid out. Right now, it just seems to be "fix whatever significant bugs pop up, then do what you want, unless Atwood tells you to do something".
And yes, someone else (the new search didn't help me find that out, it was @Yamikuronue) pointed out that GitHub provides both a bug tracker and a milestones page, and they're intentionally not using them.
-
GitHub provides both a bug tracker and a milestones page
With great bug tracker comes great accountability.
-
-
-
Figured. My memory is shit
sometimesmost of the time.
-
And for reference, here's what I get:
Searching for "milestone" filtering to just your posts:
One result, your post.Searching for "milestone" from the latest list:
Only 4 results, not including the one above.Notice the
inconDiscoursistency. Also, searching for "milestones" (since that's what you said in that post) has no difference in results.
-
Backticks don't, I had a topic somewhere suggesting we use them, then proceeded to play markdown golf inside of the backticks so chucked that idea.
-
With great bug tracker comes great accountability.
Yeah, but github's bug tracker is only mediocre.
[spoiler]Still, it's fundamentally better than using a web forum.[/spoiler]
-
Yeah, but github's bug tracker is only mediocre.
It's one of the better "free" solutions that I've found, and way better than using Discourse. Given that they're already using GitHub for hosting, they could even use the extra features which automatically update the relevant issues straight from the commits.
It would make sense to allow people to report and discuss bugs in meta.d, but as soon as it's an agreed bug, it should be moved into the proper bug tracker, with a link from the forum topic to the bug.
-
But...but...DOGFOOD
I hear they're looking to get away from github (and git) altogether and just start jamming it all into a separate discoinstance.
-
Relevant:
-
-
-
-
That just reminded me of another photoshop of @codinghorror's avatar.
If only I remember where that one was ...
Filed under: What is wrong with me
-
-
That just reminded me of another photoshop of @codinghorror's avatar.
If only I remember where that one was ...
Filed under: What is wrong with me
Was it the one attaching the hair to Clippy? Because that one's allowed.
-
OK, but this search is still broken:
And the search is still constrained to only one post per topic the search term is found in.
-
No, it's the one where they made his avatar look eager to put something that isn't dogfood in his mouth.
-
And we're back to searching in the current topic not being the default, so the browser's Ctrl+F behavior is really broken. Again/Still (take your pick).
-
searching in the current topic not being the default
Also not searching only the user when starting search from a profile.
-
And we're back to searching in the current topic not being the default,
It's the default for me when I'm in a topic already. Some new stuff coming soon:
https://meta.discourse.org/t/double-stuf-improved-search-feedback/19490/10?u=boomzilla
-
It's the default for me when I'm in a topic already
It didn't for me earlier, when I was testing the search @abarker reported originally, but it does now.
Profile search doesn't start with "this user only" on by default. And Ctrl + F doesn't bring up search from the profile.