TCotCDCK is so pleased with their efforts to use Discourse as an issue tracker, they have now introduced a tool for migrating GitHub issues to Discourse.
I wish I was kidding.
Filed Under: This is not a facepalm. This is a facepalm.
TCotCDCK is so pleased with their efforts to use Discourse as an issue tracker, they have now introduced a tool for migrating GitHub issues to Discourse.
I wish I was kidding.
Filed Under: This is not a facepalm. This is a facepalm.
Continuing the discussion from The Backup Likes Thread - Because it's not the same:
@abarker said:@HardwareGeek said:@Luhmann said:This doesn't feel the same ... I'm continuously forgetting to like here ...I'm not forgetting; I'm protesting the ex post facto imposition of the rule in this topic.
Are you saying that we should start yet another likes thread with the rule baked in from the start?
Because I can do that.
Because the Original Likes thread has been put on the step, and @HardwareGeek and @Luhmann don't like the Backup Likes Thread, we now present the Backup Backup Likes thread.
This thread has only three rules:
If you can abide by those rules, then welcome! If not, then GTFO.
@accalia said:what if you can abide by the rules but choose not to?Then we'll create the backup backup backup likes thread!
Good point! Nothing stops us from trying over and over and over and over and over and over and over …
Reminds me of a shirt I got when I went to Austria in high school:
I got so many weird looks when I got back, and a few people came up and tried to correct me.
what if you can abide by the rules but choose not to?
Oy! I think that fits under the "If not" portion.
Why is called hanzo?
Has to do with some stories from the front page. Details are provided in the Discopædia.
Is it just me, or is this topic missing the magic of the original?
This thread now referenced by the topicalize definition.
Wow there's a very small window for take-backs on liking - 23 minutes and that like is locked!
Take back is 10 minutes.
The backup likes thread has fallen to the exclusion GUID! Long live the backup backup likes thread!
Damn! I knew I forgot something!
I think this one speaks for itself:
British woman claims lawyers should have told her divorce would end her marriage
A British woman attempted to sue her former lawyers for professional negligence, claiming that, alongside a number of other allegations, they failed to advise that finalising divorce proceedings would inevitably cause her marriage to end.
Status: AAAAAAGGGGGGHHHHHH!!!
So my wife suspected she's pregnant. Fine. She took a test and it came out positive. Fine. She went to her OB who confirmed and gave her an ultrasound. Fine. The ultrasound showed two gestational sacs. Fi.. Wait. What‽
At least there's only an 80% chance of actually having twins at this point. Nothing's really for certain until the second trimester.
Status: Found out the baby's sex yesterday (ultrasounds are awesome). Now that we already have three girls, we're finally having a boy!
We told our daughters by making colored vanilla milkshakes with lids and clear straws. Our oldest (7) is super excited because she's been wanting a baby brother since we were expecting the second. The second (4) ended up crying for about 10 minutes because she doesn't want a baby brother (she's come to terms with it now). The youngest (2) was like "I got milkshake."
All told, it went over pretty well.
@Arantor, I am curious about your intentions as well.
I can't believe it's been almost two years since I was last on here. Having a good employer does weird things to you ...
@asdf said in Forum guidelines:
Even requiring [NSFW] tags would be too much, IMO
That's primarily a courtesy we encourage because so many use the forum from work. It's nice to have that warning to avoid awkward situations at work.
@Nocha said:letter avatar cache serverDid they ever do more WTF comparable to this one? It's been a while and I still can't accept they did something that stupid. (apart from the mass-banning, that is)
They way they did it is bad enough (it's not even a cache server). But when you consider their history with the gravatar CDN, it makes it even worse.
: Here you go, when you sign up, we automagically pull your current gravatar based on whatever external account you used to sign up! It's our user friendly default!
: But that's a security problem. First, you can link all sorts of different profiles together based on them having the same avatar. Second, the image URL contains an MD5 hash of your email address. MD5 has been cracked for ages. That makes it crazy easy for people to track you across multiple sites and figure out your IRL identity.
: All right. I guess we can just auto-generate some letters with colorful backgrounds to use as the default avatars.
…
: All these instances are having trouble generating these letter avatars all the time. It's really putting a load on all these instances. Let's build a central server that can handle the load of building the letter avatars on request!
: How is that significantly different from using gravatar? Sure, it's not available across the entire interwebz, but it works across all discourse instances. And you've shown that security between instances in the same container isn't that reliable anyway.
: You are no longer welcome here.
500 Internal Server Error when Liking; yep, this is a Likes thread alright
No, that was when posting.
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
https://meta.discourse.org/t/is-there-a-way-to-install-discourse-without-using-discourse-setup/45270
: stable [branch] isn't recommended, way too far behind.
From that same post:
: There is zero value in using Cloudflare with Discourse, actually negative value as it makes setup and troubleshooting more complex. The only value in CF is DDOS protection, if you are sure you will be DDOSed.
Never change, Jeff. If you did, we wouldn't have such an easy punching bag. :P
@NedFodder said:I'm betting s get disabled for this thread before this post gets 10 likes.Sorry, was eating lunch...
Hidden exclusion GUID
Damn it.
Oh well. 'Twas too good to last.
@abarker said:@accalia said:THE RESOURCE IS BEING HELD FOR "ENHANCED INTEROGATION" FOR IT HAS SECRETS THAT ARE NECESSARY TO EXTRACT TO PROTECT MY QUEEN!BUT IT'S GETTING IN THE WAY OF ME LIKING ALL THE THINGS!A NECESSARY SACRIFICE FOR THE GREATER GOOD!YOU'RE IN THE WRONG TOPIC FOR SUCH SACRIFICES.WHAT'S WITH ALL THE YELLING?
SORRY CAN'T HEAR YOU OVER THE SHOUTING!
ISN'T IT ODD THAT DISCOURSE COUNTS MARKDOWN WHEN TRYING TO DETERMINE IF THERE ARE ANY LOWERCASE LETTERS? THE ONLY TRICK IN THIS POST IS HAVING A QUOTE!
/me eyes @abarker suspiciously<mutter> I will protect my queen....
/me slinks off in an overly suspicious manner
Seems like themodsadmins have been cracking down hard on abuse, according to the "2^0 Posts" description.
FTFY
Well, maybe the belch. Or at least his lack of sanity.
Then why were you aiming that comment at me? I wasn't threatening anyone.
I wonder if you can drive someone sane.
Because driving people insane is such old hat.
Were you by any chance vying for the 100th post?
Nah, he just want's to be the most talkative.
Shut up Discourse.
I bet a mod could come up with some other creative way to hide the bot babbling ...
An admin could change ownership of the posts.
Frustrating because it isn't consistent.
FRACKING 500 ERROR
@abarker said:@RaceProUK said:500 Internal Server Error when Liking; yep, this is a Likes thread alrightNo, that was when posting.
I was Liking
So it's your fault!
I've noticed it a few times, on two different systems.
Bastard! Now we need a backup backup backup likes thread that does exclude those damn bots!
You know what? You can start the next one! Then when something gets forgotten you can take the fall!
Ungratefull belch!
@abarker said:Anyone else having issues finding the sweet spot on the newlevator? The whole thing looks clickable, but only expands when I click just the right spot.Expands when clicked anywhere on it. On desktop at least.
Mobile's different, natch.
I'm talking about desktop. Win 7, Chrome 44.
Not running custom CSS on my home system, and I can (intermittently) repro there.