Discourse 1.1
-
Continuing the discussion from Discopædia:
http://blog.discourse.org/2014/11/discourse-1-1-and-release-schedule/
I removed the ugly photo, it was ruining my breakfast.So apparently we're now have Discourse 1.1
1.1 is a polish release
Doubting about making a joke about polish, Polish or Discourse ...
Screw it:
I'm still waiting for the Finnish release ... maybe by then they'll have Discourse truly waxed and polished.and reflects a stabler, faster, more secure Discourse.
So that was what I noticed this weekend ... keeping those posts empty will definitely make for one stable discussion!
It’s what 1.0 should have been
You mean with working search? The thing that is according to the release notes the biggest gain for 1.1?
For the full release notes:
It's a 'polish' release but it includes several new things? First entry under new features would consider as a security omission, but I'll let that slide.
Because this one is no 'feature' it's a fucking BUG! We can argue if it was a bug in code or by design but it was a fucking bug for the users.
Stop live refreshing new suggested topics
And then this:
Site setting for words to censor in posts
is a bug disguised as a feature. Like Sam said: it's the thing that never should have been. Or make it an optional plug-in but since it is a core option I can nicely expect it to work properly.
Allow manual excerpt to be defined past the beginning of the po...
of the pope? Come on! The suspension is killing me!
Oh ..; wait ... because the sentence was incomplete Jeff typed it again:Allow manual excerpt to be defined past the beginning of the post
Thanks Jeff!
But really didn't anybody proof read the release notes? I'm not talking about spelling errors, I'm talking about incomplete sentences, double listings, ...Fix embedded posts background for good
That's a bold statement! No it isn't ... wait I can fix that ...
Fix embedded posts background for good
Better!
That being said ... I totally forgot to highlight the positive nuggets that where in there. There are ... really ...
OK I admit it ... I gave up after 5th bug fix entry because I was getting depressed.
-
That's one huge changelog.
-
Wait, the black ugly user cards are part of Discourse? I thought it was just some messed up CSS on our forum.
-
-
Pretty sure our Forum has one of the better CSSs. We even have a flower down left (currently). Also pretty sure @PJH and @ChaosTheEternal fix CSS things occasionally.
Filed Under: They apparently cant/wont fix that "feature", though
-
Well, it accepts GIFs... let's see if mine works...
EDIT: Well,
loopingthe image is broken...
-
Pretty sure our Forum has one of the better CSSs.
Current site specific (S)CSS - it seems to grow organically...
/* Spiderweb */ /* body { background-image: url('/uploads/default/_optimized/94e/977/63b2128dcc_456x500.png') !important; background-repeat: no-repeat; background-attachment: fixed; background-position: right 60px; background-size: 10%; } */ /* Poppy */ body { background-image: url('/uploads/default/9442/e6250e4f321cf14f.png') !important; background-repeat: no-repeat; background-attachment: fixed; background-position: left bottom; background-size: 5%; } /* Revert small+small+small http://what.thedailywtf.com/t/quickly-save-the-nested-smalls/4661 */ small { font-size: 10px; small { font-size: 8px; small { font-size: 6px; small { font-size: 4px; small { font-size: 2px; }}}}} /* Replace badge */ // http://fortawesome.github.io/Font-Awesome/cheatsheet/ article[data-user-id="20"] .username i:before{ // content: "\f193"; // fa-wheelchair // content: "\f186"; // fa-moon-o content: "\f1db"; // fa-circle-thin } /* Darken/bolden post separators and HRs */ .topic-avatar, .topic-body, hr { border-top: 1px solid #ccc; } /* Revert NEW markers to more visible */ .badge-notification.new-topic { background-color: #6cf; color: #fff; font-size: 11px; font-weight: normal; } .topic-list .badge-notification.new-topic { padding-left:3px; top:-2px; } .badge-notification.new-topic:before { content:''; } .badge-notification { min-width:10px; padding:5px; } /* Stick a border around images */ #wmd-preview img:not(.thumbnail), .cooked img:not(.thumbnail) { padding:1px; border:1px solid #D8E5FB; } img.emoji { padding:0px !important; border:0px !important; } /* Move the poll-close button far away from the show/hide results to stop accidental clicking */ .poll-ui > button:last-of-type { float: right; } .poll-ui > button:first-of-type { float: none; } /* Differentiate between clickable and non-clickable pencil icons top right of posts */ div.post-info.edits a, div.edits a, div.edits a[class] { color: #fe7a15 !important; } div.post-info.edits span, div.edits span, div.edits span[class] { color: #555 !important; } /** Widen the topic progress bar so the arrows aren't overlapped by the last number of the post-count for topics >9999 */ /* http://what.thedailywtf.com/t/dancing-discourse-scrollbars/3154/20?u=pjh */ /* http://what.thedailywtf.com/t/the-official-likes-thread-proudly-doing-it-wrong-since-june-2014-suggested-reply-method-a-class-mention-text-a/1000/18629?u=pjh */ /* http://what.thedailywtf.com/t/the-official-likes-thread-proudly-doing-it-wrong-since-june-2014-suggested-reply-method-a-class-mention-text-a/1000/18634?u=pjh */ #topic-progress-wrapper { left: 0; right: 0; width: 25%; max-width: 555px; margin: auto; margin-left: 75%; } #topic-progress { width:170px; left:100%; margin-left:-175px; } #topic-progress-expanded { width:158px; left:100%; margin-left:-175px; } #topic-progress-expanded .jump-form input[type="text"] { width: 85px; } /* Underline links in posts - only. (but not @mentions) */ #wmd-preview a, .cooked a { text-decoration: underline; } #wmd-preview a.mention, .cooked a.mention { text-decoration: none; } a:not([href]), a[href="#tag"] { text-decoration: none; } /* Stop code boxes getting scroll bars after 20 or so lines */ pre code { max-height: initial; } /* Reduce font size in code blocks */ /* http://what.thedailywtf.com/t/discotime-in-emojiland/3264/34?u=pjh */ pre code { font-size:11px; line-height: 120%; } /** Stop nested kbd's hanging FF https://meta.discourse.org/t/dos-deeply-nested-kbds-hangs-firefox/17991/4 */ kbd * * { display: inline-block; } div.cooked * * * * * * * * * * * * * * * * * * * * { display:none; } #reply-control .wmd-controls #wmd-preview * * * * * * * * * * * * * * * * * * * * { display:none; } /* Have the 'reply as new post' partially visiable all the time to stop people mistakingly clicking on it. See http://what.thedailywtf.com/t/can-we-make-reply-as-new-topic-always-visible/1838 */ .discourse-no-touch .post-cloak .gutter .reply-new { opacity: 0.5; } .post-cloak:hover .gutter .reply-new, .post-cloak:hover .gutter .track-link { opacity: 1; } /* Stop the link extending the width of the gutter http://what.thedailywtf.com/t/can-we-make-reply-as-new-topic-always-visible/1838/6? */ .gutter .reply-new, .gutter .track-link { display:inline; } /* * CSS for logo */ .d-header #site-logo { max-width: 280px!important; } details summary { cursor: pointer; } /* see http://what.thedailywtf.com/t/topic-not-found-doesnt-match-expected-post-style/1144 */ .page-not-found-topics { display: none; } /* Category Icons dont' need to be 150px large... */ .category-logo { max-height: 64px; } /* Badges. Badge names are case sensitive in this context */ span.user-badge[data-badge-name="Someone didn't get the joke"] i::before { color: #DE5D83; /* 'blush' */ } span.user-badge[data-badge-name="@codinghorror"] i::before { color: #A4C739; /* android green */ } span.user-badge[data-badge-name="@nagesh"] i::before { color: #A4C739; /* android green */ } span.user-badge[data-badge-name="I'm a special snowflake"] i::before { color: #ACACAC; /* silver */ } span.user-badge[data-badge-name="Worst of the Worst"] i::before { color: #CC33FF; /* Purple */ } span.user-badge[data-badge-name="INB4 fail"] i::before { color: #A3C00F; /* Puke Green */ } span.user-badge[data-badge-name="Touched In The Head By An Angel"] i::before { color: #e00a97; /* Thick Magenta */ } span.user-badge[data-badge-name="Too Much Time On My Hands"] i::before { color: #967117; /* Bistre Brown */ } /* liked-heart colour */ nav.post-controls button.has-like { color: #FF0000; } nav.post-controls button.like:hover { color: #FF0000; background: #FF8080; } /* Don't fade the footer */ .discourse-no-touch .post-cloak div.actions, .discourse-no-touch .post-cloak .post-actions { opacity: 1; } //staff icons .fa-trophy:before, .fa-magic:before { background-color: #FFF; border: 1px solid #E9E9E9; border-radius: 3px; box-shadow: 0px 1px 0px rgba(34, 34, 34, 0.898); color: #222; display: inline-block; font-size: 12px; line-height: 1.4; margin: 0px 0.1em; padding: 0.1em 0.6em; }
-
The comments really read like a display of what is wrong with the default Discourse look.
-
<aside class="quote">stabler: one who keeps a stable
</aside> _insert horseshit joke here_
-
@The release notes said:
Heck, we even listen to our customers, sometimes!
QFT
Maybe we should propose they link that sentence to http://what.thedailywtf.com/t/things-our-customers-have-said-about-discourse-thread/2202?
-
Awww, the overlay ruins this one :(
-
article[data-user-id="20"]
Wait, you can get CSS to match on data tags now?! Since when?! This changes everything!
*skips off to get rid of a bunch of ugly x-path in Selenium*
-
New feature! All the posts now have the same number of unread posts!
-
-
Since when?!
CSS3 i think, or maybe it's part of CSS2 and no one used it much until recently because of how bad IE6/7/8 were...
-
Looks like since 2011. Incidentally, 2011 was the year I got out of web design professionally; I closed down my independent contractor sole proprietorship so I could go overseas and get my masters' degree, explaining why I missed that bit of news.
-
it's part of CSS2
Yes
and no one used it much until recently
Probably
how bad IE6/7/8 were...
Undoubtably
-
Oh - you mean in general - I thought you meant on here...
-
Wait, you can get CSS to match on data tags now?! Since when?! This changes everything!
Since CSS2(.1?). If it wasn't for that, the whole "use
data-
attributes instead of classes" discussion a few weeks back would make me look really stupid.
-
dude, 18% battery‽
charge yer damn phone!
(one of these might help, i find mine absolutely indispensible!)
-
Was I in that discussion? If so, I was probably on the wrong side because I didn't know you could do that XD Having to dro into x-path to find things by data attribute is a nasty part of my job
-
(one of these might help, i find mine absolutely indispensible!)
I prefer one or two backup phone batteries and an external charger. That being said, my phone is an LTE S3, which has a nasty habit of discharging a bit slower when put on most chargers...
-
oh.... one of those phones....
well unless it discharges at faster than 2.1amp that battery pack will charge it (provided you plug it into USB2, USB1 only puts out 1amp)
-
faster than 2.1amp that battery pack will charge it
It has a current limit of 1A, no matter how much the port puts out. For charging, that is; it will happily put about twice as much load on the battery...
-
The guy at the phone store couldn't believe me that my Razr Maxx didn't have much battery life. "It has the biggest battery on the market!" Yeah, but that's only half the equation, dude.
-
Was I in that discussion?
Is this the one being referenced? If so, no you weren't.
-
It has a current limit of 1A, no matter how much the port puts out. For charging, that is; it will happily put about twice as much load on the battery...
... sounds like it's about time for an upgrade. and for an S3 there are a bunch of upgrades available!
-
Second bug!
It's 42 not 62.
-
... sounds like it's about time for an upgrade. and for an S3 there are a bunch of upgrades available!
Shoo off, I bought it a month ago. It's pretty awesome and cost me a hundred quid or so; if only it wasn't for that terrible battery life, I could easily stick with it for a few more years.
-
Shoo off, I bought it a month ago.
oh. didn't know that fact. I buttumed that you had it a while.
well then...... know any simpleminded people with a Nexus or more recent samsung galaxy that you could trick into trading? ;-)
-
dude, 18% battery‽
charge yer damn phone!
I was in the tram! I guess I could've stuck my hand out and grabbed on to the 600V DC power line...
-
Just a guess, but you might need an inverter and a step-down transformer to make that work. Unless you like cell phones that act like shrapnel grenades.
-
Unless you like cell phones that act like shrapnel grenades.
those are the best burner phones ever!
Favorites of MI6, in favt i think they invented them!
-
Did...did they make an animated GIF of an upgrade hanging?
http://blog.discourse.org/wp-uploads/2014/11/discourse-one-click-upgrader.gif
Shouldn't it be like a time-lapse of a successful upgrade then a hurray all done explosion of rainbows, unicorns and kittens at the end? Something to make me feel confident it is super-duper idiot easy?
-
>and reflects a stabler, faster, more secure Discourse.
Is that why we had a minutes long outage this morning?
>It’s what 1.0 should have been
Oh, so they're admitting that they jumped the gun on the whole 1.0 label? We
could havetold them that.First entry under new features would consider as a security omission, but I'll let that slide.
I wouldn't, but they won't listen to me anyway.
>Site setting for words to censor in posts
is a bug disguised as a feature. Like Sam said: it's the thing that never should have been. Or make it an optional plug-in but since it is a core option I can nicely expect it to work properly.
Apparently Sam and Jeff need to talk more and get their stories straight.
>Fix embedded posts background for good
We should remember that for the next time it regresses.
-
Apparently Sam and Jeff need to talk more and get their stories straight.
I think Sam was agin' it from the beginning, IIRC the topic on meta.d that instigated it. And his current strategy is a "work to change stuff from the inside" sort of thing.
-
-
Is that why we had a minutes long outage this morning?
speaking of which are my bots still online?
upstart says yes... @Zoidberg are you alive?
-
I took the liberty of fertilizing your caviar.
-
It's 23, actually:
-
Just a guess, but you might need an inverter and a step-down transformer to make that work. Unless you like cell phones that act like shrapnel grenades.
thatwasthejoke.gif
If you're trying to prove that I'm blakey's sockpuppet with these trolls, I have to inform you that it's not going to work.
-
I thought he was doing his @HardwareGeek impression.
-
If you're trying to prove that I'm blakey's sockpuppet with these trolls
That definitely wasn't even a thought, but since you bring it up...
Guilty conscience?
-
Guilty conscience?
I don't let anyone to make me feel guilty. If they do, I kill them.
-
reflects a stabler, faster, more secure Discourse.
They really need to clean the mirror, because that's not what it looks like to me.
-
-
We even have a flower down left (currently).
Not any more. @PJH, what happened to the poppy? Today is the actual Veterans/Armistice/Remembrance Day. It's a bit premature to remove it.
-
Maybe it's a reverse-holiday decoration. It's only present on days that aren't Veteran's Day/Armistice Day/whatever the holiday is called in your local location.
-
I thought he was doing his @HardwareGeek impression.
Not quite.
Just a guess, but you might need an inverter and a step-down transformer to make that work.
If the phone wants a DC input, you'd also need a rectifier to convert that back to DC, and probably a capacitor to get rid of at least some of the electrical noise — at least if you want to use it while it's charging.
In theory, since the input is DC, all you really need is a resistor.
It has a current limit of 1A
So it draws 1A while charging, and let's assume it needs 5V. (That's what my cheap-ass Nokia wants.)Vr = Vsupply - Vout = I * R (where Vr is the voltage across the resistor)
600 - 5 = 1 * R
R = 595ΩThis simple solution does have a few problems, however. Aside from the minor issue of potential electrocution, the voltage delivered to the phone is very sensitive to changes in the current drawn by the phone. Even if the phone draws a constant 1A while its charging, what happens when it's fully charged? Presumably, it stops drawing current (or close enough to zero to illustrate the following point). V = I * R, still, but now I = 0A; therefore, V = 0, and both ends of the resistor are at the same voltage — 600V. Which brings us back to
cell phones that act like shrapnel grenades.
There is also the fact that the resistor would be dissipating 595W, which could be a wimpy hair dryer, toasty space heater, really bright incandescent light bulb, or small explosive, depending on how big it is and how quickly you can dissipate the heat.
You can overcome the first problem, to within an arbitrarily small voltage change between charging and done, by using a voltage divider rather than a single resistor. By adding a second resistor to ground in series with the first one, you can keep current flowing through it (and thus a voltage drop across it) even when the load (phone) stops drawing current.
Suppose, for the sake of convenient numbers, that your phone could tolerate 10V without damage. This can be solved to give R1 (the big voltage-dropping resistor) of 295Ω and R2 (which keeps current flowing through R1 when the phone stops drawing current) of 5Ω. This prevents your phone from being damaged, but R1 is now dissipating I2 * R = 22 * 295 = 1180W (and R2 dissipates 5W while charging, and 20W with the load drawing no current).
The difference between Vout in the charging and done conditions can be reduced to an arbitrarily small change by reducing the values of both resistors, but at the cost of making your phone battery charger produce enough heat to melt the train carriage. This is unnecessary, however, because even the 10V-5V swing above is within the ability of an active voltage regulator to manage.
Or you could just use a switched-capacitor DC-DC converter that can handle 600V.
-