[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Snapshot: 2007-02-18
Re: Snapshot: 2007-02-18
Sat, 24 Feb 2007 02:44:47 +0100 (CET)
On Sun, 18 Feb 2007, Dmitry Borodaenko wrote:
This snapshot incorporates the most easy and uncontroversial from
Boud's suggestions and patches, such as translation-related fixes
(including ellipsis and Front Page link), image links starting with
//, and hidden messages.
Expect it in experimental soon.
070218 passed my (very elementary) tests. :) Nice.
i've shifted "message-hide" down to the deprecated section of:
Status of other outstanding issues:
- calendar: at a quick glance, the design seems to be too intrusive, I
need more time to have a good look at it and see what can be done
- rss-import: I still need to refactor message handling so that this
can be done in a cleaner way
Given the goal of keeping samizdat totally transparent and
keeping as much editorial "power" at the guest and registered
user level (and in some cases, moderator level), i think we have a problem
putting the RDF URI list in the config file, but i don't see any trivial
and totally user-friendly solution.
My idea at the moment is put the ID number of a message in the config,
where that message holds the RDF inputs in yaml format and is open for
editing for all members. It's potentially open to abuse, but if email
is enabled, then the barrier for registered users is more than for
totally anonymous people, and it's something like the same "gamble" of
wikipedia: trust that most people are reasonable and can correct each
others' errors. By the time that the tiny minority decide to make the
effort required to be abusive, a community should have built up which
will quickly correct the abuse, and if necessary, think of further steps
in the software evolution. And this would be better than having the
sysadmin manage the list of RDF feeds.
This could also be potentially revolutionary. ;) If everybody around
the world not only started publishing their own articles, but also
selecting their own RDF feeds, which in turn get exported to others (this
would require rdf imports being *really* imported and turned into local
resources, so that they could be output as well as input, and as well,
modified), then we'd have a huge number of potential positive feedback
loops. Of course, there should also be negative feedback loops, but this
is the sort of thing that could really make indymedia 2.0 :). Especially
with translation included.
But other stuff needed would be something like "traceability" to
measure the different filters (in the Hermann & Chomsky sense, also in
terms of geographical balance) which have been applied to a resource
on its chain from initial production through several export/import
steps on different servers.
We could then apply anti-filters against the 5 corporate propaganda
filters in the Hermann-Chomsky model
Anyway, the snapshot seems fine to me :).