Wedge

I'm against it. What matters is that GIF/PNG files are the smallest possible. Not their particular file format. GIF is smaller than PNG most of the time when optimized correctly.

In your particular case, that would fix it. In my case (the matryoshkas), I strongly suspect that wouldn't.

Me neither... Which is a big problem :P

And I guess no one else than us is reading this...You shouldn't worry about it. If only because Aeva's code is originally not by me -- so I had to learn how Dragooon did his gallery stuff and how Karl did his embed stuff. Then I did my best to improve on their already very good work. :)
I'm sure I could get to work on the plugin code too if I wanted, but I have to admit I was scared by the amount of commits related to it. It's just.. Easier to let people who use plugins debug it :P
Because one of my reasons for doing Wedge was that I could have in core whatever I had in my mods or custom code... :PYes.Certainly a good suggestion.More like... (When it comes to entry names.)

Configuration
   Features and Settings
      General
      ---------------
      Pretty URLs
   Moderation
      Settings
      ---------------
      Anti-Spam
      Warnings
      ---------------
      Filters
      Add filter

(I'm also positive Pretty URLs configuration could still be moved somewhere else, so that Features and Settings could let go of the sub-menus.)I understand that. That's also why I added the separator between moderation settings and filters.
Technically, though, we could always do that restructuring later, to give people time to 'discover' the filter system, but then again we'll probably have forgotten about the restructuring by then... :PWhich means that, in SMF developers' minds, a m.approved test is very close to a t.approved test because in SMF, an unapproved topic can't hold approved posts. I think. Meaning I'll definitely have to add {query_see_topic} for all m.approved occurrences... Which is a bit too much. Doing a {query_see_message} will be simpler whenever there's a query without a 't' join, but it still means that this will have to hold a subselect on the topic table...

Oh, my...Let's take a concrete example. Recent.php.
Look at the only query with a m.approved test. It doesn't test for topic privacy. Then, the subsequent query does a topic join but doesn't have query_see_topic, either. In the end -- it's broken.See just above. :(Would you feel up to the task for this, by any chance......? :whistle:

Oh, I'm doing the privacy tables, and a bit of a bummer with indexes... I have no auto-incrementing fields, and just a id_topic, privacy_type (groups, members...) and privacy_id (group ID, member ID...). So basically an index on this would be based on all three items, not one more.
Would it help at all to add a primary key based on the three keys...? Or is it a waste of space? (Maybe if I add a field later it'll be useful, of course... But right now I'm not so sure and I'm not well versed in MySQL indexing.)They wouldn't be penalized...? query_see_message would always return 1=1 on a filter-free environment. However, and that's important, the topic table would always need to be tested against. Unless I make the privacy system an option, of course, rather than something always active...Would be fixable I think -- if anything, by renaming these custom aliases to 'm', and renaming the other 'm' to something else...I have no idea what you meant here :P
To me, single quotes and double quotes can always be used in a field. It's just when *communicating* with that field that one has to be careful... i.e. you have to escape quotes at the last moment when inserting data. But that's really the ONLY moment I can think of where we absolutely NEED to escape stuff... Unlike a 039 that has no particular purpose in a table row.It's always going to be this way. Even if we encrypted data in the database -- there's nothing preventing a plugin from accessing said data through Wedge functions, and then returning them to the admin, etc. It's a trust issue.

So, basically, respecting topic privacy against admins means that query_see_topic will need to test against the privacy field, rather than just returning 1=1. I'm fine with that, BTW.That's way out of my league.Any interesting topics to catch up with over there...?I don't know, I've never watched Jersey Girl and I hated Jay & Silent Bob Strike Back, his worse movie by far IMO, but I loved the rest -- Clerks, Mallrats was okay, Chasing Amy is still is best to day, Dogma was great, Clerks II was as good as the first, and Zack & Miri was as sweet as it was crude, which I enjoyed. I finished watching the first episode of Comic Book Men since last time I mentioned it, and it really, really sucked HARD. I ended up doing something else while the episode was playing. Which I usually don't do... I guess my main problem is that I hate French unscripted shows. It's the first time I'm watching a US show of that bastard kind. It's just every bit as boring and annoying. And unnatural. Which is not exactly was unscripted should stand for.... And did I mention boring? Yes I did. And boring? Did too. I really don't care about people selling collectible items in a comic book store. And *I* worked for some time for a comic book store back in the mid 90's! (Wasn't selling items or anything, it just means I should really be interested in that kind of show.)It's on my to-do-list, at worst ;)Just like my current plans. :)

The error system has its errors itself.

For instance a template error (index?) will sometimes regenerate the full page inside of itself. I always smile when it happens. No biggie though. I don't know about the problem you mention though.

Yep, I remember that...

Okay, time for bed. I'm gonna get killed otherwise :P

"Quick search" ;)

BTW, I tested the PM settings page -- shouldn't there be a "min" setting of 0 for minimum number of PMs etc...? I can go under 0 by clicking the buttons, it's funny ;)Well, it's going to be... interesting, seeing whether I manage to put Wedge online here on March 1st as promised, or if I'll have to postpone it again because we're in the middle of some complex changes... :P

With that kind of granularity, I'm surprised you could even consider not allowing topic privacy for multiple specific membergroups and contact lists... I'm sure that's something you'd have brought up less than a few months after the feature was implemented :P