Sort by: Newest, Oldest, Most Relevant
(#c6yyvda) Woa, go easy, mate! Don't be upset, @prologic. Everybody can use whatever they want, or not. That's absolutely their free choice. From my point of view @lucidiot's statement is just like ranting about any other shitty¹ software or topic in general. Precisely like that, not more, not less. Just this time it's something you've built. I've written some of the extensions, but I don't feel offended at all. It's just an offer we make, not everybody has to accept it. That's just the way it goes. And it is good this way. ¹: like everything else, this is highly subjective

matched #b7kwmdq score:11.26 Search by:
Search by 2 mentions:
Search by 1 tags:
@prologic @eaplmx (#c6yyvda) To be fair, the only thing I can think of that makes Yarn feeds not be "standard twtxt" is the disregard for twt size (which many others also do with their non-yarn clients). But sure, I can see how reading these feeds might be frustrating: too big posts, markdown everywhere, linebreak characters, emojis... But I'll consider it the "freedom of the user" to decide whether or not to follow a feed written in a certain style. The provocative metadata comment? Easy (and better) to just ignore.

matched #chfyroq score:11.26 Search by:
Search by 2 mentions:
Search by 1 tags:
(#c6yyvda) @marado well, I find that's a problem of leaving that open. Using should vs must. Leaves that to different interpretations. >A status should consist of up to 140 characters, longer status updates are technically possible but discouraged. twtxt will warn the user if a newly composed status update exceeds this limit, and it will also shorten incoming status updates by default.

matched #ee7jksq score:11.26 Search by:
Search by 1 mentions:
Search by 1 tags:
This is twtxt search engine and crawler. Please contact Support if you have any questions, concerns or feedback!