- Press CTRL-H ( ⌥⌘F on Mac ).
- Press ALT-R ( ⌥⌘R on Mac ).
- Type
_([a-zA-Z])
. - Press TAB and type
$1
. - Press ALT-ENTER ( ⌥ENTER on Mac ).
- Press F1 and type
upper
, then press ENTER. - Press CTRL-ALT-ENTER ( ⌥ENTER on Mac ).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// ==UserScript== | |
// @name LingoMarker | |
// @namespace http://tampermonkey.net/ | |
// @version 0.22 | |
// @description Highlight and store selected words via LingoMarker backend | |
// @author 1token & AI Assistant | |
// @match https://*.reuters.com/* | |
// @match https://*.apnews.com/* | |
// @match https://apnews.com/* | |
// @match https://*.bbc.com/* |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// ==UserScript== | |
// @name Lingea Dictionary with Highlight | |
// @namespace http://tampermonkey.net/ | |
// @version 1.162 | |
// @description Highlight and store selected words, open in Lingea dictionary | |
// @author 1token | |
// @include https://*.reuters.com/* | |
// @include https://*.apnews.com/* | |
// @include https://apnews.com/* | |
// @include https://*.bbc.com/* |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// ==UserScript== | |
// @name Lingea Dictionary | |
// @namespace http://tampermonkey.net/ | |
// @version 1.10 | |
// @description Open selected word in Lingea dictionary on any device | |
// @author Your Name | |
// @match *://*/* | |
// @grant none | |
// ==/UserScript== |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// ==UserScript== | |
// @name Lingea Dictionary Lookup | |
// @namespace http://tampermonkey.net/ | |
// @version 1.0 | |
// @description Adds a context menu item to translate selected text using Lingea dictionary. | |
// @author You | |
// @match *://*/* | |
// @grant GM_registerMenuCommand | |
// @grant GM_openInTab | |
// ==/UserScript== |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Let's say Alice has a video from the conference and she wants Bob to see it. | |
Prerequisites: | |
• Alice and Bob use independent, not federated providers. | |
• They both have signed-in into their Claims Provider and supplied some necessary information. | |
• Alice has set up her email provider to auto-forward emails from a specified Claims Provider email address e.g. claims@foo.com to another specified Claims Provider address e.g. dkim.signed.claims@foo.com. | |
• Alice knows where Bob's RS is. | |
• Alice has created a resource with her video and has given Bob access to this file. | |
• Bob has created a shared resource “Inbox” where any client that can demonstrate the ability to perform delegated tasks on behalf of RqP can create a small file. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Non-Interactive Claims Gathering / Verified RqP Client (UMA Deep Dive) | |
Assume these pre-reqs: | |
• RO has shared a link with RqP. | |
• RO has set up his AS to anyone who can demonstrate control of RqP. | |
• RqP has presented his claims via the Webfinger (or Webfist as a fallback) protocol. One of the claims contains the URI of RqP's Client. | |
Flow steps: | |
1. The RqP uses a client to access an UMA protected resource at the RS. | |
2. Without an RPT, the RS returns 401 with a permission ticket and the URI of the AS. |