Notices tagged with oauth
-
Thoughts about #OAuth and #SimpleLogin.io in my #blog
https://www.sami-lehtinen.net/blog/simplelogin-tested-oauth -
@notclacke @dwmatiz There's an #OAuth bug in #GNU_Social (introduced in the last 2-3 years) that make #Mustard "unauthorized" to post. Since #AndStatus only connects by username password, it isn't affected. That's the primary reason I use AS. I should conect Mustard by username / password and use it as my main client again. Faster, more responsive, shows posts that AS never does.
-
@notclacke @dwmatiz There's an #OAuth bug in #GNU_Social (introduced in the last 2-3 years) that make #Mustard "unauthorized" to post. Since #AndStatus only connects by username password, it isn't affected. That's the primary reason I use AS. I should conect Mustard by username / password and use it as my main client again. Faster, more responsive, shows posts that AS never does.
-
@HerraBRE #Mastodon works with !GNUsocial as it is pretty well. There were some issues that @gargron raised with me, some of which I believe I fixed and some that I couldn't really figure out (some profile avatar update thing for example?)
Regarding RFC7033 (#WebFinger) it - since standardisation - only _requires_ a JRD (application/jrd+json). application/xrd+xml is just a bonus from !GNUsocial (voluntary according to spec).
The host-meta XRD is XML that because it was standardised before people who reinvent everything (JSON fanpeeps) started developing standards: https://tools.ietf.org/html/rfc6415
But since JRD and XRD are easily translatable between each other it doesn't really matter. And while #Mastodon doesn't use it, the /.well-known/host-meta endpoint is good for discovery unrelated to profiles, such as #OAuth endpoints etc. (so clients can auto-configure them).Tuesday, 18-Apr-17 20:55:51 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E in context Repeated by takeshitakenji -
@HerraBRE #Mastodon works with !GNUsocial as it is pretty well. There were some issues that @gargron raised with me, some of which I believe I fixed and some that I couldn't really figure out (some profile avatar update thing for example?)
Regarding RFC7033 (#WebFinger) it - since standardisation - only _requires_ a JRD (application/jrd+json). application/xrd+xml is just a bonus from !GNUsocial (voluntary according to spec).
The host-meta XRD is XML that because it was standardised before people who reinvent everything (JSON fanpeeps) started developing standards: https://tools.ietf.org/html/rfc6415
But since JRD and XRD are easily translatable between each other it doesn't really matter. And while #Mastodon doesn't use it, the /.well-known/host-meta endpoint is good for discovery unrelated to profiles, such as #OAuth endpoints etc. (so clients can auto-configure them). -
@andstatus Which seems really odd since #Mustard and Mustard{MOD} do !GNUSocial #OAuth without trouble. @lambadalambda
-
"I did play with Subversion which is why I tend to permeate governments nowadays. Though yeah, anyone could simply remake the group"
"It has been known to do but I suppose not having too much issues."
"I had to download the previous service doesn't work on mangoposter\.club with #OAuth."
"I didn't have touchpads."
"You do have a special place in order to watch Love Live sunshine..."
"Jack Layton and Steve Jobs died in the process of securing it. Got UFW and Fail2Ban set up in VirtualBox for me. May try that out soon actually." -
Managed to get Twidere to work on cherryposter.club with #OAuth.
-
@cassolotl That's a !GNUsocial question, not related to the !qvitter interface :)
I don't know what you mean with "authorise Twitter". If you're interested in posting from your quitter.se account _to_ Twitter, then there is a separate Twitter tab in the settings for that, on instances where it's enabled. (The #OAuth connections page is for doing the same, authorising third party apps/services, but with the quitter.se account) -
see RT @lnxw48 See Tim Bray’s take: (helped develop #OpenID version based on #OAuth) https://www.tbray.org/ongoing/When/201x/2014/05/03/Security-Farce
-
OK, some progress. now I get: "No suitable consumer keys stored locally, fetching latest list... Sorry, #IdentiCurse currently lacks the #API keys needed to support #OAuth with your instance (fediverse.com). If fediverse.com is a public instance, let us know which one it is (filing a bug at http://bugzilla.identicurse.net/ is the preferred way of doing so), and we'll add support as soon as possible."
-
anonymous #authentication with Public Key #cryptography (RSA keypairs, like SSH does): "Such a key repository could be local or remote and could have any number of mangement features (at least key creation and deletion) and perhaps also provide #APIs for existing authentication methods such as #OpenID and #OAuth." "Your private key could be used to #encrypt notifications which can be thrown into a giant #anonymous mixing bowl message store, or attached to an #API endpoint (or #PubSub node?) from which you can retrieve them and decrypt them using your private key" cc @question
-
Yeah, by supporting a system which doesn't support #federation with other systems. Go for it: "In this release #mediagoblin moves closer to federation by shifting our #oauth code to be pump.io compatible" http://mediagoblin.org/news/mediagoblin-0.5.0-goblin-force.html
-
@gryps75 did you already do: "Register an #OAuth client application to use with this instance of #StatusNet." ? it's in http://oracle.skilledtests.com/settings/oauthconnections (adapt link to your instance)
-
#identicurse works with and without #oauth in #statusnet! Which IC version are you using ? If you were using it before then your settings might be borked, see solution: http://oracle.skilledtests.com/notice/236090
-
#OAuth 2.0 editor resigns and takes name off spec http://bit.ly/LYf2wN
-
You know, despite #OStatus and #OAuth not working so well on RDN, I do like how it's significantly faster than #Identica and allows for longer posts.
Saturday, 05-Nov-11 18:13:08 UTC from web