# External links editing problem on ruby garden

**URL:** <https://rubytalk.org/t/external-links-editing-problem-on-ruby-garden/14791>\
**Category:** ruby-talk\
**Created:** [14 November 2004 16:46 UTC](https://rubytalk.org/t/external-links-editing-problem-on-ruby-garden/14791 "2004-11-14T16:46:20Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sam\_Roberts1](https://avatars.discourse-cdn.com/v4/letter/s/ed8c4c/32.png) [@Sam\_Roberts1](https://rubytalk.org/u/Sam_Roberts1)\
**Post date:** [14 November 2004 16:46 UTC](https://rubytalk.org/t/external-links-editing-problem-on-ruby-garden/14791/1 "2004-11-14T16:46:20Z")

</div>

It has become quite hard to edit rubygarden's wiki. Any page with a  
link, if you try to change it you get redirected to:

&nbsp;&nbsp;[http://www.rubygarden.org/ruby?ExternalLinks](http://www.rubygarden.org/ruby?ExternalLinks)

Your homework assignment is then to search the ruby-talk archives to  
find out what's required...

This is NOT easier than asking for a passwd, not the first time. And  
even once you know the mixed case convention, all editors are forced to  
go through and change all the links in any page they edit. Again, this  
is more time-consuming than logging in.

I wouldn't be so bad if the ?ExternalLinks page described how to fix  
links, and why (everybody appreciates the pain of spam fighting).

Can I add that description, or is it some kind of security thing to only  
let people in the know, or willing to search ruby-talk, edit pages?

I was just about to edit the page, then realized it might be  
intentional...

Thanks!  
Sam

---

<div class="post-metadata">

**Author:** ![Francis\_Hwang1](https://avatars.discourse-cdn.com/v4/letter/f/ecae2f/32.png) [@Francis\_Hwang1](https://rubytalk.org/u/Francis_Hwang1)\
**Post date:** [14 November 2004 17:02 UTC](https://rubytalk.org/t/external-links-editing-problem-on-ruby-garden/14791/2 "2004-11-14T17:02:35Z")

</div>

I haven't been paying that much attention to this discussion, but wouldn't it be possible to set up a whitelist so certain external URLs can be safely posted?

> **···**
>
> On Nov 14, 2004, at 11:46 AM, Sam Roberts wrote:
> 
> > It has become quite hard to edit rubygarden's wiki. Any page with a  
> > link, if you try to change it you get redirected to:
> > 
> > &nbsp;&nbsp;[http://www.rubygarden.org/ruby?ExternalLinks](http://www.rubygarden.org/ruby?ExternalLinks)
> > 
> > Your homework assignment is then to search the ruby-talk archives to  
> > find out what's required...

---

<div class="post-metadata">

**Author:** ![James\_Britt6](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@James\_Britt6](https://rubytalk.org/u/James_Britt6)\
**Post date:** [14 November 2004 17:15 UTC](https://rubytalk.org/t/external-links-editing-problem-on-ruby-garden/14791/3 "2004-11-14T17:15:51Z")

</div>

Sam Roberts wrote:

...

> Can I add that description, or is it some kind of security thing to only  
> let people in the know, or willing to search ruby-talk, edit pages?
> 
> I was just about to edit the page, then realized it might be  
> intentional...

Quick summary: Much spam. Much from bots. Quick hack to stop bot spam by requiring urls to use uppercase HTTP. Still spam from humans; at least make them work for it.

James

---

<div class="post-metadata">

**Author:** ![Jim\_Weirich1](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jim\_Weirich1](https://rubytalk.org/u/Jim_Weirich1)\
**Post date:** [15 November 2004 02:44 UTC](https://rubytalk.org/t/external-links-editing-problem-on-ruby-garden/14791/4 "2004-11-15T02:44:55Z")

</div>

Sorry for the pain. I think the HTTP think was partially successful in  
reducing spam. We have only had a few incidents of spam related activity in  
the past few days. Perhaps the spammers have gone to greener pastures or  
perhaps they are just waiting until our guard is down.

The ExternalLinks page did at one time have an explaination of how to  
represent external links. It was expressed as a Ruby algorithm on the theory  
that the casual spammer wouldn't/couldn't read it. Someone removed the  
description because they felt it made the information too readily available.  
At the time, I let it go, but based on your feedback I've restored it. Take  
a look and see it it is ok. It should be plain enough to anyone with a ruby  
background.

Regarding existing pages with lowercase links. You are right, they are a pain  
to edit. I've fixed a number of them by hand, but the real answer is to walk  
through each page file with a script and fix the page data. I've got this on  
my todo list.

Thanks for the feedback.

> **···**
>
> On Sunday 14 November 2004 11:46 am, Sam Roberts wrote:
> 
> > It has become quite hard to edit rubygarden's wiki. Any page with a  
> > link, if you try to change it you get redirected to:
> > 
> > &nbsp;&nbsp;[http://www.rubygarden.org/ruby?ExternalLinks](http://www.rubygarden.org/ruby?ExternalLinks)
> > 
> > Your homework assignment is then to search the ruby-talk archives to  
> > find out what's required...
> > 
> > This is NOT easier than asking for a passwd, not the first time. And  
> > even once you know the mixed case convention, all editors are forced to  
> > go through and change all the links in any page they edit. Again, this  
> > is more time-consuming than logging in.
> > 
> > I wouldn't be so bad if the ?ExternalLinks page described how to fix  
> > links, and why (everybody appreciates the pain of spam fighting).
> > 
> > Can I add that description, or is it some kind of security thing to only  
> > let people in the know, or willing to search ruby-talk, edit pages?
> > 
> > I was just about to edit the page, then realized it might be  
> > intentional...
> 
> --  
> -- Jim Weirich jim@weirichhouse.org [http://onestepback.org](http://onestepback.org)  
> -----------------------------------------------------------------  
> "Beware of bugs in the above code; I have only proved it correct,  
> not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)

---

<div class="post-metadata">

**Author:** ![Sam\_Roberts1](https://avatars.discourse-cdn.com/v4/letter/s/ed8c4c/32.png) [@Sam\_Roberts1](https://rubytalk.org/u/Sam_Roberts1)\
**Post date:** [14 November 2004 17:25 UTC](https://rubytalk.org/t/external-links-editing-problem-on-ruby-garden/14791/5 "2004-11-14T17:25:54Z")

</div>

Quoteing jamesUNDERBARb@neurogami.com, on Mon, Nov 15, 2004 at 02:15:51AM +0900:

> Sam Roberts wrote:  
> \>Can I add that description, or is it some kind of security thing to only  
> \>let people in the know, or willing to search ruby-talk, edit pages?  
> \>  
> \>I was just about to edit the page, then realized it might be  
> \>intentional...
> 
> Quick summary: Much spam. Much from bots. Quick hack to stop bot spam  
> by requiring urls to use uppercase HTTP. Still spam from humans; at  
> least make them work for it.

Understood. I'm starting to like the login/passwd idea, though. At least  
internet users understand the mechanism. The capitialize all HTTP thing  
is more like a secret handshake!

Cheers,  
Sam

---

<div class="post-metadata">

**Author:** ![Sam\_Roberts1](https://avatars.discourse-cdn.com/v4/letter/s/ed8c4c/32.png) [@Sam\_Roberts1](https://rubytalk.org/u/Sam_Roberts1)\
**Post date:** [15 November 2004 02:48 UTC](https://rubytalk.org/t/external-links-editing-problem-on-ruby-garden/14791/6 "2004-11-15T02:48:37Z")

</div>

Quoteing jim@weirichhouse.org, on Mon, Nov 15, 2004 at 11:44:55AM +0900:

> The ExternalLinks page did at one time have an explaination of how to  
> represent external links. It was expressed as a Ruby algorithm on the theory  
> that the casual spammer wouldn't/couldn't read it. Someone removed the  
> description because they felt it made the information too readily available.  
> At the time, I let it go, but based on your feedback I've restored it. Take  
> a look and see it it is ok. It should be plain enough to anyone with a ruby  
> background.

It looks great, particularly the note about existing links.

Thanks,  
Sam

---

<div class="post-metadata">

**Author:** ![James\_Britt6](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@James\_Britt6](https://rubytalk.org/u/James_Britt6)\
**Post date:** [14 November 2004 18:04 UTC](https://rubytalk.org/t/external-links-editing-problem-on-ruby-garden/14791/7 "2004-11-14T18:04:47Z")

</div>

Sam Roberts wrote:

> Quoteing jamesUNDERBARb@neurogami.com, on Mon, Nov 15, 2004 at 02:15:51AM +0900:

> > Quick summary: Much spam. Much from bots. Quick hack to stop bot spam by requiring urls to use uppercase HTTP. Still spam from humans; at least make them work for it.
> 
> Understood. I'm starting to like the login/passwd idea, though. At least  
> internet users understand the mechanism. The capitialize all HTTP thing  
> is more like a secret handshake!

Yes, very much so.

Thinking out loud:

The choice seems to depend on where best to shift the burden or cost of maintenance and compliance. Using a login system, code must be added to manage it, which is a one-time cost, but there is also a recurring cost of checking that users are not abusing privileges. Users may also forget their passwords, so one can either write code to manage that part, or carry the admin burden of manually providing the password. For users, though, the system is familiar and easy, and password management is often built into the Web browser, so there is little to do once a login in obtained.

With the secret handshake approach, there is also a one-time code cost, but it is arguably much lower than the cost of a password system. The burden of compliance is carried more by the user, who must go figure out the handshake. There is a recurring admin cost of monitoring for spam, but that may always be the case no matter what. And users tend to be the ones reporting spam, not a site admin. Users also carry a recurring cost, having to employ the handshake for any post that includes a URL.

If the handshake needs to change, the overall cost is going to be much lower for the administrator than for users.

In general, what are the criteria when deciding how to assign such costs? Partly it has to do with barriers to entry, so another question might be, what sort of barriers to participation produce the most useful or interesting results?

James
