Wedge

But where could it be compromised?
- Online RSS reader services? What do they care about your particular rss feed when they've got billions to pick from? And what difference does it make with online e-mail services? If I trust GMail with my e-mails reproducing the contents of private PMs, why shouldn't I trust Google Reader with RSS feeds doing the same? And I actually read my feeds, while most of my e-mails end up in spam boxes...
- Sharing the RSS feed link? As I said, it's exactly like sharing your account's user name & password... You can do it if you want -- but don't complain.

Obviously, publishing a RSS feed link with credentials would require showing a disclaimer below the link, something along the lines of, "This is your private feed link, please do not share it with anyone or they can access your personal data."

I basically had some time to think of all that (although never got around to discussing it again), and I guess I think there are more good aspects than bad to this. Don't forget that such a feed would eventually be something like a Facebook wall -- any answers to a thought, any PM would be posted there for your convenience. Wedge would just need to 'log' any data into the feed and drop all older elements from the table, making it faster to retrieve any kinds of data for any user's rss feed.

I'm not saying it should be in Wedge 1.0, but this is something that we should keep discussing with the community -- it's an interesting feature to add, security can be taken care of by letting the admin disable it and the user choose e-mail notifications, and basically if the community wants it and it's fun to implement, why should we stop ourselves from doing it? :)

Completely agreed.

But go tell a newbie to use rss/atom! To each their own...

If only SMF notifications could be made by rss... Oh that's an idea to develop ;)

rev 973 (everything I did while playing Xenoblade this week :P)
(12 files +1, 21kb)

! The smiley cache was always regenerated on each call, because of a last-minute change in parameter order. (Subs-BBC.php, Subs-Cache.php)

* Reprocessed copyright comments in JavaScript files to only cache the bare minimum, i.e. @copyright stuff, and avoid showing the version number and issue date. (Subs-Cache.php)

* The cache folder's htaccess should specify a Vary-Encoding header to make Page Speed happy and help with proxy caching or whatever. (cache/.htaccess)

* Shaved a few extra bytes off the main script file's cached version. I also sacrificed my plain view credit for the menu code for the good cause. It's still in the uncached version though, it's my thing, took me years to finetune it, nearly drove me crazy, I want the whole world to know that stupid script is mine. And that includes you, reading the changelog. (script.js, theme.js)

! Reverted rev 972's removal of the securityDisable_why text string, as it's unrelated to the availability of securityDisable itself. (Login.template.php, Help.language.php)

! Syntax error in PM template. Not sure where this one came from... (PersonalMessage.template.php)

* Tweaked current date's margin and we:block styling. (index.template.php, index.css)

* Spacinazi. (ManageBoards.php)

Did they do that for AeMe, too? :P

Are we all misfits in here? :P

What do they say in Confidential? The 'real name' solution was also the one I'd come up with when watching the episode... Given the fact that IIRC, River had whispered his name in a similar situation (in the ear).

I'm thinking that after the first public releases (alpha or gold?), we will consider at least releasing nightlies.
But not for now...

Always reminds me of the goth kids in South Park (Raisins, The Ungroundable...), they're pretty funny in their desire to stand apart from society and fight against conformism... ;)