Ideas for brower extention/plug-in (Chrome, Firefox etc.) #951

Render twtxt files in a nice view
Add twtxt feed to your Yarn follow-list
Share this pages to your Yarn timeline

- Render twtxt files in a nice view - Add twtxt feed to your Yarn follow-list - Share this pages to your Yarn timeline

@marado@twtxt.net had a great idea for a browser extension: twt:// URI handling. It would provide a way to make pre-written twts like twitter.com/intent. Webmasters could create share buttons for Yarn.social using twt:// URIs and the extension would direct you to the web interface of a pod or to your standalone Yarn client (using a native messenger program).

The web client would be extended to support pre-written twts in this way once the extension hands it off to the web client.

This idea could be extended to reference twts, conversations, and feeds in a pod-agnostic way. Instead of linking to twtxt.net in the last paragraph, it could have been a special URI.

The original twt for reference:

@movq@www.uninformativ.de I have thought of different approaches, each have strengths and weaknesses. Mostly, I’d like to know what others think :-) In any case, I suppose I’d like to “extend” the hashtag generation API, so each blog post can have its own thread hash tag (like twts do). Then, “listing” the comments could be via querying a registry, and the “leave a comment” link could link to https://preconfigured-yarn.pod/?newtwt=@blogowner%20(#hashtag) or whatever link that would open that pod ready to create that new post if you’re logged in. Bonus points if you can configure more than one pod and it displays a dropdown; more bonus if we decide to implement twt:// uris letting twt clients listen to those (including a browser plug-in letting you say ‘open twt:// uris on https://my.pod’).

Yes, I might be overengineering.

[@marado@twtxt.net](https://twtxt.net/user/marado) had a great [idea](https://twtxt.net/conv/enmfm3a) for a browser extension: `twt://` URI handling. It would provide a way to make pre-written twts like [twitter.com/intent](https://developer.twitter.com/en/docs/twitter-for-websites/tweet-button/guides/web-intent). Webmasters could create share buttons for Yarn.social using `twt://` URIs and the extension would direct you to the web interface of a pod or to your standalone Yarn client (using a native messenger program). The web client would be extended to support pre-written twts in this way once the extension hands it off to the web client. This idea could be extended to reference twts, conversations, and feeds in a pod-agnostic way. Instead of linking to twtxt.net in the last paragraph, it could have been a special URI. The original twt for reference: > [@movq@www.uninformativ.de](https://www.uninformativ.de/twtxt.txt) I have thought of different approaches, each have strengths and weaknesses. Mostly, I’d like to know what others think :-) In any case, I suppose I’d like to “extend” the hashtag generation API, so each blog post can have its own thread hash tag (like twts do). Then, “listing” the comments could be via querying a registry, and the “leave a comment” link could link to https\://preconfigured-yarn\.pod/?newtwt=@blogowner%20(#hashtag) or whatever link that would open that pod ready to create that new post if you’re logged in. Bonus points if you can configure more than one pod and it displays a dropdown; more bonus if we decide to implement twt:// uris letting twt clients listen to those (including a browser plug-in letting you say ‘open twt:// uris on https\://my.pod’). > > Yes, I might be overengineering.

@mckinley I agree with the basic concept. In my client, I also parse out the URL of all hashtags, conversation threads, users and searches and replace them with internal links ("buttons") for the user.

However, please don't violate keyword hashtag labels (or the blake2b yarn-hash) by including random characters within them.

Referring to the blog post permalink in the subject might be an acceptable alternative, though (without the hashmark). It's much more opaque that durable that way. If you used free text search, you could post the URL anywhere within the twt body anyway.

@mckinley I agree with the basic concept. In my client, I also parse out the URL of all hashtags, conversation threads, users and searches and replace them with internal links ("buttons") for the user. However, please don't violate keyword hashtag labels (or the blake2b yarn-hash) by including random characters within them. Referring to the blog post permalink in the subject might be an acceptable alternative, though (without the hashmark). It's much more opaque that durable that way. If you used free text search, you could post the URL anywhere within the twt body anyway.

Labels Milestones

Ideas for brower extention/plug-in (Chrome, Firefox etc.) #951