~raphm

Trackers

~raphm/gemthread

Last active 7 months ago

#1 Centralization Problem 7 months ago

Comment by ~raphm on ~raphm/gemthread

Also an archiving suggestion (also from Toby): "A more radical idea is that each thread is compiled into a gempub. To view a thread and the responses, you download the latest gempub and view it. When a user adds another response, the gempub is recompiled with the new response inlined. This way, if the GemThread server is taken offline, people may still have gempub copies of the threads they were interested in. Perhaps this could be extended with an aggregator that downloads gempubs for thread you've started or responded to."

This would be relatively trivial to add.

#1 Centralization Problem 7 months ago

Comment by ~raphm on ~raphm/gemthread

Toby's suggestion: "Perhaps it's the responses that should link back to the topic, and up to GemThread to pull them all together like the lace script currently does. So a poster can just submit their response to GemThread and it finds the original topic, creates it if necessary, and stitches in the response."

This feels like an easier way to initiate a thread.

#3 No way to get a consolidated view 7 months ago

Ticket created by ~raphm on ~raphm/gemthread

Toby Kurien: "Other people can run their own instances of GemThread, but now threads and responses may end up spread across them, with no easy way to get some consolidated view."

This is definitely a gap that I've been pondering as well. More thought required.

#2 Possibly too much effort 7 months ago

Ticket created by ~raphm on ~raphm/gemthread

Toby Kurien: "It seems a chore to add all my posts to a GemThread server, just in case anyone wants to respond. Otherwise, the person responding will have to add the original thread and the response thread. Not a train-smash, but this may be a barrier."

I agree with this. It seems like the primary use pattern will be that a person finds a thread that they want to respond to, they add the thread to a gemthread server, and then they add their response. It feels like there is an opportunity for some sort of automatic initiation protocol, or perhaps some sort of dovetail with geminimention.

#1 Centralization Problem 7 months ago

Ticket created by ~raphm on ~raphm/gemthread

Toby Kurien: "If the GemThread server goes down, all I am left with are my responses with possibly no link-back to the original thread nor a way to rebuild the thread by following and collecting links. Seems like a centralization problem."

This is also a concern I share. This calls for some sort of mirroring, archive protocol, or federation. More thought is required. :)