prologic

twtxt.net

Problems are Solved by Method\" πŸ‡¦πŸ‡ΊπŸ‘¨β€πŸ’»πŸ‘¨β€πŸ¦―πŸΉβ™” πŸ“βš― πŸ‘¨β€πŸ‘©β€πŸ‘§β€πŸ‘§πŸ›₯ -- James Mills (operator of twtxt.net / creator of Yarn.social 🧢)

In-reply-to » Anyone using XMPP? I've been hearing a lot about how it is the OG messaging protocol. That G00gle Talk used to use it as a back-end, that FB messanger and w_hatsapp use some modified version of it or something; And that setting up a server (or even using a public one) would be a better alternative to the aforementioned apps, so I did. Now the question is: "Where the Fu__ are my video calls at!!? 🀣" ... The protocol supports videoconferencing and I'm yet to find a decent Desktop/Mobile client that implements it. I wish I knew enough Code-Fu to contribute/help implement some, somewhere.

@movq@www.uninformativ.de I don’t. but i do use IRC so hmmm 🧐

​ Read More
In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

there is for example, a user configurable and default instance configuration called only one postponed domain

​ Read More
In-reply-to » Also, if bots/spsiders hit your feed, they are showing as followers. Certainly not true. Right now I am blocking all bots, but that’s not the proper approach, I think.

@bender@twtxt.net Please create an issue for this too! Probably against twtd right? We should validate new fetchers and see if they are real clients or not. I think yarnd already does ybis quite well? 🧐

​ Read More

And if we can compile a list and file issues for feeds, twtxt.app and anything else as issues for when i get back πŸ™ feature requests, bug reports. etc 🀞

​ Read More
In-reply-to » Adding support for forking, forked conversations and navigating back to the root of a thread for the Twtxt App 🀞

@itsericwoodward@itsericwoodward.com Haha! I’m glad you like it! 🀣 I ummed and arrred over the set of publishing backends it should support, and in the end decided to support Yarn, Github/Gitea and twtd. I hope that’s enough and flexible enough for most folks 🀞

​ Read More
In-reply-to » @GabesArcade Did you by change edit or otherwise delete the Twt you replied to (2nd last in your feed) with the reply/thread id lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks 🀣

I think I fixed this bug!

​ Read More
In-reply-to » @GabesArcade Did you by change edit or otherwise delete the Twt you replied to (2nd last in your feed) with the reply/thread id lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks 🀣

Oh if we’re talking about the twtxt.app client, that’s a different story. I still consider that alpha/beta quality. Lemme look into that. It has it’s own cache of course (using IndexDB) and it’s entirely possible some behaviours are still not quite right yet…

​ Read More
In-reply-to » @GabesArcade Did you by change edit or otherwise delete the Twt you replied to (2nd last in your feed) with the reply/thread id lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks 🀣

@GabesArcade@gabesarcade.com Yes, because if you edit/delete a Twt after the ecosystem has ingested it, well there then are two versions πŸ˜… Just be aware of edits/deletes, especially if someone has already replied to said Twt 🀣

​ Read More
In-reply-to » @GabesArcade Did you by change edit or otherwise delete the Twt you replied to (2nd last in your feed) with the reply/thread id lleeypvkzbw2? That Twt was never ingested by twtxt.net (and likely the search engine) so umm hmmm threading breaks 🀣

It’s no big deal of course, we are fully aware of the couple of rare(ish) edge cases with the threading model.

​ Read More