denise | (no subject)

Please tell people that I will be in Sydney for a few days this week, and if anybody wants to hang out, to watch

mark for an announcement of time/place/something.

I am undecided about alerting folks to the interests issue. On the one hand, mass panic will ensue (maybe). On the other hand, more reports might make it easier to triangulate or dodecahedronate the cause.

News notice of "back up your bleeding interests" is probably not a bad thing, along with "no, it's not a sign of account compromise, it's a sign of a FUCKING BUG", might prevent some panic.

Yeah, and interests can be downloaded at:

http://www.dreamwidth.org/misc/interestdata.bml?user=USERNAME

Gradation is mostly tweaked now--most pages should work, and people who find other (more hidden) areas that are problematic should still report them to here: http://dw-dev.dreamwidth.org/33203.html

I just pasted mine into an entry, and the thing I did with explaining all of them may start a meme.

Changes to the screening behavior, and the popular with circle page?

Additional inbox sections (poll section, unread section) -- I've made very good use of both of these for cleanup by now :D

Fix for crossposting footer being silently truncated -- it's longer, too. Weird characters in feeds also fixed! Option to not save external passwords may be worth a mention since, IIRC, we promised this some time ago.

Perhaps a gentle/cheerful reminder that we welcome reports of any kinds of issues, because we may not know about them yet. (Thought triggered because I just accidentally found out about one bug via an aside in an entry saying "perhaps they'll fix it soon!" *g*)

Yes it is, please don't do this. We've had reports from 3 or 4 people, tops, and the news post goes out to 60,000 people or something.

I do not believe a 0.000022% chance of this bug hitting you is worth broadcasting it into news and making people all worried. We do have to have some sort of minimum threshold on what to panic people over, and this does not meet mine.

I'm also not convinced they're actually changed. My money is on a memcache problem.

If people are using Firefox and are finding that long entries with long comments are cutting off at some seemingly-unspecified point, tell them to append ?usescheme=celerity to the end of the URL and see if that fixes it. If it doesn't, they should contact Support.

Does Celerity also work? I thought only Lynx worked... Huh.

According to my notes, it is a problem specific to Tropo. I don't think I am confused, but feel free to double check if you want.

Nah, I believe you ;)