#78: Hide subthreads with score lower than X
------------------------+--------------------------
Reporter: ttomecek | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
It would be great if !HyperKitty had a feature to hide messages (and its
possible replies) by default which are:
* below a specified score
* marked as spam
* marked as not constructive
With this system we could get smaller thread tree with messages which are
widely-accepted. On the other hand, this system could hide sensible
messages, which may be interesting to read, but community doesn't like
them.
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/78>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
#84: add RSS feeds
------------------------+--------------------------
Reporter: sumanah | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
Per [http://lists.w3.org/Archives/Public/www-rdf-
interest/2003Feb/0047.html] -- add RSS feeds.
{{{
I just stumbled across this after an #rdfig discussion about adding RSS
support to Mailman, the popular list management and HTML archiving
package.
Turns out the patch exists already (but wasn't intergrated yet).
It took me less than 10 minutes to patch my Mailman installation and
rebuild the archives for rdfweb-dev. I now have
http://rdfweb.org/pipermail/rdfweb-dev/rss.xml generated automatically.
See http://rdfig.xmlhack.com/2003/02/09/2003-02-09.html#1044813421.381747
for the (trivial to apply) patch and related info. Just cd into the
Mailman/Archiver/ directory and do 'patch < ~danbri/rss.patch' or
whatever,
then re-run bin/arch on your archives.
The markup exported is fairly basic, but sets things up nicely for
future extensions -- you could add in richer descriptions of the mailing
lists fairly easily, though I'm not sure how best one would hook such
information up to Mailman's www-based frontend.
Dan
}}}
It would be awesome to be able to subscribe to a specific list via RSS;
after that, it would also be neat to be able to subscribe via RSS to all
public lists on a domain, to mail from a specific user, or to mail to a
list on a specific "topic"/thread.
I'm taking this idea from
http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28
-- a TODO/wishlist for the Mailman 3.x series.
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/84>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
#67: RFE: Provide an alternate thread viewer interface
------------------------+--------------------------
Reporter: duffy | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
Request from LWN article comments (http://lwn.net/Articles/596895/)
"I kinda wish HyperKitty would also offer a threaded hybrid interface in
addition to showing the thread in a messageboard-like fashion.
"Like Gmane does, or slrn, or mutt: The screen split horizontally, with
the upper half showing the subject lines arranged in a threaded hierarchy,
and the lower half showing one message. I personally find that easier and
more logical to navigate."
It would be cool to provide this maybe as a user option; I think I could
make this work with some CSS hackery. I will play around with this and see
if I can come up with anything.
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/67>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
#68: RFE: Change like/dislike system
------------------------+--------------------------
Reporter: duffy | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
Some comments from the LWN article thread
(http://lwn.net/Articles/596820/)
"The like/dislilke should be implemented based on personal preference not
controlled by majority..."
"Advogato's diary ratings got that right, based on its trust metric:
http://advogato.org/trust-metric.html"
" The problem with upvote/downvote/karma systems is that they allow a
majority mindset to establish and stay established. Just look at the
circle-jerks on Hacker News and Reddit (where clever algorithms have had
to be tacked on especially to try to reduce the effects of group-think).
Everyone with a slightly different point of view to the established clique
gets downvoted, and downvoted messages are more likely to attract more
downvotes. People don't click anonymous upvote/downvote buttons because of
reasoned, civil thought, they do it as a deep, primal, emotional, self-
centred reaction. They might do it because $famous_person or $alpha_person
did. They don't think "does this add objective value to the conversation?"
they think "do I agree with this? Does this person's literacy meet my
standards? Do they use C or C++? Do they use emacs or vim? Down with their
opinions!" People are awful. Giving them downvote buttons only enables
their awfulness."
I wonder if it would be possible to swap out how we do the likes/dislikes,
or at least sit down and re-think it. This is one area that has been hard
to test out on the staging server.
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/68>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
#98: Should threads show up in every month they are active?
------------------------+-------------------
Reporter: sumanah | Owner: duffy
Type: enhancement | Status: new
Priority: major | Milestone: 1.0
Version: | Keywords:
------------------------+-------------------
Hi Mo!
Right now, neither of the pages for the March archive of the hyper-kitty
test list ([https://lists-dev.cloud.fedoraproject.org/archives/list
/hyperkitty-test%40lists-dev.cloud.fedoraproject.org/2015/3/?page=1 1],
[https://lists-dev.cloud.fedoraproject.org/archives/list/hyperkitty-test
%40lists-dev.cloud.fedoraproject.org/2015/3/?page=2 2]) include [https
://lists-dev.cloud.fedoraproject.org/archives/list/hyperkitty-test
%40lists-
dev.cloud.fedoraproject.org/thread/WGOEOE7UHT5JUTTB4PINIJEKXYNIXLEB/ the
"test 6" thread], even though the original message in that thread was sent
in March. That's because right now, a thread only shows up in the monthly
archive for the month in which that thread was last active.
Instead, I think that a thread should show up in the monthly archive of
every month that it was active. Do you agree?
Thanks!
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/98>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.
#50: Handling of users changing Subject lines of threads
------------------------+--------------------------
Reporter: ianweller | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Beta version
Version: | Keywords:
------------------------+--------------------------
Sometimes you see this subject line in threads:
Subject: Re: Bar (was: Foo)
My understanding from abompard is that HyperKitty currently does not show
the subject change at all to the user. It should probably at least show
the new subject to the user.
Two ways of potentially dealing with this:
* Where the subject changes in the thread, add it above the first message
(what most mail clients do)
* Make it a different thread (what in some cases might make more sense --
and if it did break a thread incorrectly, you could reattach it, but then
you still want to show the subject line change).
--
Ticket URL: <https://fedorahosted.org/hyperkitty/ticket/50>
HyperKitty <http://mm3test.fedoraproject.org>
The HyperKitty Django app provides a web interface to access GNU Mailman archives.