Managing a wiki is
-
Developer
Making sure I document that weird thing I found out about.
Manager
Making sure we track who did what because of the boogeyman will mess it up...
User
Making sure the goddamn fucking thing is fucking wikified so I can use my fucking intuition and find information I need to know.
-
wiki wiki SLIM SHADY!
-
I'd ask what this topic is about, but I know there's no satisfactory answer. Let's talk about gum. Sorbitol or Xylitol??? I'm a Xylitol man, myself.
-
Walked in the strip club, had my jacket zipped up
Making sure we track who did what because they'll mess it up
-
this topic is about
why dev wikis get bogged down in conditions that satisfy management but distract from the purpose of a wiki, and why people that write in a wiki seem to think it's a place to put verbose text documents... with no cross linking.
My company seems to think that hierarchical structures for documentation is somehow superior to searchable wiki.
-
Making sure we track who did what because of the boogeyman will mess it up...
No, that's what source control and an issue tracker are for.
-
I meant adding additional measures on top of default wiki edit tracking, like manual supervisor approval, etc.
-
@xaade said:
Making sure we track who did what because of the boogeyman will mess it up...
No, that's what source control and an issue tracker are for.Wikis do version tracking. Can't we just paste the source code into that, and it'll track magically? Just create a new wiki page for each code file. Easy.
-
Should I wikify the OP?
-
@Lorne_Kates said:
Wikis do version tracking. Can't we just paste the source code into that, and it'll track magically? Just create a new wiki page for each code file. Easy.
GitHub wikis can be cloned as git repositories and pushed too. Too bad that GitHub wikis also support having characters in article names that no filesystem supports...
-
-
Let's talk about gum. Sorbitol or Xylitol??? I'm a Xylitol man, myself.
You're a punk. Real men chew Bazooka Joe, sugar be damned.
-
Too bad that GitHub wikis also support having characters in article names that no filesystem supports...
sounds like a feature.
-
-
Too bad that GitHub wikis also support having characters in article names that no filesystem supports...
Really, you mean my filesystem doesn't let me have a file named .xlsx? It's totally disambiguous what that's for!
-
GitHub wikis can be cloned as git repositories and pushed too. Too bad that GitHub wikis also support having characters in article names that no filesystem supports...
There are characters linux filesystems don't support? I thought being able to ahve control characters in your filenames was one of its major misfeaturesโฆ
-
apparently it doesn't support ambiguously suggestive grunts and farts as filenames.
-
Walked in the strip club
...like whaddap, I got a big co...oh, sorry, wrong track, move along.
-
There are characters linux filesystems don't support?
-
Really, you mean my filesystem doesn't let me have a file named .xlsx?
Um, actually, GitHub is for pure OPEN SOURCE projects. .xlsx is a CLOSED FORMAT that was forced upon the world to lock up YOUR DATA. Go suck Micro$soft's cock, you Cathedral-loving corporate whore.
-
I know you're kidding, but...
https://www.google.com/search?q=filetype%3Axlsx site%3Agithub.com
-
@Lorne_Kates said:
Wikis do version tracking. Can't we just paste the source code into that, and it'll track magically? Just create a new wiki page for each code file. Easy.
We can do source control using Discourse, obviously. Just create a thread for each file and post revisions as new posts. This has the added advantage that we can use whispers for peer review.
-
-
-
https://www.google.com/search?q=filetype%3Axlsx site%3Agithub.com
Huh. only 283 results. TMYK
-
, Is that why it's called the "Open XML File Format"?
It's called that because they wanted to intercept searches for OpenDocument XML.
-
because
Ah. I thought they just wanted to sound trendy.
-
I know you're kidding, but...
https://www.google.com/search?q=filetype%3Axlsx site%3Agithub.com
Heathens.
-
We can do source control using Discourse, obviously. Just create a thread for each file and post revisions as new posts. This has the added advantage that we can use whispers for peer review.
As it turns out, there's a 30k character limit to each post. So even when you're , Discourse is er.
-
BONUS DISCOUrSE FUCKUPS!
First, the URL of the thread is actually "https://what.thedailywtf.com/t/lornes-stupid-thread-of-war-and-elgiu-because-if-everyone-else-can-abuse-discourse-so-can-i-doing-it-wrong/51954". Note the "elgiu". But when I pasted it above, it baked it into BOX BOX BOX, and thus broke the URL.
As such, it didn't NoneBox.
In the Status thread, I posted a quick-n-dirty War in Javascript game. If you want to find it, be my guest.
I've been tinkering with the code trying to turn it into a playable
game. Mostly for my amusement. Partially because of-- secret raisins.
In any case, I figured I should get the code into some sort of code
tracker system, so I can track revisions. But rather than doing it in
any sane or correct way-- Discourse!
-
FUCKING SERIOUSLY? "e l g i u" is the censored word, not "b e l g i u m"??!?!?!?!??!?!??!
Godfuck you Discourse you pile of cat vomit.
.......... https://what.thedailywtf.com/t/51954 ................
Let's see how Discourse and or fuckbox fucks this up:
-
#AMAZING! IT DOESN'T CENSOR THE ONEBOX! BRILLANT!
-
I want to access your thread, but won't let me...
-
@https://what.thedailywtf.com/site/settings.json said:
"censored_words":"elgiu|belgium|b.....m"
Hey Discourse, why are censored words censored in plaintext, DiscoCensored in two-or-more backticks, but fine in single backticks?
-
Hmmm...
Belgium
B.....m
Botttom
-
Buuuuum
-
Hey, @PJH, can you censor
.*
on your test instance and then post something containing that and show us what happens?
-
Hey Discourse, why are censored words censored in plaintext, DiscoCensored in two-or-more backticks, but fine in single backticks?
I'll take RegEx Fuckery for 300.
-
@Lorne_Kates said:
FUCKING SERIOUSLY? "e l g i u" is the censored word, not "b e l g i u m"??!?!?!?!??!?!??!
YMBNH. Both of them are censored.
-
Hey Discourse, why are censored words censored in plaintext, DiscoCensored in two-or-more backticks, but fine in single backticks?
Why don't you hop on over to meta.derp and ask ?
-
@Lorne_Kates said:
FUCKING SERIOUSLY? "e l g i u" is the censored word, not "b e l g i u m"??!?!?!?!??!?!??!
Godfuck you Discourse you pile of cat vomit.
No - that was a deliberate choice on my part to see if the censoring software exhibited a clbuttic bug.
Hey, @PJH, can you censor
.*
on your test instance and then post something containing that and show us what happens?Why? I put that test in on here a while back:
postgres@hpdesktop:~$ EDIT=censor sql_tdwtf setting # History of setting changes from user_histories uh join users u on u.id=acting_user_id where subject ILIKE '%censor%' order by uh.updated_at asc updated_at | subject | username | previous_value | new_value ----------------------------+----------------+----------+----------------+----------------------- 2014-11-06 11:06:41.437128 | censored_words | PJH | | elgiu 2014-11-06 11:12:29.994805 | censored_words | PJH | elgiu | elgiu|belgium 2015-03-17 20:00:27.470697 | censored_words | PJH | elgiu|belgium | elgiu|belgium|b.....m (3 rows) Elapsed: 0.039s Backup taken: 2015-12-29 11:29:46.995825 postgres@hpdesktop:~$
Hmmm...
Belgium
B.....m
BotttomEr - seriously? That never used to work like that; goes some way to explaining my footnote...
LOL - Preview before closing the fence:
After:
-
> on your test instance
Config:
Entry+preview:
Post:
Found the problem - adding the explicit one, anything matching the regex periods gets censored:
Not interested in
.*
however.
-
Not interested in .* however.
I am almost 100% certain that would completely break your instance beyond usability. Even if you remove the censor settings, there'd be so many "baked" censored posts and URLs that Discourse would like shit so much it'd come out of it's mouth, then it would die.
Of course you could always restore from backups.... .... sorry, couldn't keep a straight face thinking that Discourse is something that one can simply "restore" from "a backup". Just don't break your forum. Breaking your forum is
-
He could probably recover, though. The admin section is like its own little world, little affected by other settings. Which is annoying when you get circle avatars there, but probably useful when it forgets to censor itself.
-
Not interested in .* however.
Your post didn't contain
.*
, which is what I wanted to know about.
-
Your post didn't contain .*, which is what I wanted to know about.
Yes it did. You even quoted it...
Pedantry aside, what it didn't contain was a screenshot to corroborate the lack of interest...
-
Found the problem - adding the explicit one, anything matching the regex periods gets censored
HowTF does that happen? I'm trying to imagine what the (broken) algorithm would look like. It's a literal search not a regex search, unless it is found with the literal search, then it becomes a regex search? ?
-
HowTF does that happen?
of course, of course.
Mr. Ed - Intro (Opening Theme) – [00:19..00:42] 00:42
— PsychoDad1860
-
Literal search followed by preg_replace, because that's faster than just preg_replace? But then you'd expect .* to censor as wellโฆ a puzzler.
-
Knowing there's probably some MD5 involved as well.