ticket	summary	type	release	owner	status	created	modified	_description	_reporter
6340	TracPastePlugin: development strategy	task	0.12		new	2009-12-16T13:15:40+01:00	2017-02-24T05:23:32+01:00	"this is an umbrella ticket to keep track of TracPastePlugin development. i'm thinking major strategy directions would go into simple list in description and all random discussion and thoughts in comments as they come along.

 * layout needs to be much better, textarea too wide, sidebar too narrow.
 * need 0.12 style resizable textarea
 * there is a problem with API-style pastebin POST submit: __FORM_TOKEN -> Noah sez we should use XmlRpcPlugin for everything remote programming, so we need XmlRpc pastebin API interface"	lkraav
5695	Allow pastes to expire	enhancement	0.11	Michael Renzmann	new	2009-08-20T20:31:49+02:00	2020-05-01T06:51:13+02:00	"it would be great if you could allow expiring pastes, e.g. after one month, or 6 month.
"	anonymous
6144	Spam filter integration	enhancement	0.11		new	2009-11-03T07:21:30+01:00	2017-02-24T05:20:03+01:00	"Pastebin should make use of the spamfilter functionality (if available) to prevent spammy pastes from being posted.

See #4029 for the original idea of having a ""turing test"" plus a patch that implements such a feature. However, I agree with [http://trac-hacks.org/ticket/4029#comment:1 osimons] that the approach of that patch is wrong:

''All other plugins that deal with spam implement optional plugins to the trac:SpamFilter plugin, so that if you have that installed then it will also automatically check the entered pastes. That means implementing something like an `IPasteManipulator` interface to allow other plugins to hook into the paste creation and potentially veto the changes. An `IPasteListener` would also be nice while you are at it... :-)''
"	Michael Renzmann
6160	TracPastePlugin: Implement TagsPlugin support	enhancement	0.11		new	2009-11-05T08:27:31+01:00	2020-05-06T02:05:20+02:00	would be nice to be able to tag pastes right? opinions welcome.	lkraav
6348	TracPastePlugin: Implement XML-RPC support	enhancement	0.11	lkraav	new	2009-12-17T23:36:16+01:00	2017-03-18T16:05:17+01:00	basic feature of a pastebin is API posting. [http://groups.google.com/group/trac-users/browse_frm/thread/34e763c124ce6c91/78b4021fae604049?hl=en&tvc=1&q=__FORM_TOKEN#78b4021fae604049 Noah says] POST is out, XML-RPC is in.	lkraav
10121	Add a RecentPastes macro	enhancement	0.11		new	2012-06-25T02:56:31+02:00	2020-05-06T02:05:20+02:00	As originally suggested in [http://trac-hacks.org/ticket/5773#comment:5 comment:5:ticket:5773].	Ryan J Ollos
10223	features from existing paste sites	enhancement	0.12	Michael Renzmann	new	2012-08-03T21:52:52+02:00	2012-08-10T04:59:59+02:00	"I installed TracPastePlugin, checked it out, and concluded I cannot use it yet. Here's my ideas, hopefully they'll be implemented someday. They're mostly security-related, since I expect to share pastes with other people but don't want anyone else to just come in and easily view them all.

 * config to use long randomized paste IDs (currently sequential and easily crawled)
 * config to disable the 'recent pastes' list
 * option to post 'unlisted' paste (won't show in recent pastes and timeline)
 * paste manager, see all pastes and do mass operations
 * configuration section in Admin panel (once you have some config options)
 * paste editing(?) (source code shows that updating a paste is possible internally)"	ultramage
10929	Allow pastes to be edited	enhancement			new	2013-03-12T16:16:21+01:00	2020-05-06T02:05:20+02:00	"It's sometimes useful to be able to edit a paste -- either its title or its contents.  The TracPastePlugin doesn't currently provide this feature.

It would probably make sense to have a separate PASTEBIN_EDIT permission for this, and perhaps (inspired in part by trac:ticket:10909#comment:18) an even finer-grained PASTEBIN_EDIT_OWN permission so that a configuration could allow paste authors to edit their own pastes but no others. "	ejucovy
4265	Paste numbers are being re-used	defect	0.11		new	2008-12-12T14:31:02+01:00	2020-05-01T06:51:13+02:00	"To reproduce:
 * create two new pastes (for example, ID 9 & 10)
 * remove the pastes ID 9 & 10
 * create new paste quickly (before anybody other have chance to create one concurrently)
 * compare old address with the new paste. The new paste will have ID equal 9. Subsequent one will have ID equal 10, and so on.

If you remove one or more last pastes, the new paste to be created will re-use IDs of former pastes. This will lead to people finding completly unrelated pastes under same ID, if the previous one has been deleted and was the highest numbered one.

I'm not entirely sure whether it's abut the most recent paste in sense of time, or the highest numbered one. I guess it's the later.

The problem is probably caused by default SQLite semantics."	dexen.devries@…