Depends how you do it.
Posts made by end
-
RE: So... I am no longer blind about performance here ...
we want to know that our issues are being heard and considered. We want to feel that we matter as users to the developers of the software.
You guys definitely matter!just not as much as the people that pay us actual money
-
RE: Zed Shaw gets schooled on C undefined behavior
Zed Shaw used to work for Bear Sterns, which I thought was hilarious. Up until they stopped existing.
-
RE: So... I am no longer blind about performance here ...
I just changed it from 5 minutes cache to 10 minutes, so hopefully it will help.
That is a good start but it needs a bit more sophistication, e.g. scale the interval with post age as well. On older TDWTF topics poll for comment topic changes even less often. -
RE: Jeff Atwood knows what good code is like
Why would you blindly quote the URL in the post right above yours?
Doing it wrong, man!
-
RE: Changing DISCOURSE_SMTP_USER_NAME ?
We almost went about 47 nanoseconds without a new bug appearing.
Well, to be fair, it was 40 more nanoseconds than last time. -
RE: Imports (Was: {brace yourselves} the import is coming {Spoiler Alert: Not all of it} [i.e. blakeyrat was not utterly wrong for the first time ever] Filed under: append-only titles.)
We have some expertise on archiving old forums now, which turns out to be.. hard.
I always try to convince customers not to do imports at all, and archive the old site in place as static HTML with our help. Alternately, just do what SitePoint did and pick the "top" topics with the most organic traffic and just migrate the best stuff. Or the last year or two. Anything to cap the amount of data converted.
-
RE: Discourse Metabooty
I am reading this on an iPad Air 2, so believe me, we care about tablets.
Just, you know, tablets that people actually use.
(Not that it is all wine and roses, you should see the crazy crap we had to do because iOS 8 Mobile Safari has these insane positioning bugs)
-
RE: Quoting broken on Windows Phone 8
Well, to be fair, the market share for Windows Phone has done fuckall since then too ;)
-
RE: Forums migration
Migrations are hairy.
I always recommend archiving the old content (leaving it as static HTML, which is a lot harder than you might think) and starting fresh if you can. That way nothing is lost.
Ironically the more and older and larger the content is, the stronger the argument in favor of archive and start anew. For smaller sites, less inertia, less old obsolete content.
-
RE: Discourse Metabooty
I love that quote. It might be my favorite thing I have ever read on a computer screen because it is so deeply true:
We are vulnerable, but we don’t want to be reminded of that. We want to believe that the world is understandable and controllable and unthreatening, that if we follow the rules, we’ll be okay. So, when this kind of thing happens to other people, we need to put them in a different category from us. We don’t want to resemble them, and the fact that we might is too terrifying to deal with. So, they have to be monsters.
There is a reason that article, as terrifying as it is, won a Pulitzer.
Also, nice mugs!
-
RE: Discourse Metabooty
It's all good, just pointing out that this is a community that wants to have its cake and eat it too:
-
100% rock solid stability with zero bugs, ever
-
Lots of custom local experimentation and customization, bots, new features, beta versions, etc
Pick one.
-
-
RE: Discourse Metabooty
Could be related to running bleeding edge betas here, also, there's quite a bit of local customization going on in here as well. As I recall there was a badly written bot explosion as well which resulted in downtime.
All fine, it's good to experiment, but know what you're signing up for.
-
RE: Discourse Metabooty
Now, if he wants to donate a larger sum of money to my company that is working on a competitive website that will be releasing a demo for pax in march and an event in April, now we can talk, because that wouldn't be supporting a toxic software.
As long as it isn't written in PHP and MySQL -- aka Server Herpes -- I am for it. -
RE: Discourse Metabooty
The tagging plugin is included in Discourse 1.2 so it is available to everyone, once that releases.
I still like the idea of you guys secret santa-ing each other for the top 6 people who actually filed bugs on meta.d in a constructive way. And definitely include @matches who went out of his way to register a domain and everything.
-
RE: 💣 Discourse 1.2 incoming! 軣
Yes, I will see @sam's 2011 and raise you a 2006
-
RE: 💣 Discourse 1.2 incoming! 軣
Ok the $150 was transferred to @boomzilla for whatever purposes you guys deem worthy -- let the games begin!
-
RE: 💣 Discourse 1.2 incoming! 軣
You can buy a XenForo license if you like. You just can't install it here.
(I think that's only one year though? I have no idea how licensing works, it's a pain in the ass)
-
RE: 💣 Discourse 1.2 incoming! 軣
OK, so who do I send the $150 to? How about @boomzilla? Are you in the USA?
-
RE: 💣 Discourse 1.2 incoming! 軣
I went ahead and sent @pjh a 50 Amazon gift cert.
I think what I would like to do is PayPal the $150 to someone here in the USA and let them be in charge of the process. Can you guys decide who that is, and PM me an email to send the funds to?
It might be funny if
56* people decide what $25 items to send Blakey, and I guess the annoyance factor is in the spirit of what goes on here every day ;)But really it's up to you guys, whatever you want. I just want to hand it over to you so you can be in charge.
PM me!
* math is harrrrd
-
RE: 💣 Discourse 1.2 incoming! 軣
Also bonus points if we can get @blakeyrat something*. I wonder if a secret Santa type thing would be fun where you collectively pick stuff for each other from Amazon with a budget of $25.
* That will doubtless enrage him.
-
💣 Discourse 1.2 incoming! 軣
Which reminds me, how can I reward my favorite beta testers?
I was thinking something like $25 Amazon gift certs for the top 5 folks here who submitted bugs on meta? And maybe $50 for @PJH for exemplary moderator-ing?
But you tell me. With that rough budget in mind ($200), what would you guys like?
-
RE: Grayscale images get belgium-ed
We still do not have a fix for this unfortunately. Sam's idea affected gamma on ALL images which was.. bad. So that had to be reverted. And we know upgrading to latest ImageMagick does not help.
-
RE: Grayscale images get belgium-ed
@sam we should update ImageMagick version for sure, we need a new base image anyway.
-
RE: Logged-out users get a blank screen of death
Remember you can always share by clicking or tapping the date at the upper right of each post. Even as anon.
Date = permalink, etc.
-
RE: Grayscale images get belgium-ed
Definitely something up here, has been reported a few times, seems specific to greyscale images somehow.
-
RE: What's killing off "gameified" communities (yes I made a post of my tweets, suck it)
I don't have enough Forumpointzzz to answer my own questions. Or even comment on them. And if you put the answer in by editing the original question, you're in violation of the "rules", even though there's no other way to do it.
You can always answer your own questions on Stack Overflow. There's even blog posts about it.You can also always comment on answers to your questions (or of course the question itself, which you wrote) even with 1 rep.
What you can't do is comment on answers or questions that are completely unrelated to yours unless you have 50 rep.
Blakey, I must reiterate that I do admire a man who isn't about to let mere ignorance keep him from having an opinion about something.
-
RE: Can't even shoot the messenger
I'm just amazed that there isn't one that pops up to suggest in orange tones that I hold off on committing my reply until I've read more of the thread that the fucking toaster has just occluded. It would be as irritating as all fuck. Huge missed opportunity there, @codinghorror.
The solution is clear -- transparent overlay. -
RE: Jeff has a brother who is a famous woodworker?
I suspect that somehow has to do with the link mysteriously being changed by @riking into archive.today -- the original link was http://www.atwoodknives.com/
So if I had to guess, something to do with unusual TLDs inside quotes.
(it's not even correct as a quote, so it's LIBEL!)
-
RE: Jeff has a brother who is a famous woodworker?
Are you trying to get some of this hot fire?
-
RE: Another terrible project full of bugs
because people left your software because none of their fucking bugs ever got resolved
And for some people, you want them to leave. Remember, the customer is always right... unless the customer happens to be a lunatic psychopath serial killer. -
RE: Another terrible project full of bugs
I thought it was interesting that after a certain date (say 2 years), all old bugs are just discarded. To me this makes sense:
-
stuff has probably changed a lot in the last 2 years; are the original conditions and assumptions of the bug even valid?
-
if a bug survives for 2 years the odds of it being a feature req in sheep's clothing are high
-
if a bug survives for 2 years the odds of it being so minor that it isn't affecting "anyone" significantly, statistically speaking, are high
-
it is good to clean house every so often and if the issue matters, it will come up again organically. And if it does not, well...
I remember Joel, my old business partner, talking about doing this every so often on their own product, FogBugz, which is .. wait for it.. a bug tracker.
-
-
RE: Flagging bugs
No repro, I can see the reply text in flags, old. This is on iPad. Is it browser specific?
-
RE: Site-specific emoji
Emoji override is not a goal for 1.2 but it is up to @zogstrip, if it can easily be done then sure.
-
RE: Discourse is slow on Android. Why?
Well we know Android rendering gets exponentially worse as you add more content so rendering half as much for now at least keeps our head above water. @sam also deferred a bunch of stuff that was needlessly rendered at page load time which helps all platforms.
As I said we will attack it on multiple fronts, but there is just no getting around the disease (getting V8 Android fixed) vs. the symptoms.
-
RE: How slow is Discourse on your mobile?
Lately "latest" has been very bleeding edge, lots of breakages, because we upgraded Ember to 1.8 and 1.9. Much more so than usual but that is why we cut weekly-ish beta releases .. We still have not cut a 1.9 release beta officially, but will next week.
Good news is we are done with global framework changes for a while...
-
RE: How slow is Discourse on your mobile?
Like you're always doing. "Oh, it's Chrome's fault! Oh, it's Ember's fault! Oh it's Markdown's fault!" No. It's your fault.
Are you reading what I write? We pushed on fixes in Chrome / Android and they are in progress. We pushed on fixes in Ember and gave them a perf benchmark. We basically forked Markdown to get fixes to the spec and consistency.If you can't or won't understand that, I'm sorry. But your lack of understanding has nothing to do with me.
also @intercourse we were seeing some big Digital Ocean problems last night; basic Linux server commands were taking minutes to complete, even after a reboot. Seems to have subsided now but we told Alex to ask about noisy neighbors.
-
RE: Discourse is slow on Android. Why?
It starts off at 3883, goes to 3895, and then 3974. I think that's actually worse, but I'd have to find my original post.
Yeah per the original bug entry one side effect of the Chrome android V8 issues is how it constantly optimizes and deoptimizes the JS as it runs, causing massive perf issues, manifesting as huge standard deviations.You would expect to see lots of variability in runtime as a result. All the Android benches in Ember show this to the point that it is hard to tell if anything is getting faster.. 3 sec with a standard deviation of 1.5 seconds? Is that better than 2.5 sec with a standard deviation of 1.5 seconds?
All of which will hopefully go away when the V8 fixes land in a version of Chrome you can download from the Play Store.
-
RE: Discourse is slow on Android. Why?
Those are amazing numbers for Android.
I am telling you guys when the V8 fixes land it is going to be a dramatic improvement. For everyone on all devices, and not just our stuff but in general for heavy JS code. The best kind of upstream fix that attacks the disease not just the symptoms.
-
RE: How slow is Discourse on your mobile?
Ok fine so you hate me, you hate the project, you hate open source projects that offer free discussion software to the world, and you hate attempting to improve open source projects upstream of us. Got it.
And yet here you are discussing it with me, day after day, using this very software you hate.
Who's zooming who, here?
-
RE: Discourse is slow on Android. Why?
This is a long term game; if it takes a decade to get there, so be it.
-
Long Term: Happy to wait 2-3 years for old devices to die off.
-
Medium Term: significant V8 Android improvements are already in the pipeline, only one Play Store update away in Chrome. If that takes 8 months, that's fine too.
-
Short term: we halved the work for Android devices and made a few other deferments of work such as Suggested Topics. Ember team has a perf suite contributed by us and is focusing on perf for Ember 1.10 which is maybe two to three months out.
Android 4.1 sets the right expectations; and certainly people are used to OS versions determining this stuff since on iOS (and AFAIK Windows Phone and Blackberry and what ever other fraction of a percent mobile platforms there are) you have to update the OS to get a new browser version. Android is kind of the outlier in this regard, and that can be a mixed blessing since it means vendors will ship crapbrowser as default instead of Chrome.
-