@prologic@twtxt.net (#vp2aicq) It’s a hint: it nudges my feed’s followers ā€œhey read this twtxt in another feedā€. We can probably find a better way to implement these hints or nudges, but if there’s nothing in place, I wonder if we won’t end up with a bunch of twtxts just saying ā€œagreeā€ or ā€œ+1ā€ā€¦


#5efnnyq

@prologic@twtxt.net (#nsmsvfq) Apparently, nitter ā€œUses Twitter’s unofficial API (no rate limits or developer account required)ā€, so I suppose you could run your own instance and not depend on a 3rd party, or even just see on nitter’s code (it’s free software!) thev relevant parts of that ā€˜unofficial API’…


#ewa7j4q

@prologic@twtxt.net (#opev6mq) Spoofing is always possible, and always a concern (don’t we ā€œdealā€ with it already for the url field?).

For the side-question, the feature is nice but depends on availability, and trust, I’m more interested in adversarial interoperability. What if I’m moving from a pod because I dislike their new policies, or new terms of service, their monetization model, etc.? And what guarantees do we have that every pod (or even yarn implementation) will have the redirect option available to its users?


#ahdl23q

(#qkqefka) @ullarah@txt.quisquiliae.com I check twtxt just now but it seems the way to go, the js code in the article feels a bit excessive to me.

A simple class added to the post that have more than X lines should be enough.

And by just nullifying the max-height with none or initial should do the job, or even better having a read-more class that add the max-height and show the button, it would be even cleaner.


#hxa2s5a