Re: [boost] codepad code longevity ?

Subject: Re: [boost] codepad code longevity ?
From: OvermindDL1 (overminddl1_at_[hidden])
Date: 2010-01-29 20:54:23

On Fri, Jan 29, 2010 at 6:45 PM, Dean Michael Berris
<mikhailberis_at_[hidden]> wrote:
>> On Fri, Jan 29, 2010 at 6:32 PM, Dean Michael Berris
>> <mikhailberis_at_[hidden]> wrote:
>>> The only point I was making is that Github gists is an alternative
>>> means of doing it. Of course if the code fits in an email and is worth
>>> inlining, then that's alright I guess.
>>
>> Not asking about alternates, rather asking *NOT* to do it at all
>> actually. Â Inline if short enough, or attach it as a full compilable
>> example.
>>
>
> So what would the consequence be for people who do post links to gists
> or codepad-like services? :D

Asking them to follow the rules.  If they break too many rules, probably banned.

On Fri, Jan 29, 2010 at 6:45 PM, Dean Michael Berris
<mikhailberis_at_[hidden]> wrote:
> Anyway, I think if it's longevity of stuff on codepad is the problem,
> then not using codepad is one solution. Inlining and attachments are
> fine until you run into the attachment limit problem.

I have yet to run into that though, and I have posted some pretty
massive post-processed code files.  :)

On Fri, Jan 29, 2010 at 6:45 PM, Dean Michael Berris
<mikhailberis_at_[hidden]> wrote:
> I guess what I'm saying is "discouraging" someone from doing it is
> different from "banning" it. Unless there's a way for automatic
> transparent enforcement of that, I'm not really seeing the benefit.

Same as following any other rule, like no top-posting.

On Fri, Jan 29, 2010 at 6:45 PM, Dean Michael Berris
<mikhailberis_at_[hidden]> wrote:
>> On Fri, Jan 29, 2010 at 6:32 PM, Dean Michael Berris
>> <mikhailberis_at_[hidden]> wrote:
>>> If the concern was longevity, as long as the user's github account is
>>> active and the gist has not been deleted, then it's just like anything
>>> else out there that's accessible via a link. :)
>>
>> Not just longevity, but also searchability, remember, everything here
>> is archived, it needs to all be searchable *in-context*. Â Links
>> elsewhere, whether codepad or anything else awful like that, like
>> gist, harm that in a number of ways.
>
> Alright, I get the point.
>
> However I don't agree that it's as evil as it's being called out to
> be. It's the same problem when using tinyurl or bit.ly or even just
> "natural" link rot -- I don't see how it's a huge downside. If there's
> a downside like SEO friendliness, I think it's marginal enough to be
> acceptable.

But it really is as evil.  The whole reason this came up at all is due
to complaints about some old links to code in old posts were no longer
working, thus the person had to post to ask how to fix it since the
old fix disappeared into the aether.