The "fa-spin" Testing Thread
-
Your current set of avatars are:
http://what.thedailywtf.com/user_avatar/what.thedailywtf.com/faoileag/20/3811.png
http://what.thedailywtf.com/user_avatar/what.thedailywtf.com/faoileag/32/3811.png
http://what.thedailywtf.com/user_avatar/what.thedailywtf.com/faoileag/45/3811.png
http://what.thedailywtf.com/user_avatar/what.thedailywtf.com/faoileag/120/3811.pngSo the first folder is for size in pixels and the second looks like an ID/GUID as you had '3595' before.
None of the expected images are served under the old ID of 3595.
Try http://what.thedailywtf.com/user_avatar/what.thedailywtf.com/faoileag/40/3595.pngEither the "45" is a typo or you missed that size.
-
you missed that size.
Yeah, I didn't want to brute-force the folders as well as the IDs in case @apapadimoulis didn't approve.
As a quick check I haven't found any differences yet, they do just seem to be different sized copies.
-
This post is deleted!
-
Can you make it big, spinning and have it respond to mouseover?
Dragging this over here (from html abuse thread) [Drop the quote down]
-
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
I'm not sure what you did there, and it might be just coincidence, but my entire computer completely locked up when this was just below the bottom of my window; I had to power cycle it. Thanks for deleting it.
-
I had to force boot my computer too, it's something else in this thread.
-
I saw the original very briefly before it vanished. I think it was just slightly different text, he mis-quoted maybe?
Either way I didn't repro the crashing.
Edit: Oh That's new. All the elements on the screen quickly turn black (i.e. I get a full black window) when I scroll that post to the bottom of the screen
-
The original was a quote too deep, and didn't include spinning action.
The crash occurred for me when I was in this thread for a period of time. I suspect a memory leak that kills computers with low ram.
-
I suspect a memory leak that kills computers with low ram.
Yeah, watching Task Manager, memory use went crazy (well, crazier than usual) before it crashed. Computers with low RAM, yep, that's my work laptop!
-
FF leaking memory and not stopping here. Nothing is even spinning!
Gotta restart it and never return I think.
-
Seems I missed a lot of fun... :-(
-
I'm pretty sure it's @ender's 93 MB gif that's crashing people's browsers. Direct link to file.
Not sure why Firefox needs 2.5GB to load a 93MB file, but it apparently does.
-
GIF does use compression. It's probably trying to unpack it completely which will cause it to go nuts.
-
GIF does use compression. It's probably trying to unpack it completely which will cause it to go nuts.
Hm...
Filed under: Now to construct an image with an optimal compression ratio.
-
If it helps, GIF uses LZW compression within the context of a 'frame', and each frame is not necessarily the full 'area'. You can do partial frames that aren't set at the same position as the previous one and make it effectively a delta from the previous frame.
It's actually kind of cool and can be exploited in interesting ways; in theory you can have more than 256 colours in a GIF if you spread them over successive frames because each frame can have its own palette, and indicate one index of the palette as 'inherit whatever the previous colour was' so with suitably lax image handlers, you could have as many colours as you like provided the frames are suitably managed.
-
If it helps, GIF uses LZW compression within the context of a 'frame', and each frame is not necessarily the full 'area'. You can do partial frames that aren't set at the same position as the previous one and make it effectively a delta from the previous frame.
So, when it unpacks a frame, does it convert that delta to an image in-memory? If so, maybe a solid color with many no-difference frames is the way to go. If your goal was to create the smallest image file that would unpack to the largest in-memory representation, for whatever reason someone might want to do that.
-
That depends primarily on the viewer code rather than the format. But yeah, I'd assume Firefox was creating full-fat frames from the deltas.
-
#Heads-up
@Sam's indicated he's going to rebake the whole forum soon.
If you want screencaps/recordings of still extant un-rebaked bugs/exploits, get them done sooner rather than later.
-
Rebake the entire forum huh?
I hope a certain 4k+ post thread doesn't cause problems.
Also - I assume this means all my random wikis get auto-updated? :)
-
Probably...
-
Also - I assume this means all my random wikis get auto-updated?
If they're all pointing to http://en.wikipedia.org/wiki/Special:Random, then if they don't all point to the same article I shall be Most Disappoint™.
-
This is Discourse, get used to disappointment.
-
#Heads-up
@Sam's indicated he's going to rebake the whole forum soon.
Given the fact that @system's been messing with some of my ancient posts,
http://what.thedailywtf.com/t/the-fa-spin-testing-thread/1481/13?u=pjh
is no longer moving, and Sidekiq's rather busy at the moment, I'm guessing this has now happened/happening..
-
Is there any good reason for the rebake, aside from bad PR we make with our broken posts?
-
Going to break radio silence here and explain myself, cause this was my initiative and I mucked with your stuff.
There are 3 big reasons for the rebake.
-
We are going to run a full rebake everywhere anyway for v1 in the next 3 weeks, the mechanics are already in place https://github.com/discourse/discourse/blob/master/app/jobs/scheduled/periodical_updates.rb#L32 its simply waiting on us upping this number https://github.com/discourse/discourse/blob/master/app/models/post.rb#L19
-
There was an XSS in place that meant security issues could have been lurking in the 30k posts here.
-
There were a big slew of markdown bugs that were fixed in the last month that heavily improve rendering
That said, I am really impressed by this topic, already explained how to add whitelists perhaps long term someone can devise some changes that allow us to pass context to the whitelister and then we can whitelist fa-spin on this topic with a plugin.
Apologies, rebake is over now. Expect another one when v1 is released.
-
-
Yay, @sam is back!
-
# increase this number to force a system wide post rebake BAKED_VERSION = 1
aka
XSS_EXPLOITS_SO_FAR = 1
Filed under:
TIMES_SCREWED_BY_TDWTF = 1
-
An XSS in place that we didn't know about already? For shame, guys, for shame!
-
There was an XSS in place that meant security issues
could have beendefinitely was lurking in the 30k posts here.
FTFY
-
An XSS in place that we didn't know about already?
Hell, we've found at least 3 entirely separate XSS exploits haven't we? (we = not me, I only found a side XSS that was missed by a patch for an XSS that someone else already exposed)
-
There were a big slew of markdown bugs that were fixed in the last month that heavily improve rendering
Nooo markdown bugs are my baby
Don't f with my screwy text, man!
Filed Under: That's not exactly a markdown bug, more of a css issue, I know.
-
for v1 in the next 3 weeks
v1 is only three weeks out? Don't you think that is a bit optimistic?
-
@Intercourse said:
v1 is only three weeks out? Don't you think that is a bit optimistic?
Considering they thought they were basically ready when they came here, I'd call it progress.
-
Considering they thought they were basically ready when they came here, I'd call it progress.
Yeah, they are slightly less clusterfucked now. I would put them in the late-alpha stage, very early-beta stage at this point. My rough guess is that at this rate my toddler will have grandchildren when they reach what I would consider v1.
-
I think we have forced the issue on a lot of huge flaws.
But unfortunately Dicsourse Syndrome is setting in and a lot of people are just settling for the flaws and ignoring them rather than complaining about things that are still broke.
-
I think we have forced the issue on a lot of huge flaws.
But unfortunately Dicsourse Syndrome is setting in and a lot of people are just settling for the flaws and ignoring them rather than complaining about things that are still broke.Discourse Syndrome was forced upon us primarily because @kodinghorror refused to budge, or even acknowledge several bugs. Hell, even the latest I saw over on meta was ridiculous:
https://meta.discourse.org/t/logs-page-now-404s-take-2/17542/2
@kodinghorror thought the address hint in the status bar area was a tooltip, and couldn't understand why @PJH was having a problem.
We had the most success getting bugs fixed when we called on @sam. Even then some of them (such as the search feature) never got touched.
-
Logs page now 404s. Take 2
Yes, that bug was particularly funny in that it essentially demonstrated how incapable of using a browser that @
codingwhorror is.
-
Yes, that bug was particularly funny in that it essentially demonstrated how incapable of using a browser that @<table></table>codingwhorror is.
I honestly think that if @sam weren't involved, @ckdingwhorror would never have been able to get Dicsourse out there. I think it would have died before it ever saw TDWTF.
-
-
That's probably not true, I've seen several reasonably decent people work on the project (who never came over on this side) there's the guy with the fish avatar, and the guy with the guy avatar in the shirt holding the thing.
But @sam is my favorite.
-
It's actually kind of cool and can be exploited in interesting ways; in theory you can have more than 256 colours in a GIF if you spread them over successive frames because each frame can have its own palette, and indicate one index of the palette as 'inherit whatever the previous colour was' so with suitably lax image handlers, you could have as many colours as you like provided the frames are suitably managed.
Not just in theory - you can do that in practice (the thread snapshot I pasted above uses a global palette, meaning all frames use colours from the same 256-colour palette), but doing that was actually harder than having local per-frame palettes (well, at least if I wanted the animation to look good).
Here's a GIF file where every pixel is in different colour:
-
Why don't you just call it DickSores and get it over with?
Because Dicsourse is more subtle, and I enjoy subtlety.
-
That's probably not true, I've seen several reasonably decent people work on the project (who never came over on this side) there's the guy with the fish avatar, and the guy with the guy avatar in the shirt holding the thing.
But @sam is my favorite.
But would @kodingwhorror have been able to bring them onboard without @sam working along side?
-
Probably? I don't know how their pay structure works, or even if they are getting paid.
-
I said in theory because while I've done GIF animations before even in code, I've never played with local palettes so it was only in theory as far as I knew, I didn't recall actually seeing it, but it's cool to see
-
Why don't you just call it DickSores and get it over with?
Because Dicsourse is more subtle, and I enjoy subtlety.
Same reason I say Dicsourse. It's close enough to be considered a simple typo, and usually gets the reader to double-take the first time they see it.
-
@Intercourse said:
v1 is only three weeks out? Don't you think that is a bit optimistic?
Since it's apparently borderline unusable on mobile devices, and many browsers still have trouble keeping the scrolling consistent with the fog-of-war loading*, I think yes, that is very optimistic.
*) Chrome whenever, and Firefox does the occasional skip and jerk when moving upward through a thread.
-
Even then some of them (such as the search feature) never got touched.
@sam did work on the search. It's still useless, but originally it was even worse.
-
@sam is the straight man to @codinghorror's foil.
-
@sam did work on the search. It's still useless, but originally it was even worse.
I know he proposed an improvement. Wasn't sure it actually got applied.