Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Slashcode 1.0.6 Released

posted by CaptTofu on 12:42 PM July 11th, 2000   Printer-friendly   Email story
Slashcode 1.0.6 has been released and is available in all the usual places. It has more enhancements and bug fixes (see CHANGES). We will now be focusing primarily on the development branch, Bender. There's a lot that we want to do with the code that will be more feasible to accomplish in the development branch.
CHANGES:
slash-1.0.6, 2000.07.10
-----------------------

*	Don't let BLOCKQUOTEs nest more than 4 in comments.pl (same
	as UL and OL)

*	Added Bundle::CPAN to Bundle::Slash (see INSTALL)

*	Don't let users edit authors without seclev >= 500 (ttyp0)

*	Fix for all TEXTAREA sections, converting all  and &
	characters to HTML entities

*	Add text next to "moderate" button to warn authors that
	checkbox is for deleting comments

*	Change redirect code to use URI->new_abs->canonical
	(still use old method if $rootdir eq '')

*	Fixed bug in search.pl where users could not click back to
	the first page of results using the "xx previous matches"
	link (Joris Trooster)

*	When performing a user search using search.pl, it will also
	check the fakeemail field, in addition to the nickname

*	Fix to allow "%" and "#" in URLs for Slash::fixurl()

*	No longer show comments to regular users in submit.pl

*	Disallow most characters from nicknames in users.pl

*	Add session-based cookies for Anonymous Coward for use
	with formkeys in submission and comment posting forms
	in Slash.pm, comments.pl

*	Slash::setCookie() can be called with an addition boolean
	parameter to set temporary, session-based cookies

*	Fixed bug that allowed users to moderate a single comment more
	than once

*	Submission titles are now shown on the browser's titlebar

*	Section articles appearing on the main index now also have a
	link to the section's home page by the "Read More" link
	(Russ Nelson)

*	Fixed bug where authors could moderate if they were logged in as
	authors, but not logged in as a registered user

*	Added 'active' field to moderatorlog (yes, it probably
	could have been called something better) to track which
	moderation attempts actually succeed. Done mainly due to the
	fact that there are some situations where we may want to make
	certain moderations that don't get applied still applicable to
	M2 review. comments.pl and article.pl have been made aware of
	this new field

*	Metamoderation results are now counted. The number of times a
	user's moderation is voted fair or unfair is now counted in
	users_info (columns m2fair and m2unfair)

*	Fixed small bug in admin.pl which would result in bugs while
	saving and editing topics if $I{basedir} was not derived from
	$I{datadir} (i.e., if the 2 directories were on different
	partitions)

*	If there were no images in the topic images directory, the topic
	editor would display a select list with no items. Now, a warning
	is displayed and the user is given an input box filled with the
	current filename

*	Hit counting has been disabled (again) in search.pl due to
	problems with httpd stability. Aparently precounting results,
	even on fast servers will cause a huge load on MySQL which then
	flakes out the httpds. Will be analysing this to see if a
	solution can be found. Until then, we will only count the
	number of matches we've encountered and the bottom link will
	say "More matches..." as opposed to "x more matches"

*	More counts added for M2, now in addition to counting the
	number of times a user is voted fair or unfair, we also count
	the times a user VOTES fair or unfair. The last pair of numbers
	can be used to determine if your Slash metamoderation system is
	being abused. (This adds 2 new columns to users_info:
	m2fairvotes and m2unfairvotes)

*	Changes to the moderation system, these can be summed up by
	describing the following new variables added to slashdotrc.pl:

		m2_maxunfair: Float from 0 to 1. This number determines
			the percentage of unfair votes that indicates
			abuse. The user performing M2 will quietly be
			assessed a karma penalty and their votes will
			be ignored if their percentage of unfair votes
			equals or exceeds this value.

		m2_toomanyunfair: Float from 0 to 1. This number
			determines the percentage of unfair votes that
			indicates POSSIBLE abuse of the system. If the
			percentage of unfair votes exceeds this value
			then these votes are ignored. No penalty is
			assessed.

		m2_mincheck: Integer. Number of comments which have to
			be voted on before the above checks are
			performed.

		m2_comments: Number of comment moderations to be
			displayed in a single M2 session.

		m2_bonus: Amount of karma to be awarded upon completion
			of M2.

		m2_penalty: Amount of karma to be subtracted if M2 is
			abused.

		m2_maxbonus: Karma maximum from M2. If a user's karma
			exceeds this value, then said user receives no
			further bonus or his participation.

*	Added the 'flag' column in metamodlog; this indicates how an M2
	session was treated and is a good way to check for possible M2
	problems. Currently flag can be the following values:
        	0 - No detected problems with M2
        	1 - Questionable M2. Votes ignored
        	2 - Abuse of M2. Votes ignored and UID penalized

*	Renamed slashdotrc.pl variables:
	        'goodkarma_limit' is now 'goodkarma'
        	'badkarma_limit' is now 'badkarma'

*	User's ID (UID) added to comment headers

*	Names of the comment poster have been removed during
	metamoderation

*	Fixed a minor bug in metamod.pl that inadvertantly stopped the
	injection of new eligible users into the metamoderation pool

*	Added " ... " to .rdf file, and added encoding
	of "ISO-8859-1" (will later be configurable) in slashd
	(Roger Carneiro Soares)
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • by Anonymous Coward
    I guess that's to put a dent in the posers, but I don't think I like the results as seen the past few days on slashdot. I'm willing to give the idea a few days; I just hope nobody's wedded to it.

    -- slashdot user #6908, evidently much more elite than them other 200k+ folks.

  • Vladinator wrote: I thought Slashdot didn't delete comments? Am I missing something?

    Slashdot may not delete comments, but that little check box still shows up next to every comment. And, if you're uncertain of what that box does, it's rather easy to delete a comment. Unfortunately, I learned this the hard way, when in the first few days of MacSlash, Pudge visited and posted a comment about Slashcode development work being partially done on the Mac. I was eager to show everyone how cool this was and clicked that checkbox, moderated it to insightful, and was horrified to find that the comment dissappeared.

    Because of that horror story, and others that I've heard from many people, I'm very glad that the check box now comes with a warning. From a usability standpoint, it's a great improvement.

    --
    Ben Stanfield
    Executive Editor, MacSlash
    http://www.MacSlash.com [macslash.com]

    --

    --
    Ben Stanfield
    Executive Editor, MacSlash

  • Go to this site's home page. Click on the prominent "Download" link. Or go to this site's FAQ, and read the entry about downloading the code.
  • by Anonymous Coward
    I'm new, where is "..available in all the usual places." ?
  • But why do we need this one:

    * Add text next to "moderate" button to warn authors that checkbox is for deleting comments

    I thought Slashdot didn't delete comments? Am I missing something?
    --


    "How about you interface with my ass? By biting it!" --Bender
  • Shouldn't moderation be done by plain old regular users?

    Shouldn't that be up to the site administrators?

    Why do authors get to moderate?

    I don't care why. If the site administrators wants to let them, then he will. It is not our job as authors of Slash to decide site policy for the users of Slash.

    Do they get to moderate comments to their own stories?

    If the site administrators let them, yes.

    If this is the site about the code that Slashdot runs on, where's the site about the code that this site runs on?

    It uses the exact same code as Slashdot. Please read the FAQ [slashcode.com] for the question "Is this the same code that runs Slashdot?".

  • I thought Slashdot didn't delete comments?

    I don't know, did you? :-)

    Am I missing something?

    I don't know. You noted that there is functionality for deleting comments, and you wondered if you thought that Slashdot didn't delete comments. What are you wondering if you missed? Perhaps you are under the mistaken impression that Slashdot uses all the fatures in Slash.

  • please tell me that you're not asking this.
  • Try Here [slashdot.org].
    --


    "How about you interface with my ass? By biting it!" --Bender
  • "Fixed bug where authors could moderate if they were logged in as authors, but not logged in as a registered user"

    Shouldn't moderation be done by plain old regular users? Why do authors get to moderate? Do they get to moderate comments to their own stories?

    If this is the site about the code that Slashdot runs on, where's the site about the code that this site runs on?

    --

    If this is the site about the code that Slashdot runs on, where's the site about the code that this site runs on?