Sean Robinson | 25 Jul 00:24
Picon

wiki farmURL fixes

  While trying to make a local wiki farm, I discovered that the URL-generating methods do not honor config.httpd_port.  The attached patches fix this for getBaseFarmURL() and getWikiURL() so that one can run Sycamore on ports other that 80 or 443.

--
Sean Robinson
WiFi Radar - http://wifi-radar.berlios.de
Python WiFi - http://pythonwifi.wikispot.org

Sean Robinson | 16 Jul 02:03
Picon

Re: URL blacklist

On Sat, Jul 10, 2010 at 4:01 PM, Ryan Tucker <rtucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
On Sat, Jul 10, 2010 at 5:06 PM, Sean Robinson <seankrobinson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>   After looking at blacklist.py (but not running it), it appears that the list of restricted URLs are hard coded into the source file.  Is anyone interested in making this use a wiki page for the list of URLs?

If someone's looking for inspiration on how to retrieve the list from
a wiki page, the spell-checking code does this.  There's probably some
good room for code reuse (or modularization!) there, for sure.  -rt


  The following is an attempt at a new blacklist.py.  I am seeking comments and criticism to see if I understood what I was reading in the spell check code and whether I am using PageEditor correctly, etc.  This is an early draft of non-working code, but I would appreciate feedback about my approach.

# -*- coding: utf-8 -*-
# blacklist against wiki spammers

# WikiSpot admins can add a URL to 'Global Blacklist Page' to disallow an
# edit which contains that URL.

import re, types
from Sycamore import config
from Sycamore.PageEditor import PageEditor
from Sycamore.request import RequestDummy
from Sycamore.security import Permissions

# get the global blacklist page contents
request = RequestDummy()
blacklist_page = PageEditor(config.global_blacklist_page, request)
if blacklist_page:
    blacklist = blacklist_page.get_raw_body()
    self.blacklist_re = "|".join(map(lambda s: "%s" % s.strip(), blacklist.strip().split("\n")))
    self.blacklist_re = re.compile(self.blacklist_re)

class SecurityPolicy(Permissions):
    def save(self, editor, newtext, datestamp, **kw):
        match = blacklist_re.search(newtext)
        if match:
            print "blacklist match: %s" % match.group()
        return match == None


--
Sean Robinson
WiFi Radar - http://wifi-radar.berlios.de
Python WiFi - http://pythonwifi.wikispot.org

William Lewis | 6 Jul 20:07
Picon

URL blacklist

How difficult would it be to create a URL blacklist? It's getting ridiculous dealing with the same spammers
coming and posting the same links over and over again.
Ryan Tucker | 12 Apr 04:29
Picon
Gravatar

A proposal for a new comments system

Greetings!

On RocWiki, comments have been a contentious feature.  We aim for a
factual and neutral point-of-view for the "main" content on a page, with
opinions and whatnot kept to the comments.  This works fairly well, but
the current implementation limits flexibility and makes comments a
target for abuse.  I am proposing a new system that separates the
comments from the main page content, solving some of these issues and
allowing for flexibility to add features in the future.

The current Comments macro functions by appending the user's comment to
the bottom of the page.  This is simple and works pretty well, as long
as some rules are respected:

 * Don't edit other people's comments
 * Don't delete other people's comments
 * Don't mess with the formatting

These three rules run directly counter to the normal wiki instincts, yet
are essential to the use of comments for open discourse.  Unfortunately,
these rules are not always respected, and when they aren't, all hell
breaks loose.  We've also had issues with very heavily-commented pages:
new comments get added to the bottom, which is a long ways from the top.

I believe the best long-term solution to this is to separate the
comments from the editable page content.  I propose to do this by
creating a database table to store comments, with the comments.py macro
responsible for outputting the comments during page rendering.

This system should initially support the following:

 * Seamless transition from current system, including importing of
existing comments
 * The ability for users to delete and edit their own comments
 * The ability for admins to delete and edit other user's comments
 * The ability for users to delete comments from their own user page
 * Sorting displayed comments newest-to-oldest
 * Comments should still appear in the Recent Changes page as usual

In the future, I envision the system perhaps supporting:

 * RSS feeds for comments (for example, a feed of all comments across
the site)
 * Threads: being able to reply to a comment and having your comment
linked to the original
 * Comment voting: users can vote up/vote down other comments
 * Page voting: along with a comment, including one to five "stars",
e.g. for restaurant "review"-like stuff

In some ways, my model for this is reddit.com's comment system, although
probably nothing that fancy will occur.

I plan to start work on this in the near future, and am wondering if
other folks are interested in something like this and/or if there's any
feedback or suggestions.  If so, some collaboration could surely ensue.

Thanks!  -rt

--

-- 
Ryan Tucker <rtucker@...>
Sean Robinson | 31 Jan 00:21
Picon

google webmaster tools start

  Attached is a zip archive of three patches which I hope add admin-only permission to create and edit .html and .htm page names.  My intent is that can this be used to add pages of the required name for Google Webmaster Tools.

  I have not tested this change.  I have only spent minimal time looking at the Sycamore code.  And my whole concept for implementing this may be hopelessly naive.  But, I hope to start the conversation and I am willing to work more on this problem if the devs are able and willing to work with me.

--
Sean Robinson
WiFi Radar - http://wifi-radar.berlios.de
Python WiFi - http://pythonwifi.wikispot.org

Attachment (sycamore-gwt-sr-patches.zip): application/zip, 2452 bytes
Ryan Tucker | 1 Jul 13:27
Picon
Gravatar

Sycamore SVN (unofficially and experimentally) cloned onto github

In a cold sweat last evening, I realized it was the end of the quarter,
and the odds of devjavu being gone this particular morning were
therefore somewhat higher than usual.  (It's still around this morning,
phew)

So, I used a svn2git tool to import the sycamore SVN into git overnight,
and then pushed it to github so it's not just on my computer:

http://github.com/rtucker/sycamore/tree

No endorsement of git, github, or myself is being made by this; I just
wanted to make sure things didn't go poof overnight.  :-)  Feel free to
use this to play around with git/github.  However, the SVN is still the
final authority so don't use this for real development/deployment.  -rt

--

-- 
Ryan Tucker <rtucker@...>
Philip Neustrom | 27 May 22:04
Picon
Gravatar

Re: Fwd: Important Notice: DevjaVu is going to be shutting down

I'm in love with my own weird and imperfect dvcs, darcs.  But git has really won the mindshare game and it's the least unfamiliar to folks.

On May 27, 2009 9:26 AM, "Michael Ivanov" <mivanov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

Assembla offers hosted source control using SVN or Git or Mercurial as well as Trac or their own ticketing system, and a bunch of other little extras.  It's free for public open source projects, and really easy to set up the modules you need.  I've been using them for a few months for personal stuff and have had a decent experience.

http://www.assembla.com/

Mike

On Wed, May 27, 2009 at 9:04 AM, Paul <pivanov-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote: > > I'm glad that DVCS is back...


_______________________________________________
Sycamore-Dev mailing list
sycamore-dev-R5Z0CYfGwkJg9hUCZPvPmw@public.gmane.org
http://www.projectsycamore.org/
https://tools.cernio.com/pipermail/sycamore-dev/
https://tools.cernio.com/mailman/listinfo/sycamore-dev

Philip Neustrom | 3 May 08:13
Picon
Gravatar

Fwd: Important Notice: DevjaVu is going to be shutting down

We'll have to set up Trac / SVN soon

---------- Forwarded message ----------
From: "DevjaVu Team" <jeff-u6n3aiYOcNNBDgjK7y7TUQ@public.gmane.org>
Date: May 2, 2009 6:09 PM
Subject: Important Notice: DevjaVu is going to be shutting down
To: "philipn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <philipn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Hello everyone,

You're getting this message because you have a project at
DevjaVu and we have a very important notice about the service.

Over the next few months, DevjaVu will be winding down and
eventually shutting down. We'll try to hold on as long as
possible, but we don't have the money to run more than a few
months unless we work something out with Engine Yard (perhaps
go down to one slice). We highly recommend you start migrating
off as soon as possible. A more concrete end of service date
will be announced soon on our blog: http://blog.devjavu.com

You have full access to your SVN repo and Trac instance in the
Admin under Export. If your repository is too big to export, we
can do the export for you and give you a link to download. Just
contact support-u6n3aiYOcNNBDgjK7y7TUQ@public.gmane.org if that's the case. If worse comes
to worse and we do have to shut down before everybody is off,
we'll give plenty of warning and then provide downloadable
exports of everybody's projects linked in an email to the
project owner once the service is off.

This is the first time I've had to do anything like this, so
if you have any feedback on handling this in a better way, let
me know. I'd love to give a detailed explanation of what's
going on, but I think I'm going to hold off until the final day.
In short: the business never got the momentum I wanted to
sustain my personal interest, so while running at break-even
worked so-so for so long, it finally started dying and has been
losing money for a while. I started an effort to save it, but
I decided I did not want to continue supporting this type of
service, especially by myself.

So, sorry everybody! I would have liked this to be less of a
surprise than I'm sure it is for some of you. Yes, it certainly
could have been avoided if I better communicated with you guys
up to this point. But I want to thank you for using DevjaVu
while you did.

If you have questions or concerns, email me at jeff-u6n3aiYOcNNBDgjK7y7TUQ@public.gmane.org

Jeff Lindsay
DevjaVu

This email was sent to philipn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org.
You can instantly unsubscribe from these emails by clicking the link below:
http://devjavu.cmail4.com/t/y/u/htdttt/dtdkjruhu/

Arlen Abraham | 25 Apr 00:28
Picon

Re: Real Names

Would this be an optional describive box that is turned on/off/customized by the admins?

--a

On Apr 24, 2009 3:14 PM, "Philip Neustrom" <philipn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

Yeah, I like the idea of a descriptive box rather than a username check.

-p

On Fri, Apr 24, 2009 at 3:01 PM, Brent Laabs <bslaabs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > It's feasible with the cu...

Alex Mandel | 22 Apr 00:42

Real Names

Seems like a fair number of people, especially on new wikis seem to pass
over the whole, we recommend you use your real name. I'm wondering if we
should add a check or 2 on the registration process that looks for odd
things like numbers in the name, and prompts. "This doesn't appear to be
your real name, real name's are important ....are you sure you want to
use this name, checkbox."

It's been so long, I actually don't really remember what the
registration process says, guess I should look it up on me dev box.

What do people think?
Alex
Philip Neustrom | 1 Apr 06:34
Picon
Gravatar

Trac/SVN down

See http://blog.devjavu.com/2009/04/01/more-upstream-problems-today/

Should be up again soon.

Gmane