Conversation
Notices
-
I wonder if it's possible to delete others' notices with this client... Someone post something and lemme see, since I'm too lazy to just ask @bitshift myself.
-
@redenchilada Posting pink Celestia
-
@redenchilada Nope. There are no API methods (in the twitter-compatible API at least; will have to take a look when migrating to the AtomPub API) for basically _any_ moderation functions, making it very hard for a client to actually do them (short of manually fetching/parsing the normal site HTML, which is a terrible idea in so many ways).
-
@bitshift tl;dr StatusNet is a POS?
-
@redenchilada Is POS like TOS? Piece of services?
-
@redenchilada Eh, it's understandable as far as the twitter-compatible API goes; Twitter has no public APIs for such things. If it's still not possible via the AtomPub API (which IdentiCurse is migrating to in the long term), then yes. And it's still a POS in other ways (most of which Cerulean has complained about in detail here). :P
-
@bitshift More like piece of horse manure.
-
@november POS = Piece of <word that would break RDN's rules>.
-
@redenchilada That meant to go to november. @bitshift Might it be possible to pause the timeline while a notice is being typed? :<
-
@redenchilada It already pauses if it hasn't started a refresh yet. Still not entirely sure how best to go about pausing a refresh that's already in progress, though I do want to get _something_ working there, having had the same issue before.
-
@bitshift Possibly just hold the server response until the notice is sent?
-
@redenchilada You could work around it via doing "/r[eply] NUM" with no message, that goes into "reply mode", which locks in the replied-to notice even if the timeline then refreshes. It's not obvious, and wasn't even the point of reply mode, but it does the job well enough until I find the aforementioned usable solution to the problem.
-
@redenchilada The problem right now is that the threading approach used is terrible, so once a refresh thread is going, there's no good way to tell it to stop. An overhaul of that is the solution, but I've not yet got around to it.
-
@bitshift I see. Still, aside from my not being used to the non-graphical interface, this is probably the best client I've used so far.
-
@redenchilada Heck, most of the remaining problems stem from code that worked, but isn't ideal, and needs to be replaced, but they're all in places that make it tricky to replace them without tweaking/rewriting a lot of other things. :(
-
@redenchilada Practically speaking, it'd probably benefit from a ground-up rewrite of most of it, but again, I've not had the time yet. Hopefully should have a lot more time over the summer once uni exams are done with, though, so there's always hope there. :)
-
