Untitled attachment

Notices where this attachment appears

1. Adam Moore (LÆMEUR) (laemeur@gs.sdf.org)'s status on Tuesday, 27-Sep-2016 19:59:21 UTC Adam Moore (LÆMEUR)

   in reply to
   Technically, the OAuth tokens do get sent to http://aegn.us by the user's browser during the initial authorization of the app with your GS node, but the server does nothing with them. That server just hosts some files, there's no CGI code running on it.  The OAuth tokens are stored in the browser's localStorage, not on aegn.us.
   
   The domain is just a hook for launching the add-on. In the add-on's manifest, it basically says "if the user tries to visit aegn.us, load ÆGNUS into the current tab", and that's it. After you've authorized the add-on, there's no OAuth communication, no posts or activities, going to/through aegn.us; it's straight between the browser and your GNU social server.
   
   If that still seems dodgy, you can actually change the address that you want the browser to launch ÆGNUS on in the 'manifest.json' file in the add-on's folder. The "matches" property, which is set to ["*://aegn.us/*"] can be changed to any URL, even a file:// URL if you want ÆGNUS to launch when you visit a shortcut file or something. 
   
2. Claes Wallin (韋嘉誠) (clackemovedtoheldscalla@quitter.se)'s status on Tuesday, 27-Sep-2016 09:03:18 UTC Claes Wallin (韋嘉誠)

   in reply to
   @maiyannah @laemeur Yeah, but I can't find a way to use the plugin except going to http://aegn.us/ .
3. Adam Moore (LÆMEUR) (laemeur@gs.sdf.org)'s status on Sunday, 25-Sep-2016 07:29:59 UTC Adam Moore (LÆMEUR)
   My !gnusocial client, ÆGNUS, has been successfully reworked into a browser extension. If any brave souls want to give it a try (Firefox or Chrome), head over to http://aegn.us and give it a whack.