From morgan at morgansutherland.net  Wed Feb  4 12:57:08 2009
From: morgan at morgansutherland.net (Morgan Sutherland)
Date: Wed, 4 Feb 2009 12:57:08 -0500
Subject: [Instiki] instiki moved to a new host, rails 2.2 and passenger,
	all previous spam removed
In-Reply-To: <E851080B-72A2-438A-9AA7-5334B308C14F@gmail.com>
References: <E851080B-72A2-438A-9AA7-5334B308C14F@gmail.com>
Message-ID: <9b850fd0902040957v3add3485o49dbef55d4c03ea7@mail.gmail.com>

Hello,

How did you go about deleting spam messages?

On Mon, Jan 26, 2009 at 7:37 AM, Matthias Tarasiewicz <parasew at gmail.com> wrote:
> We moved the main instiki site to a new, faster hosting. We also set up
> apache with passenger to serve the site faster.
> We also deleted all the spam pages that were created in the past, so the
> site is slim and slick again.
>
> expect some further updates and a new version soon.
>
> -parasew
> _______________________________________________
> Instiki-users mailing list
> Instiki-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/instiki-users
>

From parasew at gmail.com  Wed Feb  4 21:33:18 2009
From: parasew at gmail.com (Matthias Tarasiewicz)
Date: Thu, 5 Feb 2009 03:33:18 +0100
Subject: [Instiki] instiki moved to a new host, rails 2.2 and passenger,
	all previous spam removed
In-Reply-To: <9b850fd0902040957v3add3485o49dbef55d4c03ea7@mail.gmail.com>
References: <E851080B-72A2-438A-9AA7-5334B308C14F@gmail.com>
	<9b850fd0902040957v3add3485o49dbef55d4c03ea7@mail.gmail.com>
Message-ID: <012739B2-1786-4F9E-B97B-48A800A673DD@gmail.com>

On 04.02.2009, at 18:57, Morgan Sutherland wrote:

> How did you go about deleting spam messages?


we manually deleted the existing spam messages in the database, since  
the db grew too big and the export would take too long.

if somebody tries to redo this manually, keep the following in mind:
the data in the db is connected/linked, so when deleting rows from  
tables, make sure to not destroy the database integrity. the best  
approach to deal with the data is via the script/console.

backup your database before interacting with the data!

1. invoke with 'ruby script/console production' in the instiki root
2. get the page you want to alter

 >> mypage=Page.find_by_name('HomePage')

3. check how much revisions you've got

 >> mypage.revisions.count
=> 202

4. either delete all the versions but one (leave at least one  
revision! else your data integrity is gone!)

 >> mypage.revisions.each {|r| mypage.revisions.reload; r.destroy if  
mypage.revisions.count.to_i>1}
 >> mypage.revisions.reload
 >> mypage.revisions.count
=> 1

(keep in mind that on the website, the changes might be not visible  
immediately because of caching. delete everything in /cache to get the  
site to rebuild.

if you accidentally deleted all the revisions of your page and get  
error 500's:

 >> mypage=Page.find_by_name('HomePage')
 >>  
mypage 
.revisions 
.create 
(:revised_at=>Time.now,:author=>Author.new('console','127.0.0.1'))
 >> mypage.save!
=> true

5. selectively delete revisions:

# delete all revisions systemwide that contain the word "v1agra"
 >> Page.find(:all).each {|p| p.revisions.each {|r| r.destroy if  
r.content.include? "V1agra" }}

# delete all revisions systemwide that from the ip 55.55.55.55
 >> Page.find(:all).each {|p| p.revisions.each{|r| r.destroy if  
r.ip=="55.55.55.55" }}



# make sure that you don't have any pages without revisions afterwards

# either restore empty revisions
 >> Page.find(:all).each {|p|  
p 
.revisions 
.create 
(:revised_at=>Time.now,:author=>Author.new('console','127.0.0.1')) if  
p.revisions.size == 0}

# or also delete the corresponding Pages without revisions
 >> Page.find(:all).each {|p| p.destroy if p.revisions.size == 0}



in the next version of instiki there will be a "delete" functionality,  
but i am thinking of also implementing a delete-option for versions  
(revisions) soon, since databases can grow huge if there are lots of  
rollbacks.

another idea would be something like an "administrative rollback" or  
"hard rollback" that deletes all previous versions between the current  
entry and the to-be-rolled-back entry, anyone interested in such a  
functionality?

-m

From morgan at morgansutherland.net  Thu Feb  5 17:29:18 2009
From: morgan at morgansutherland.net (Morgan Sutherland)
Date: Thu, 5 Feb 2009 17:29:18 -0500
Subject: [Instiki] instiki moved to a new host, rails 2.2 and passenger,
	all previous spam removed
In-Reply-To: <012739B2-1786-4F9E-B97B-48A800A673DD@gmail.com>
References: <E851080B-72A2-438A-9AA7-5334B308C14F@gmail.com>
	<9b850fd0902040957v3add3485o49dbef55d4c03ea7@mail.gmail.com>
	<012739B2-1786-4F9E-B97B-48A800A673DD@gmail.com>
Message-ID: <9b850fd0902051429hb4981bu7aa16128a51d5ea5@mail.gmail.com>

I'm very glad to hear that you're planning to implement deletion! And
the ability to delete revisions would be convenient.

Thanks for your help.

On Wed, Feb 4, 2009 at 9:33 PM, Matthias Tarasiewicz <parasew at gmail.com> wrote:
> On 04.02.2009, at 18:57, Morgan Sutherland wrote:
>
>> How did you go about deleting spam messages?
>
>
> we manually deleted the existing spam messages in the database, since the db
> grew too big and the export would take too long.
>
> if somebody tries to redo this manually, keep the following in mind:
> the data in the db is connected/linked, so when deleting rows from tables,
> make sure to not destroy the database integrity. the best approach to deal
> with the data is via the script/console.
>
> backup your database before interacting with the data!
>
> 1. invoke with 'ruby script/console production' in the instiki root
> 2. get the page you want to alter
>
>>> mypage=Page.find_by_name('HomePage')
>
> 3. check how much revisions you've got
>
>>> mypage.revisions.count
> => 202
>
> 4. either delete all the versions but one (leave at least one revision! else
> your data integrity is gone!)
>
>>> mypage.revisions.each {|r| mypage.revisions.reload; r.destroy if
>>> mypage.revisions.count.to_i>1}
>>> mypage.revisions.reload
>>> mypage.revisions.count
> => 1
>
> (keep in mind that on the website, the changes might be not visible
> immediately because of caching. delete everything in /cache to get the site
> to rebuild.
>
> if you accidentally deleted all the revisions of your page and get error
> 500's:
>
>>> mypage=Page.find_by_name('HomePage')
>>>
>>> mypage.revisions.create(:revised_at=>Time.now,:author=>Author.new('console','127.0.0.1'))
>>> mypage.save!
> => true
>
> 5. selectively delete revisions:
>
> # delete all revisions systemwide that contain the word "v1agra"
>>> Page.find(:all).each {|p| p.revisions.each {|r| r.destroy if
>>> r.content.include? "V1agra" }}
>
> # delete all revisions systemwide that from the ip 55.55.55.55
>>> Page.find(:all).each {|p| p.revisions.each{|r| r.destroy if
>>> r.ip=="55.55.55.55" }}
>
>
>
> # make sure that you don't have any pages without revisions afterwards
>
> # either restore empty revisions
>>> Page.find(:all).each {|p|
>>> p.revisions.create(:revised_at=>Time.now,:author=>Author.new('console','127.0.0.1'))
>>> if p.revisions.size == 0}
>
> # or also delete the corresponding Pages without revisions
>>> Page.find(:all).each {|p| p.destroy if p.revisions.size == 0}
>
>
>
> in the next version of instiki there will be a "delete" functionality, but i
> am thinking of also implementing a delete-option for versions (revisions)
> soon, since databases can grow huge if there are lots of rollbacks.
>
> another idea would be something like an "administrative rollback" or "hard
> rollback" that deletes all previous versions between the current entry and
> the to-be-rolled-back entry, anyone interested in such a functionality?
>
> -m
> _______________________________________________
> Instiki-users mailing list
> Instiki-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/instiki-users
>

From parasew at 5uper.net  Thu Feb 19 16:01:56 2009
From: parasew at 5uper.net (Matthias Tarasiewicz)
Date: Thu, 19 Feb 2009 22:01:56 +0100
Subject: [Instiki] Instiki now on GitHub
Message-ID: <BFD8CF5E-8821-4E97-82EB-2B3BB1065435@5uper.net>

Gentlemen, we moved Instiki to GitHub.
Find the latest Development Tree here:
http://github.com/parasew/instiki/tree/master

If you want to contribute, please only use the github repository from  
now on, fork from the url above and send us a pull request
see http://github.com/guides/pull-requests

the svn on rubyforge will be closed soon.
we are currently working on a new forum that is closely tied to the  
instiki mailing list. please let us know if you have any previous  
issues that have not been resolved!

bug tracking: there were several bug trackers for instiki around, we  
are currently moving to a new one, which will also be ready soon.

happy forking!
-parasew


From parasew at 5uper.net  Tue Feb 24 14:54:11 2009
From: parasew at 5uper.net (Matthias Tarasiewicz)
Date: Tue, 24 Feb 2009 20:54:11 +0100
Subject: [Instiki] Instiki 0.16.3 Released: Big steps,
	Rails 2.3.0-RC1 and tons of new stuff!
Message-ID: <5ED6DBC5-4D0D-4BBA-B8CA-F74BE48C4745@5uper.net>

* 0.16.3: Big steps, Rails 2.3.0-RC1 and tons of new stuff!

get the new version here:
http://rubyforge.org/frs/download.php/52272/instiki-0.16.3.zip
http://rubyforge.org/frs/download.php/52273/instiki-0.16.3.tgz


All the patching, developing and great hacking from Jacques Distler was
merged into the main codebase of instiki. Jaques is now also  
maintaining the
main branch (together with parasew), which brings instiki up-to-date!

Find more information about all the changes in his site:

   http://golem.ph.utexas.edu/instiki/

New Features:
* Instiki comes and runs with Rails 2.3.0-RC1
* New Markdown interpreter: Maruku
* Default markup dialect is Markdown+itex2MML
* Mathematics suport, using itex2MML (Markdown+itex2MML)
      http://golem.ph.utexas.edu/~distler/blog/itex2MMLcommands.html
   or BlahTeX (Markdown+BlahTeX/PNG)
      http://golem.ph.utexas.edu/instiki/show/BlahTeX
* Theorem Environments
* Automatic Equation numbering and automatic Theorem numbering,
* Integrated presentation software
      http://golem.ph.utexas.edu/instiki/show/S5
   complete with support for themes
   (available with Markdown, Markdown+itex2MML or Markdown+BlahTeX/PNG)
* Sends application/xhtml+xml to compatible browsers
   (available with Markdown, Markdown+itex2MML or Markdown+BlahTeX/PNG)
   Serve Webs which use non-Markdown Text Filters (Textile, RDoc or  
Mixed) as
   text/html. This makes those Text Filters usable, again.
* Scalable Vector Graphics (SVG) enabled
   (available with Markdown, Markdown+itex2MML or Markdown+BlahTeX/PNG).
* Nifty SVG Logo
   (available with Markdown, Markdown+itex2MML or Markdown+BlahTeX/PNG).
* Atom 1.0 feeds.
* ETag support.
* Filesystem-based caching.
* New, industrial-strength Sanitizer (anti-XSS protection).
* Uses xhtmldiff for redline diff pages.
* (Actually functional) LaTeX output.
* InterWeb WikiLinks
* Add a user interface to manage uploaded files.
* Add a user interface to delete a Web.
* Add a user interface to delete orphaned pages in a Category. In  
addition to
   deleting all orphaned pages, you can now delete just the orphaned  
pages in a
   particular category. Among other things, this provides a handy way  
to delete
   a (selection of) page(s): just assign them to a new category  
(?delete?, say)
   and delete the orphaned pages in that category.
* Add the manage_fixtures plugin for easy database migration
* Descriptions in the File Upload Dialog are used as the default alt  
text (for
   pictures) or the default link text (for files).

Bugfixes:
(see http://golem.ph.utexas.edu/~distler/blog/archives/001893.html for a
complete list)

* fixes to xhtmldiff
* fixed Sanitizer issues
* Do dnsbl lookups more judiciously. Anti-spam effectiveness is  
undiminished,
   but the application is more responsive.
* Fix a Session CookieOverflow when rescuing Instiki::ValidationError
* Domain independent caching
* Fix for no Flash Messages
* Links on ?published? Webs were all screwed-up. Fixed.
* Make uploaded pictures display in the ?published? view.
* Make @import rules in the ?Stylesheet Tweaks? work in the  
?published? view.
* Actually verify the password, when setting a password for a Web,  
rather than
   just pretending to do so.
* fixes for nowiki ?<nowiki>[[!include foo]]</nowiki>?)
* Hide Equations From WikiChunk Processing
* Fix a bug in the Chunk handler, which was mangling backslashes in  
included
   pages.
* Entering the wrong password on the ?CreateWeb? form now redirects  
back to
   the form, as it should.
* Allow single-letter WikiLinks (e.g. ?[[a]]?). Requested by a  
Japanese user.
* Allow single-letter includes (e.g. ?[[!include a]]?).
* Huge improvements to caching and cache-sweeping
* Category listing restricts to current Web.
* All WikiReference methods limit results to the current web
* File uploads work right.
* Make WEBrick respond to TERM signal. (Launchd, in particular,  
requires this.)
* Ditch the URIChunk and LocalURIChunk handlers. Slow, buggy, and of  
dubious
   utility.
* Ensure unsafe operations (new, save,...) are POSTs, not GETs.
* Fix utf-8 bug in WikiChunk handling.
* Disable WikiChunk processing in tags.
* Hide Equations From WikiChunk Processing
* Fix for the "Backslashes in Included Equations" bug.
* Sessions are now stored in a cookie (signed and Base-64 encoded).
   Form_spam_protection stores form_keys in the session.
   Make sure spambots implement both cookies and javascript, by storing
   hashed (with salt) keys in the session.
* Make sure request.ip is a valid IPv4 or IPv6 address.
* Make remove_orphaned_pages work in a proxied situation.
* In the wiki_controller, only apply the dnsbl_check before_filter
   to the :edit, :new, and :save :export actions, instead of all  
actions.
   This makes mundane "show" requests faster, but does not
   compromise spam-fighting ability.
* Be a little gentler in recovering from Instiki::ValidationErrors, when
   saving a page. Previously, we threw away all the user's changes upon
   the redirect. Now we attempt to salvage what he wrote.
* Drop hostname from cache key.
* Fix Recursive Includes.
* Entering an incorrect password on the Create Web form should redirect
   back to the form, with a flash error.
* In the Stylesheet Tweaks, the owner of a Web can specify an @import  
rule
   to pull in CSS styles form an external file. This worked in the  
"show"
   view, but was broken in the "published" view. Fixed.
* Allow multiple leading capital letters in a WikiWord.

From parasew at gmail.com  Fri Feb 27 08:07:06 2009
From: parasew at gmail.com (Matthias Tarasiewicz)
Date: Fri, 27 Feb 2009 14:07:06 +0100
Subject: [Instiki] Instiki 0.16.2: non-english characters (^~) =>
	WikiWord?
In-Reply-To: <F96EAA5C-EC07-43F6-8609-32B65BA8D50E@ptinovacao.pt>
References: <F96EAA5C-EC07-43F6-8609-32B65BA8D50E@ptinovacao.pt>
Message-ID: <AB469FBF-47F5-4446-A49D-A78F33198576@gmail.com>

hi Jos?,
you are right, this is a bug, not a feature ;)
we will take a look into this and fix this asap. hopefully i can fix  
this on the weekend. in the meanwhile, you might want to use the tag
<nowiki>Refer?ncia</nowiki>
for a workaround.

regards,
matthias

On 27.02.2009, at 13:21, Jos? Bonnet wrote:

> Hi!
> I've downloaded v0.16.2 (I'd been using 0.12.0) and noticed that  
> words with accented characters (e.g., Refer?ncia) are being  
> interpreted as WikiWords. Is this correct?
> For me, who use the wiki in Portuguese, it isn't.
>
> Thanks,
> jb

--
Mag.Art. Matthias Tarasiewicz
Board Member of 5uper.net

5uper.net - incorporated society
to promote, research, develop and interlink
media, art and technology

MuseumsQuartier Vienna/ MQ Wien
Museumsplatz 1/10/7
A-1070 Vienna, Austria
EUROPE

Tel/FAX: +43 522 4881
Mobile: +43 699 11101797
SKYPE: PARASEW

http://5uper.net
http://parasew.com


From parasew at 5uper.net  Fri Feb 27 13:00:27 2009
From: parasew at 5uper.net (Matthias Tarasiewicz)
Date: Fri, 27 Feb 2009 19:00:27 +0100
Subject: [Instiki] instiki 0.16.3 on passenger
Message-ID: <FEC82DA1-51B2-4399-B16B-2037F530E1F1@5uper.net>

hi list,

if somebody wants to use phusion passenger with instiki 0.16.3, you  
have to update passenger to version 2.0.6
this is because of rails 2.3.0-rc1, which comes with the current  
version of instiki.

the instiki.org site also runs with passenger version 2.0.6.

-matthias