User:Ilya/OpenWetWare/Todo

Open

• install openldap
• follow up openwetware hostname alias transfer to model (https://help.mit.edu/SelfService/)
• Add vhost directives to Apache logs to distinguish traffic among the sites
• Eventum
• RSS feeds in wiki extension
  • add feed extensions to User:Ilya/OpenWetWare/Feeds
  • feature requested: formatting of feeds (Magpie?)
• Embed PHPBB
• Disable mail delivery to foreign addresses from non-local senders
• Semantic mediawiki - installed on test (see Austin's email for details)
• Move pheromone wiki to rackspace server:
  • user accounts - openid
  • delete spammers' user accounts
  • <Googlesearchheader>
• try Drupal, see CMS
• try Pligg - an open source social networking content management system (CMS). It combines social bookmarking, bloggin, syndication and a democratic editorial system that enables users to collaboratively submit and promote articles
• stop rotation of OWW access logs (make a script to archive the logs before they are rotated?)
• enable rsync over SSH for off-site backups
• stop sending bounces to return address provided by spammers (accept only outside mail for local delivery and only local mail for outside delivery?)
• graph of page links on the wiki

DOI

• The DOI system was established to provide persistent identifiers for digital content because URLs were "never meant to be an identifier but only to designate the location of objects" (http://www.press.umich.edu/jep/04-02/davidson.html). In other words, DOIs were designed to be generic enough so that they could be used on top of any system, including but not limited to DNS/Internet. The DOI system provides a level of indirection between the identifier and the object it identifies. This is very useful for keeping URLs current - when location of an object changes, you just need to update the URL associated with the object's DOI.

• Besides resolution services, the DOI proxies/resolvers (which are operated by the Registration Agencies and are currently web-based) also maintain some structured metadata (like author, date, title, etc) for every object. This is useful for more efficient searching, for example.

• To obtain the real DOIs for OWW content, we'd need to register each DOI with a DOI Registration Agency. This apparently requires an yearly fee (just like the Internet domain registration fee) and possibly, a one-time fee for the DOI prefix (http://www.medra.org/en/terms.htm, http://www.crossref.org/02publishers/20pub_fees.html).

• To be confirmed. DNS is hierarchical: one needs only to register a domain name and then can have unlimited number of subdomains. DOI systems is flat, so each DOI (suffix) needs to be registered with the system, even if one owns a prefix.

Blogs

• Problem: new blog notifications are sent to you@example.com. For example:

New blog created by admin\n\nAddress: http://blog.openwetware.org/outsidethebox/\nName: Outside The Box

Solved

Line terminator in email

Diagnostic-Code: X-Postfix; host uk-lif-lwmx02.cancer.org.uk[193.60.34.72]
   said: 550 Requested action not taken: Nonstandard SMTP line terminator. (in reply to end of DATA command)

• It looks like some servers have problem accepting mail from OWW UMS. According to this thread, it has something to do with the line endings.
• try changing all the \r\n in um_functions.php to \n
• On a UNIX system the MTA's "sendmail" interface assumes that recieved data will use UNIX line endings and will turn any \n to \r\n, so you must supply only \n to mail() on a UNIX system to avoid the MTA hypercorrecting to \r\r\n.
• References:
  • http://us.php.net/mail
  • http://www.ietf.org/rfc/rfc822.txt