💾 Archived View for rawtext.club › ~sloum › geminilist › 004751.gmi captured on 2023-11-04 at 14:25:41. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Alex // nytpu alex at nytpu.com
Wed Jan 6 20:47:27 GMT 2021
- - - - - - - - - - - - - - - - - - -
I really like this idea! Mixing the ease of writing, simplicity, andasynchronicity of gemlog replies with the ease of reading on acentralized page instead of searching out all the relevant posts on anaggregator.
I link to GUS' backlinks on my own gemlog, but by the time GUSupdates (last updated: 2020-12-06) my posts are usually over a monthold, making the backlinks practically useless to anyone following theconversation as it unfolds. Another way to have these sorts ofconversation are in order, saving people from having to make postslisting the full conversation like:gemini://republic.circumlunar.space/users/flexibeast/gemlog/2021-01-06.gmi
Some feedback:
I originally intended to annouce this with a working capsule directly,
but I’m having a hard time finding time to implement a board, and I
wanted to do something completely based on text/gemini files for data
to avoid using a database and it’s harder than anticipated.I see no reason why your board server couldn't use a database (or anon-gemtext file format) in the backend. It would probably make it alot easier when querying and parsing since you can use a customstructure that suits your internal data format, then just render togemtext once you're done.
The board should present a threaded view of messagesI have mixed feelings on threaded forums in general, but if you thinkit's best it it's not the end of the world. However, it would/significantly/ simplify implementations if you just chronologicallygrouped messages by post tag. You'd no longer have to query everysingle tagged post and find the first link, instead just querying thegemini feed page, saving lots of server time and bandwidth for both theboard hoster's server and the post author's server.
However, this non-threaded approach creates a problem. This is the onlysituation I've come across so far that is actually limited by the geminifeed's no timestamp limitation. Since conversations can happen in thespan of a day, it would make it hard to group them. This would be themain reason I could think of for keeping the threaded design currentlyproposed.
I dunno, it's something to ponder on. I do love the idea though, andwill be trying out your implementation when it's done.
~nytpu
-- Alex // nytpualex at nytpu.comGPG Key: https://www.nytpu.com/files/pubkey.ascKey fingerprint: 43A5 890C EE85 EA1F 8C88 9492 ECCD C07B 337B 8F5Bhttps://useplaintext.email/-------------- next part --------------A non-text attachment was scrubbed...Name: signature.ascType: application/pgp-signatureSize: 833 bytesDesc: not availableURL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210106/3216f154/attachment.sig>