Moar Cooties
-
Not isitjusmeorservercooties.com?
(Note the lack of a 't'; yes it does resolve)
-
Oh...yeah, that's in there. I just tyoped it transcribing. I didn't notice @PJH's screenshot of the page I was transcribing from.
-
I just tyoped it transcribing.
So when you @accalia something that's @accalia'd, it comes out spelled correctly?
-
Two wrongs really do make a right.
-
@boomzilla said:
I just tyoped it transcribing.
So when you @accalia something that's @accalia'd, it comes out spelled correctly?Yes. My mistakes are routinely better than other people's successes.
-
Also, your mailer is sending out non-working links. Highly unprofessional. I'd unsubscribe from your newsletter but the ink is broken.
Odds are it's missing the port number. Feel free to file a bug report over at meta.d.
More seriously, you've been promoted to admin.
-
-
That last peak was about when I tried to load @Frostcat's profile to check his page.
-
Yeah, me too. Got a nice nginx error page instead.
-
Well all I can say is I'm glad it's not just me.
-
F5 doesn't refresh on a dhromebook, but that's how you press it if you need it.
-
Admin panel currently says 20.5GB are free.
You trust information that tells you. That's cute.
-
only changes were testing some of our editor customisations for newer versions of Discourse
Did we ever get those working? Because if what @riking says is true I'd really love to get working profile pages back.
-
@boomzilla said:
Admin panel currently says 20.5GB are free.
You trust information that tells you. That's cute.
pjh@what:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 36G 21G 64% / none 4.0K 0 4.0K 0% /sys/fs/cgroup udev 2.0G 8.0K 2.0G 1% /dev tmpfs 396M 332K 396M 1% /run none 5.0M 0 5.0M 0% /run/lock none 2.0G 1.2M 2.0G 1% /run/shm none 100M 0 100M 0% /run/user pjh@what:~$
Did we ever get those working? Because if what @riking says is true I'd really love to get working profile pages back.
Go over there and see if you can break them - more than I have already that is; I filed a bug report on here about the bits I found wrong, and I've not had any suggestions to fix them yet.
I'm willing to allow someone admin access to that instance to test fixes/improve the UI if they're willing to donate the time.
-
Because if what @riking says is true I'd really love to get working profile pages back.
Or, you know, be able to set your title if, say, you got, I dunno, a new badge.
-
Is it a badge that's allowed to be used as a title? IIRC, not all of them are.
-
Is it a badge that's allowed to be used as a title?
I know someone else is using it, so yes.
-
I thought all of our custom badges were allowed. If not, I'd say bug an admin and maybe that will be fixed.
-
If not, I'd say bug an admin and maybe that will be fixed.
do the odds of it getting fixed vary depending on which admin we ask?
-
do the odds of it getting fixed vary depending on which admin we ask?
No. All are equally unlikely. Especially the active ones...
-
Anyway, for the interested:
postgres@what:/$ psql -d discourse -c "select name, allow_title from badges where allow_title=false" | cat name | allow_title --------------------+------------- Read Faq | f CLOSED - WONTFIX | f CLOSED - INVALID | f CLOSED - DUPLICATE | f CLOSED - FIXED | f First Flag | f Basic User | f Great Share | f INB4 fail | f Great Topic | f Good Share | f Good Topic | f Great Post | f Autobiographer | f Member | f First Quote | f First Like | f Editor | f Promoter | f Champion | f Reader | f Campaigner | f Test | f First Share | f Nice Share | f Nice Post | f Good Post | f First Link | f Nice Topic | f Welcome | f Anniversary | f New Badge | f Hot Link | f Popular Link | f Famous Link | f (35 rows) postgres@what:/$
-
I think it's discoappropriate that report_js_error was the number 3 URL in yesterday's report:
Top 30 urls by Server Load Url Duration Reqs --- -------- ---- POST /topics/timings HTTP/1.1 125261.42 91081 POST /draft.json HTTP/1.1 12001.71 6387 POST /logs/report_js_error HTTP/1.1 8745.91 1808
It's pretty much always in the list, usually in the top half, I think. Nothing really problematic in this round, though.
-
I don't think the CLOSED badges will ever be awarded, because you guys never close topics (except for /t/1000, but for some reason that doesn't count ).
Also, why not allow INB4 fail as a title? The other INB4s are allowed.
-
I think it's discoappropriate that report_js_error was the number 3 URL in yesterday's report:
One is wondering what, if anything, was going through your mind when you decided to link to that particular post....
-
One is wondering what, if anything, was going through your mind when you decided to link to that particular post....
It gives me a handy link back to this topic for the next time I see something interesting in the reports.
So, as per usual, only thoughts of what makes my life better were going through my mind.
-
One isNon-staff are wondering what, if anything,was going through your mind when you decided to link tois in that particular post....FTFY
One
iswould wonderingFTFY again.
-
Ah - ok; nice save...
I'll consider retracting my previous comment.
-
Nothing overly interesting. Parts that don't need anonymonging:
-
If something goes wrong in the client, it sends the error to the server? So what happens if the client error was due to the server timing out, and it tries to log the error, which also times out...does it continue infinitely until the browser crashes or the server comes back to life?
If so, that could explain a LOT. A few timeouts would snowball into a big avalanche of server cooties.
-
That's a fairly common thing to do (if all you want to catch is issues not related to connectivity); see HPKP reporting. Useful for debugging things like CSS/JS/HTML issues that don't affect the delivery of the page. If the report fails, the client probably just shrugs its shoulders because at that point it's not really mission-critical.
-
Ah - ok; nice save...
This question was asked before, too:
https://what.thedailywtf.com/t/moar-cooties/52855/102?u=boomzilla
I have a memory of @accalia asking about that, too, where I have a less terse answer (very similar to the one I gave to you) than my reponse to @Polygeekery but it doesn't appear to have been in this topic.
-
If something goes wrong in the client, it sends the error to the server?
I have wondered this many times. There does appear to be something that shows up in the logs here, but I've never been able to make much sense of it.
-
I thought all of our custom badges were allowed.
The badge page says it is, and @doctorjones uses it in his title. It's just that I can't actually set it all day today because the edit button causes a 5-second or so lag, then a 502.
-
```jeff
Top 30urls by Server LoadUrl Duration Reqs
POST /topics/timings HTTP/1.1 125261.42 91081
POST /draft.json HTTP/1.1 12001.71 6387
POST /logs/report_js_error HTTP/1.1 8745.91 1808It's nice to know that the top 3 pages on this site provide 0 content for users to read.
-
Asking out of inquisitive ignorance (NOT blame pointing!)... is it possible that auto-reader activity is being counted in /topics/timings requests? Seems a little weird to me that there would be an order of magnitude difference in that one request path...
-
is it possible that auto-reader activity is being counted in /topics/timings requests?
Yes. That endpoint is for all read tracking, no matter the source; if you look in the browser Dev Tools, you'll see that endpoint hit as you scroll through threads.Auto-readers already limit how much they hit that endpoint, as they only hit it for posts not already read; also, there were some recent changes to prevent SockBot instances auto-reading dormant threads.
-
@fbmac said:
I came here to post this image
tooand then delete the post.FTFY
And neither happened...
-
https://what.thedailywtf.com/t/website-performance-reports/49861/252?u=boomzilla
LOL...mafia ended with lots of Jeffing, so @abarker finally beat @RaceProUK:
Top 30 users by Server Load Username Duration Reqs Routes -------- -------- ---- ------ [Anonymous] 198814.07 108998 topics/show(62862.03) - (POST)(60551.62) -(35861.68) user_avatars/show(19143.96) topics/posts(4260.86) abarker 8087.49 4111 topics/timings (POST)(4147.93) topics/show(642.52) posts/create (POST)(482.71) topics/posts(470.24) posts/show(447.20) RaceProUK 7324.89 5569 topics/show(3148.28) topics/timings (POST)(1515.23) topics/posts(1036.57) list/latest(506.51) posts/create (POST)(323.48) PaulaBean 6787.20 12591 topics/show(6748.88) list/category_latest(37.49) topics/status(0.82)
-
Is it possible to get my load figures broken down by IP?
-
Apparently, @PaulaBean wanted a turn on top today:
Top 30 users by Server Load Username Duration Reqs Routes -------- -------- ---- ------ [Anonymous] 95782.06 125081 topics/show(53698.39) user_avatars/show(11043.25) - (POST)(10066.83) -(7357.54) topics/posts(2727.37) PaulaBean 9135.46 15610 topics/show(9093.77) list/category_latest(41.69) RaceProUK 5375.53 5788 topics/show(2653.90) topics/posts(1082.71) topics/timings (POST)(597.38) posts/create (POST)(342.61) list/latest(251.10) accalia 3414.08 3583 topics/posts(1589.78) topics/timings (POST)(634.72) topics/show(355.72) posts/create (POST)(240.33) list/latest(193.45)
I didn't even make the top 20.
-
Never get between a lady bot and her desire to be on top.
-
There was a super cooties storm while some of us were screwing around in the likes topic. So @boomzilla mega-Jeffed the likes topic again, but the cooties came back. Any ideas what it could be now?
Also re-posting this since my first one got mega-Jeffed...
Paging @Onyx and whoever else: TRWTF isn't Discourse anymore. Well it is, but not for us.
-
@NedFodder the bikeshedding session already happened on IRC. Will be fixed one of these days (read: when I get the time)
-
@NedFodder I heard on the grapevine there was another DoS attack; @ben_lubar?
-
@NedFodder said in Moar Cooties:
Any ideas what it could be now?
@boomzilla said in The Official Status Thread:
The cooties resumed almost immediately after I moved that back out to where it can be seen.
-
@Onyx said in Moar Cooties:
Will be fixed one of these days (read: when I get the time)
It's actually a nice meta-WTF at the moment!
-
so Likes topic is still a killer?
-
@darkmatter a very loving killer.
-
@darkmatter Sort of. Maybe. At the very least, there's a relatively simple DoS vulnerability.
-
@boomzilla seems like that alone can't be the problem - I "liked" around 3000 posts in 2 browser windows in a span of 10 - 15 minutes the other night and it wasn't a problem for the site at all.