Download Reference Manual
The Developer's Library for D
About Wiki Forums Source Search Contact

Ticket #350 (closed wishlist: wontfix)

Opened 1 year ago

Last modified 1 year ago

Security

Reported by: maxter Assigned to: pragma
Priority: minor Milestone: WebSite 1.0
Component: Web frontend Version:
Keywords: Cc:

Description

Disallow casual visitors to create pages for symbol links in the API reference

Change History

03/22/07 10:11:54 changed by larsivi

  • status changed from new to closed.
  • resolution set to invalid.

Actually, this is on purpose. We're thinking that visitors can use them to add annotations, complaints etc. We usually review all edits to the wiki in any case.

As for which pages only select few are allowed to edit, this is marked on a page per page basis (I fixed the one you edited the other day.)

Closing it.

03/22/07 10:12:04 changed by larsivi

  • milestone set to WebSite RC1.

03/22/07 12:09:23 changed by maxter

  • priority changed from major to minor.
  • status changed from closed to reopened.
  • resolution deleted.
  • type changed from defect to wishlist.

Oh, great. But I wouldn't like a casual visitor to freely edit my annotations. And if there are many, you may overlook the changes? Reopening it as wish.

03/22/07 13:03:35 changed by larsivi

  • status changed from reopened to closed.
  • resolution set to wontfix.

Well, only users registered at dsource are allowed to edit, which restricts quite a bit already. The problem as I see it (I'm usually the one who take care of the edits), is that you don't know who want to annotate, and I don't want to require them to ask permission, since that may be more of an effort than what it's worth, just see Wikipedia at large. The change log will in any case be there if someone should be mean.

If malicious changes should become a problem (so far you're the first ;), then I will consider changing the permission setup (I have given it quite a bit of thought already). As for annotations that are coming in - we may need an improved organization in any case (and many comments should probably be integrated in the API docs themselves) - which may involve a writeprotected page (approved annotations so to speak).

Closing again :) (Note that any more granularity in the permission system will be hard to handle in the current Trac, and more than I wish to administer.)

03/22/07 14:04:02 changed by maxter

I agree. Thanks for your time.