Searching We.Love.Privacy.Club

Twts matching #Conversations
Sort by: Newest, Oldest, Most Relevant

Thank you for bringing this to our attention, Mr. Fastidious. We fully agree with you.

@lyse@lyse.isobeef.org Sir, you really should have forked that conversation long back to keep our environment clean and tidy. Unfortunately, you did not attend the meeting earlier, so we have to advise you in writing to be prudent. Please keep in mind the fork lockdown is currently not in place. There are currently no plans to enforce it in the near future.

⤋ Read More

Ignite Realtime Blog: inVerse plugin for Openfire version 9.0.0.1 released!
The Ignite Realtime community is happy to announce the immediate availability of a an update to the inVerse plugin for Openfire, which makes the Converse.js web client available to your users.

This release updates Converse to version 9.0.0.

Your Openfire instance should automatically display the … ⌘ Read more

⤋ Read More
In-reply-to » @movq would it be possible to trim the subject to, say, 100 or 140 characters? Just the subject.

@movq@www.uninformativ.de

If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager

Yes, I do the same, true.

So I decided: Okay, let’s have mutt do it.

And Mutt does it well. I agree it was/is a good idea.

The subject lines are already “compressed”

I noticed, yes.

I am not sure why I asked to begin with; in retrospect, in was a silly request. Perhaps the OCD in me got triggered while viewing rich headers, on a specific twt, when I saw the huge subject line that is, otherwise, always hidden.

Anyway, don’t mind me, move along. 😂

⤋ Read More

@movq@www.uninformativ.de what is your cron job repeat time for jenny? Currently I have mine to every minute, and while it allows me to participate fairly quick on conversations it has some drawbacks: it captures every single edited twt, so I end up with seemingly the same twt, but not quite—as it has minor edits, etc. So, “repeats”. Perhaps setting cron to check every 5 minutes or so is best?

⤋ Read More

@prologic@twtxt.net we would want:

  • a way to reply to the current thread. We have this.
  • a way to reply to a specific twt. Need this. Maybe make all the replies start new conversations?
  • check if twt is start of a conversation.. we kinda have this in the main feed with the conversation button. need to extend it for forked convs
  • a way to inline first replies. maybe show one or two in the sub thread with a link to view.
  • for convenience have a link to parent conv?

⤋ Read More

@vain@www.uninformativ.de the truth is, i never “got” or liked twitter. i think it’s way too noisy and a terrible way to have a conversation, what with the character limit and all. and then mastodon came along and i thought it would be different, but then it became too twitter-like. i get what you mean about twtxt and discoverability, that is one of its drawbacks.

⤋ Read More

@tdemin@tdemin.github.io good points, though another that I’ve noticed is that it’s difficult to tell who in your network is actually reachable with your tweets. My HTTPS cert went unupdated for a brief while and now I have no idea who is still following me since I got it working again, so it’s difficult to tell where I can really have a conversation. A centralized service can tell who’s following who, but that’s basically impossible in twtxt.

⤋ Read More