This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2701
Archived fixes / Re: Error message on search
« on October 4th, 2012, 05:21 PM »
It was a bug in the plugin itself calling the permissions function wrong and as a result getting a meaningless response back.
2702
Features / Re: Plugin revs
« on October 4th, 2012, 05:20 PM »
(1 file, 1KB, 1 line)
Revision: 52
Author: arantor
Date: 04 October 2012 16:19:41
Message:
! [Topic Solved] Bah, was calling the permissions function wrong. No idea why this didn't show in testing before. (TopicSolved-MessageIndex.php)
----
Modified : /topic_solved/src/TopicSolved-MessageIndex.php
Revision: 52
Author: arantor
Date: 04 October 2012 16:19:41
Message:
! [Topic Solved] Bah, was calling the permissions function wrong. No idea why this didn't show in testing before. (TopicSolved-MessageIndex.php)
----
Modified : /topic_solved/src/TopicSolved-MessageIndex.php
2703
Features / Re: New revs - Public comments
« on October 4th, 2012, 03:15 PM »I'm not a big fan of making it easy to remove the copyright text, but I'd like to make it easy to ADD to it, precisely because it encourages people to add instead of removing stuff... Maybe a small template hook at that point?
I don't really want to put it in the template because that would mean themes could prevent that being applied.
Yes, the credits page would be the best place, but this is a discussion to be saved between plugin authors and plugin users, mostly -- do they feel their theme/plugin/poopoo warrants a footer copyright, or is it okay to have it in the credits page?
I don't know, I update the file manually when I do my uploads... To me, it's just a way to quickly tell people that I've updated the site. Having to go to the admin panel for that would add an unnecessary step in my upload process, I'd say...
Well then, why doesn't it work on my local install...?
Does it work on yours? Did you have the error last time you tried?
2704
The Pub / Re: When can I download Wedge? / Where can I download Wedge?
« on October 4th, 2012, 04:28 AM »
If in doubt, say it. What annoys me is not people who have ideas or who don't know what they're talking about, what annoys me is the feeling of having to explain myself multiple times for the feeling of not being listened to. (Yup, that is certainly one of my failings. I don't mind people doing something different to what I recommend but I will damn well be heard in so doing!)
The only silly ideas are the ones people don't apply a little bit of thought to before voicing.Quote It is not trivial nor is it a problem that you're alone in facing. I've been trying to learn Unity 3D lately, and despite having spent hours banging my head off a wall, I haven't yet been able to face starting a topic to ask a simple question for exactly that same reason. You're not alone.
The only silly ideas are the ones people don't apply a little bit of thought to before voicing.
It sounds like a trivial personal problem but that's how I feel.
2705
The Pub / Re: When can I download Wedge? / Where can I download Wedge?
« on October 4th, 2012, 04:19 AM »
Question from the back, who's Aranator? ;)
The great news is: you can help. Read the discussions, particularly about features and have your say :)
The great news is: you can help. Read the discussions, particularly about features and have your say :)
2706
Archived fixes / Re: Error message on search
« on October 3rd, 2012, 11:57 PM »
Huh, if it's the latest from both trees, I see no reason why it shouldn't work! But I'll investigate when I'm done with what I'm doing right this moment.
2707
Features / Re: New revs - Public comments
« on October 3rd, 2012, 11:56 PM »It has other issues... Like, defining WEDGE_INSTALLER in the first few steps when they're called at the same time -- it generates a warning so I had to add a defined() test before defining it.
Also... Plenty of other little bugs. Like, in rev 1710 I committed an unfortunate change to the ban groups table structure -- by renaming id_ban_group to id_ban_id_group. Probably a failed search & replace...!
BTW would it be possible to have you write a small plugin for wedge.org...? I'd just like to move the rev.txt and Facebook code to a plugin so that it doesn't end up by mistake in our final files...
There are only so many things that can be done in a plugin - either creating a template within some kind of template layer, or replacing the template in its entirety, or we have some structure that can be manipulated inside the template. It might be nice to have a $context variable that can be updated, though, in case people want to have custom copyrights in the footer (even if we think it's generally unnecessary when having the credits page)
I am also inclined to make the revision number available from the admin panel rather than being a file, just seems like it might be easier (and faster) - but I'm happy to make it either way.
Any ideas how to fix that one..?
8: Undefined index: latestRealName
File: /Sources/Subs.php
Line: 1534
(And more.)
It's the common_stats code. Very likely a bug caused by updateSettings being disabled during the install process..? But it should be enabled at that point, shouldn't it...?
2708
Features / Re: Hellbanning, aka global ignore
« on October 3rd, 2012, 07:47 PM »(1) Wedge is known to offer this feature,
(2) Banned user may not be so stupid and might read about it,
(3) they may simply log off (if they're not also tracked by IP), or look for their topics through google, then explore the cached version (in which case IP tracking won't help at all), and they would then be able to see the guest version of their topic -- which doesn't have their posts.
The point is not to be a single catch-all magic bullet. It's to deal with enough of the pains in the neck who aren't quite smart enough to realise they're being trolled.
(4) User might then choose to retaliate for the waste of time and/or to complain about the silent censorship.
* That's an even better opportunity to rename the 'approved' field to 'status', and have it set between several flags, such as 'unapproved' (has to go through approval), 'live' (normal post), 'ignored' (hellbanning), 'hidden' (user chose to temporarily hide their post through a button, which they can re-publish later)... Or even, although I wouldn't recommend it, 'scheduled', i.e. post won't be shown until the scheduled time is right. Of course I'd rather have a separate table for scheduled posts, because otherwise the post ID would give away that it's not a live post, you could even recover the original posting date by comparing with posts with similar IDs.
Ignored is a complicated one because it's not simply ignored. It's 'ignored, unless the author is the current person' which starts to get expensive.
Hidden... I don't like the idea. I fail to see a situation where you'd ever want to legitimately do that.
Scheduled, very definitely should be in a separate table. There's all sorts of issues that relate to that, as I've been discovering with Game Memorial.
* At hellban time, give the moderator the choice between 'ignoring all existing posts' (e.g. spammers), or 'ignoring future posts' (i.e. do not change status for existing posts).
As far as future posts goes, sure, that's a per-post flag.
* User can view own posts normally. Moderators can view them but with a specific style around the post showing that it's globally ignored, and the Quote/Reply buttons should be disabled to prevent a moderator from accidentally quoting a post and then having others point out that the post was non-existent in the first place.
I think it's an interesting thing to explore, provided we find workarounds for the 'things that could go wrong' area...
2709
Archived fixes / Re: Error message on search
« on October 3rd, 2012, 07:32 PM »
Smells to me like Security.php isn't patched up to date with the SVN trunk version, since I can no longer reproduce this on my local site even as a non-admin.
Or that the version of the plugin is not necessarily the most recent... I did change the code there too but for something else.
Or that the version of the plugin is not necessarily the most recent... I did change the code there too but for something else.
2710
Features / Re: Hellbanning, aka global ignore
« on October 3rd, 2012, 05:25 AM »
Well, it is exactly a variation on Annoy User - Annoy User is explicitly errorbanning and slowbanning as described above, and it comes with all the passive aggressive mentality, it's just one step beyond.
I've been debating bringing Annoy User into the core too - for those persistent pains in the neck that a typical ban would not deal with.
As far as quoted posts go, yes, you'd see quoted posts. But since no-one but admins would see the original posts, there wouldn't be any opportunity to quote them. All you'd have is a period of overlap where the posts would be able to be quoted but it would die off soon enough. This is where you get into the realm of users who were once good members but have gone bad.
Essentially, actually, I'm thinking you'd have to go through several lines of warning before this even became an option anyway, so it wouldn't affect anyone except the most persistent irritations.
I've been debating bringing Annoy User into the core too - for those persistent pains in the neck that a typical ban would not deal with.
As far as quoted posts go, yes, you'd see quoted posts. But since no-one but admins would see the original posts, there wouldn't be any opportunity to quote them. All you'd have is a period of overlap where the posts would be able to be quoted but it would die off soon enough. This is where you get into the realm of users who were once good members but have gone bad.
Essentially, actually, I'm thinking you'd have to go through several lines of warning before this even became an option anyway, so it wouldn't affect anyone except the most persistent irritations.
2711
Off-topic / Re: Happy birthday, Arantor!
« on October 3rd, 2012, 05:13 AM »
I personally take the view that I am neither late nor am I early. I arrive precisely when I mean to, and I expect nothing less of anyone else :) ;)
2712
Features / Categories as boards
« on October 3rd, 2012, 03:58 AM »
This is a slightly odd proposal but here me out.
People often want to make sub-categories. While you can certainly use sub-boards for organisation, categories do offer a clearer method of organisation - you don't just get to separate boards into a hierarchy, you can create a sideways hierarchy or sorts too.
And it occurred to me: if you create a category as a type of board, you get to create sub-categories, apply permissions, and probably even simplify the code should you want to do so.
Thoughts?
People often want to make sub-categories. While you can certainly use sub-boards for organisation, categories do offer a clearer method of organisation - you don't just get to separate boards into a hierarchy, you can create a sideways hierarchy or sorts too.
And it occurred to me: if you create a category as a type of board, you get to create sub-categories, apply permissions, and probably even simplify the code should you want to do so.
Thoughts?
2713
Off-topic / Re: Happy birthday, Arantor!
« on October 3rd, 2012, 03:16 AM »
Um... my birthday was Monday :whistle:
2714
Features / Hellbanning, aka global ignore
« on October 3rd, 2012, 02:58 AM »
I've been thinking about this for some time. As part of my extensions into the warning/banning system deal, I've been considering adding this in as a last resort.
Hellbanning, or global ignore, is an option whereby all topics and posts by a user are invisible to everyone except themselves. The idea is that they can post freely without realising that no-one else can see their nonsense.
There are some interesting asides to it:
1. Performance is likely negligibly affected, if implemented in the core. As a plugin it's a bit different but probably not that significant. (It's just way cleaner if I make it part of the core)
2. If the user was once a meaningful participant, it could be awkward to hide all the posts and topics as if they never happened, meaning you almost have to consider making it a filter applied at the post level to block a user's contributions after a given point (which *does* bring in all kinds of performance considerations)
3. There are potential issues with hiding posts - you never actively tell the user that they're being punished, but that's part of the point. Never telling them means they don't know, and beat themselves against a wall until they leave. It also means they never have a way to defend themselves or represent themselves.
Basically, I want to give people tools to be able to manage their communities. I want them to be able to deal with troublemakers and have whatever tools will be able to do that effectively. This is why I want to make the warning system more granular, so that instead of very broad levels of punishment (watched/moderated/post banned), you can have punishments that suit every level of troublemaker, right up from inappropriate signatures and avatars (temporary/permanent removal of specific privileges) through to inappropriate content (various tools that I don't want to mention yet, heh[nb]I have some... interesting... ideas that I don't want to spoil yet but that will really help with dealing with troublemakers IMO), and generally inappropriate behaviour (moderation, inability to login/browse, i.e. bans)
The other matters, removal of privileges etc. are fairly subtle but ultimately quite 'safe' punitive measures - a user who is subject to them knows that they are subject to them. But a user subject to hellbanning - or, for that matter, the annoy-user measures such as slowbanning[1] or errorbanning[2] - would not know they are subject to them. They can log out and not see these things, and before anyone so much as breathes 'by IP address' (:P) I would remind them that IP addresses are not reliable and that such things will cause people to be punished unnecessarily and unfairly.
Especially if, say, it's applied to a university or workplace range where proxies are in place. Getting another IP address is not a problem for anyone determined enough to really cause havoc anyway.
I'm also aware that this concept is absolutely nothing new, I just want to be sure that if I do implement it, it is with the best of intentions and that I put in safeguards to try and prevent it from being any more abused than it could be; I don't want to wrap admins' hands in kid gloves but I don't want to hand them a loaded gun either. This sort of measure is not a first resort for troublemakers, it is a last resort, and I want the system to reflect that.
Thoughts would be appreciated.
Hellbanning, or global ignore, is an option whereby all topics and posts by a user are invisible to everyone except themselves. The idea is that they can post freely without realising that no-one else can see their nonsense.
There are some interesting asides to it:
1. Performance is likely negligibly affected, if implemented in the core. As a plugin it's a bit different but probably not that significant. (It's just way cleaner if I make it part of the core)
2. If the user was once a meaningful participant, it could be awkward to hide all the posts and topics as if they never happened, meaning you almost have to consider making it a filter applied at the post level to block a user's contributions after a given point (which *does* bring in all kinds of performance considerations)
3. There are potential issues with hiding posts - you never actively tell the user that they're being punished, but that's part of the point. Never telling them means they don't know, and beat themselves against a wall until they leave. It also means they never have a way to defend themselves or represent themselves.
Basically, I want to give people tools to be able to manage their communities. I want them to be able to deal with troublemakers and have whatever tools will be able to do that effectively. This is why I want to make the warning system more granular, so that instead of very broad levels of punishment (watched/moderated/post banned), you can have punishments that suit every level of troublemaker, right up from inappropriate signatures and avatars (temporary/permanent removal of specific privileges) through to inappropriate content (various tools that I don't want to mention yet, heh[nb]I have some... interesting... ideas that I don't want to spoil yet but that will really help with dealing with troublemakers IMO), and generally inappropriate behaviour (moderation, inability to login/browse, i.e. bans)
The other matters, removal of privileges etc. are fairly subtle but ultimately quite 'safe' punitive measures - a user who is subject to them knows that they are subject to them. But a user subject to hellbanning - or, for that matter, the annoy-user measures such as slowbanning[1] or errorbanning[2] - would not know they are subject to them. They can log out and not see these things, and before anyone so much as breathes 'by IP address' (:P) I would remind them that IP addresses are not reliable and that such things will cause people to be punished unnecessarily and unfairly.
Especially if, say, it's applied to a university or workplace range where proxies are in place. Getting another IP address is not a problem for anyone determined enough to really cause havoc anyway.
I'm also aware that this concept is absolutely nothing new, I just want to be sure that if I do implement it, it is with the best of intentions and that I put in safeguards to try and prevent it from being any more abused than it could be; I don't want to wrap admins' hands in kid gloves but I don't want to hand them a loaded gun either. This sort of measure is not a first resort for troublemakers, it is a last resort, and I want the system to reflect that.
Thoughts would be appreciated.
| 1. | Delaying the user's page loads. |
| 2. | Throwing error messages to users. |
2715
Features / Re: $db_passwd and $ssi_db_passwd stored in a .htpasswd-like file
« on October 3rd, 2012, 12:55 AM »I have the function that saves the picture; just need to finagle it and study how wedge submits regular pictures into the gallery, and it might just be crazy enough to work.
Can't remember where I first got it, but with Apache you can set server variables from inside the config file - you can access these from PHP easily enough