On Wed, Jan 26, 2005 at 12:57:28PM -0500, IvorW wrote:
> I'm sorry I can't be around for the hackfest. I'll try and recall and
> braindump the ideas I have had to the list between now and then.
>
> Good festing and good hacking all.
Did I miss something actually being organised?
--
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
> -----Original Message-----
> From: openguides-dev-bounces(a)openguides.org
> [mailto:openguides-dev-bounces@openguides.org]On Behalf Of Kake L Pugh
> Sent: 24 January 2005 18:14
> To: OpenGuides software developers
> Subject: Re: [OpenGuides-Dev] encoding troubles
[snip...]
> I am still poking at this issue, having got distracted by the one
> below, which I think is related but not the same.
>
> Note that the page you get redirected to on a saved edit is wrong, being
> http://vienna.openguides.org/vienna.cgi?Category_CD/Platten-Gesch%C3%A4fte
> instead of
> http://vienna.openguides.org/vienna.cgi?Category_CD/Platten-Gesch%E4fte
>
> This is because the node name parameter is not being properly URL-encoded
> before the Location: header is printed to STDOUT. This bug slipped in
> because I forgot that CGI::Wiki::Formatter::UseMod's ->node_name_to_node_param
> method doesn't actually URL-encode, but expects you to do it yourself
> after calling the method (this _is_ documented).
> I think it perhaps should, since what I expect from that method is
> something I can bung into a URL and it will Just Work. However
> changing it to do that would break backwards compatibility and could
> lead to things being doubly-encoded, which would suck. Thoughts? I
> may punt this to cgi-wiki-dev as well.
I wonder whether this might be the time to revisit node_name_to_node_param
and provide something more flexible. I have in mind something inwardly
pluggable that supplies a normalisation function for node names.
Currently, n_n_t_n_p reduces multiple whitespace to a single space, replaces
spaces with underscores and adds Title Case. There is no reason why this
could not apply de-accenting of letters or turning umlauts into diphthongs.
I think that there is a strong case for this being a plugin.
Also, this could provide a solution to some of the King's_cross_st_pancras
problem (I originally raised this as an issue with search, but it could
equally be thought of as a node name munging issue).
see http://openguides.org/mail/openguides-dev/2003-October/000091.html
I'm sorry I can't be around for the hackfest. I'll try and recall and braindump
the ideas I have had to the list between now and then.
Good festing and good hacking all.
Ivor.
hello,
i saw in the readme that there are utf8 bugs around.
our webserver doesn't deliver utf8, so i changed the encoding to
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
vienna.og has troubles with non-ascii chars in categories:
http://vienna.openguides.org/vienna.cgi?Category_CD/Platten-Gesch%E4fte
abovesis not beeing recognized as Category,
nor is one beeing able to see the pages of that cat.
should ask domm what encoding the postgresql database uses,
maybe that disturbs too.
--
maks
So today I was reading the page on the dev wiki about Greylisting
(http://openguides.org//dev/?node=Wiki%20Greylisting) and it's a fairly
straight forward and a kinda nice idea to avoid the anti-wiki like idea of
requiring user logins for submissions. However there is one minor change that
I'd like to add.
After an IP address has a post moderated and accepted the first time that IP
address is then whitelisted for a time, meaning any of their further posts
are automatically accepted for a period of time. This will reduce the amount
of admin intervention required.
Possible drawbacks I've thought of so far:
* Dynamic IP address change after unknown periods of times. Initially I was
thinking the whitelist period could be measured in months, but now I suspect
it should be days or possibly hours on a very active guide.
* It won't block a spammer from making a useful edit to gain whitelist access
then using that elevated status to wreak havoc. But then that would be a
fairly dedicated spammer, and their IP address would be blacklisted very
quickly.
* There is a question of which user is whitelisted in the case of multiple
edits (Bob edits FooNode, Alice edits FooNode, AdminHex moderates Alice's
merge with Bob ... who's IP address is whitelisted? Alice? Bob? Both?) I
suggest that it's only Alice's, but this could be configurable.
I'm sure there are drawbacks I haven't thought of. Suggestions?
-Chris
This one time, at band camp, IvorW wrote:
> My thoughts about this are to have a new type of node called a route.
> Such nodes contain a list of (x,y) or (lat,long) pairs tracing a route.
> These are joined together by straight lines when displaying on SVG or suchlike.
Sounds similar to an idea I had for when you're going on a journey and
want to find all the stuff that is within a range of your route.
Ideally upload your MS Autoroute or GPS route waypoints?
This idea would be great for my site. Geek goes on holiday with
non-geeks and non-geek agenda. Geek puts in route to find where the
group's plan can be merged with some geek sites to see :)
--
Rev Simon Rumble <simon(a)rumble.net>
www.rumble.net
The Tourist Engineer
Geeks need vacations too.
http://engineer.openguides.org/
"To retain respect for sausages and laws, one must not
watch them in the making."
- Otto von Bismarck
Dear Openguides Team,
The category "Digital Communities", which met with great interest and participation in 2004, will be awarded again by Prix Ars Electronica in 2005. As you had been participating last year, we would kindly like to invite you and your team to submit your project "http://openguides.org/" - or a new project - in the category "Digital Communities" of this year's Prix Ars Electronica.
The Digital Communities category of Prix Ars Electronica encompasses digital community projects as well as developments in the field of social software, mobile communications or wireless networks. For a detailed description of the category and about Prix Ars Electronica in general, please see our website:
<http://www.aec.at/en/prix/communities/communities.asp>
Prizes
One Golden Nica with 10,000 Euro and two Awards of Distinction with 5,000 Euro each will be awarded and up to 12 Honorary Mentions made by the jury.
The registration starts January 10, 2005.
The deadline for submissions is March 11, 2005.
Please use
<http://www.aec.at/en/prix/registration/index.asp>
for your submission and to obtain further details.
If you need any further information or help, please do not hesitate to contact us.
Looking forward to your participation!
Sincerely yours,
> Ingrid Fischer-Schreiber
> Prix Ars Electronica 2005
>
> AEC Ars Electronica Center Linz
> Museumsgesellschaft mbH
> Hauptstraße 2
> A-4040 Linz
>
> Tel. ++43.664.8126230
> Fax ++43.732.7272-674
> communities(a)prixars.aec.at
> http://prixars.aec.at
>
>
Dom asked me on IRC yesterday about the code that generates the OGL node
statistics (http://london.openguides.org/statistics/). I've now modulized
it. Please test this:
http://downlode.org/tmp/Openguides-Statistics-1.tar.gz
I've not been able to test it against any databases other than the current
London one (PgSQL), so I have no idea if it will work for others, although
I've tried to write it so that it will. I also only have some very basic
tests for it because I don't know how to write tests for something that
relies on a database.
Cheers,
Earle.
--
Earle Martin
http://downlode.org/http://purl.oclc.org/net/earlemartin/
OpenGuides 0.47 has been released, with minor updates. It is available
from your favourite CPAN mirror, or
http://www.larted.org.uk/~dom/computing/code/openguides/OpenGuides-0.47.tar…
or, indeed, http://www.larted.org.uk/~dom/debian/openguides/.
md5sum:
414f612f0bd5b8542c2230c17309db1c OpenGuides-0.47.tar.gz
(files in this distribution are also signed with cpansign; run
"cpansign -v" to verify.)
Changelog:
Fixed bug with list_all_versions for nodes with only one version.
Extended config changes to examples/reindex.pl (thanks jimbo).
Now require CGI::Wiki 0.62 to fix bug with deleting versions.
Try to ensure that a .htaccess file protecting wiki.conf is installed.
Allow for external URLs for Text Formatting help.
Home node recent changes box now flags new entries.
Made default city and country be blank; specify them if you want them.
Missing PREREQUISITE on Plucene added.
Added CSS id "maincontent" to exclude the navbar and footer. Misc
template tidying including removing old layout tables.
Dominic.