mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-11-10 00:12:09 +00:00
Compare commits
2 commits
99264641f3
...
d5b19a0d72
Author | SHA1 | Date | |
---|---|---|---|
|
d5b19a0d72 | ||
|
d3c992b397 |
2 changed files with 28 additions and 0 deletions
18
content/notes/better-vote-enabled-forums.md
Normal file
18
content/notes/better-vote-enabled-forums.md
Normal file
|
@ -0,0 +1,18 @@
|
||||||
|
---
|
||||||
|
title: "Better vote-enabled forums"
|
||||||
|
date: 2022-06-14T10:53:12-07:00
|
||||||
|
description: 'Armchair speculation: how we can learn from Redit, Lemmy, "Hacker" "News", et al to build forums for discussion rather than validation and attention-seeking.'
|
||||||
|
---
|
||||||
|
Armchair speculation: how can we learn from Reddit, Lemmy, "Hacker" "News", et al?
|
||||||
|
|
||||||
|
1. A vote should be part of a reply with at least <var>N</var> words. <var>N</var> could be increased by mods and admins. Instances could federate votes conditionally based on the length or activity of a comment. Word counts can be problematic; I don't know a better alternative (maybe clause-count?). Flagging doesn't need a minimum word count.
|
||||||
|
|
||||||
|
2. Forums shouldn't host their own top-level posts and comments. Those should be links from authors' own websites with microformats (think [IndieWeb](https://indieweb.org/)). The forum should be Webmention-enabled.
|
||||||
|
|
||||||
|
3. Larger communities should have ephemeral chatrooms ("ephemeral" in that public history has a retention limit if it exists at all) to incubate posts. Authors (yes, original authors) could share their work and collect feedback/improve it before it's "ready". They could then post with increased visibility.
|
||||||
|
|
||||||
|
4. One reason to flag a top-level comment could be "didn't look at the post". I say "look at" instead of "read" because certain posts are huge essays that could take hours to read. Top level commenters should at least be expected to skim.
|
||||||
|
|
||||||
|
These qualities will make a forum less active, since the quality of content will be higher and some validation and attention-seeking will be filtered out. Low activity means higher visibility for good content. Forums could "get of the ground" by starting invite-only, gradually enabling these rules one-by-one before opening to the public.
|
||||||
|
|
||||||
|
(psst: I might be working on "a thing").
|
10
content/notes/dillo-repository-mirror.md
Normal file
10
content/notes/dillo-repository-mirror.md
Normal file
|
@ -0,0 +1,10 @@
|
||||||
|
---
|
||||||
|
title: "Dillo repository mirror"
|
||||||
|
date: 2022-06-14T13:45:31-07:00
|
||||||
|
---
|
||||||
|
|
||||||
|
Dillo's domain name has expired, making it impossible to fetch its Mercurial repository from its canonical location. Fortunately, Mercurial is a distributed version control system, and I had a copy. [I pushed my copy to hg.sr.ht](https://hg.sr.ht/~seirdy/dillo-mirror); you can see it there.
|
||||||
|
|
||||||
|
The Wayback Machine also has [recent snapshots of dillo.org from May.](https://web.archive.org/web/20220511073123/https://www.dillo.org/)
|
||||||
|
|
||||||
|
I imagine that at least a few people have copies of the mailing list archives.
|
Loading…
Reference in a new issue