edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: commandline@yahoogroups.com, Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] wikipedia
Date: Fri, 14 Feb 2014 05:27:56 -0500	[thread overview]
Message-ID: <20140114052756.eklhad@comcast.net> (raw)

I was flirting with the idea of writing a wikipedia article on edbrowse,
since I believe it has become "notable".
I have three sources to confirm credibility: it's packaging in debian, ubuntu,
and free bsd.
So I wrote the article, which is really the easy part.
Then moving on to submit the article, a process which ironically
could likely be done entirely with edbrowse, except for the captchas.
Here is my brief excursion into wiki.

1. Creating an account is highly recommended, but requires getting
past a captcha. No audio version.

2. It is possible to submit an article without an account, but at the last step,
to submit, you must get past another captcha.  Christ!
This hurdel will exist I'm sure whether you have an account or not.

3. The article must be written in a specialized markup language,
not html and not nroff or troff, or anything I know.
Something else to learn.

4. They won't submit an article for you, or help you format one;
I asked.
They will however create an account for you,
Then click on {Request an account}
I needed the vs option here, their certificate is not known to my root.
Account setup is pretty straightforward after that,
but what about the markup language?
the tutorial on it is horribly visual.
I can't make heads or tails of it.
The best bet is perhaps to find a short article on anything,
and edit it, like you're going to fix a problem with it,
and maybe then you can read the raw markup that generates the article,
and reverse engineer the language.
I suppose I wouldn't mind doing that if I were to submit or modify
dozens of wiki articles in the future,
but boy that seems like a lot of work for submitting one article.
And even if I did all that I still have to get past the last captcha.
So I'm not sure at this point if I'm going to bother.

Karl Dahlke

             reply	other threads:[~2014-02-14 10:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 10:27 Karl Dahlke [this message]
2014-02-14 13:40 ` Chris Brannon
2014-02-14 20:17   ` [Edbrowse-dev] [commandline] wikipedia Robert Ransom
2018-07-13 13:58 [edbrowse-dev] wikipedia, if anybody cares, if it really matters Karl Dahlke
2018-07-17  1:44 ` [edbrowse-dev] wikipedia Kevin Carhart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140114052756.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=commandline@yahoogroups.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).