Notices tagged with webfinger
-
!gnusocial Someone is having trouble getting #webfinger going. https://is.gd/iryYac ... Does anyone have any ideas what the issue might be?
-
@tom79 I'm not sure what you're asking really. Do you want to know the endpoints for subscribing to a !fediverse user on !GNUsocial? If you do a #WebFinger lookup you'll get this: curl -s http://status.hackerposse.com/url/7584 | json_pp ... "href" : "http://status.hackerposse.com/url/18379", "rel" : "http://status.hackerposse.com/url/18380", ... The Atom feed, just li…
-
@HerraBRE !OStatus (via /.well-known/host-meta and LRDD such as #WebFinger) lets you create aliases on any given domain name. Your alias in !OStatus is just like #WebID, any random string. However, implementations seem to assume it should be a full WebFinger ID such as http://status.hackerposse.com/url/6735 (which is actually just the human-friendly way to address a l…
-
@bobjonkman It was pretty simple, but hacky. There's no current method of #WebFinger discovery for groups, so it iterates the locally known groups with the same 'nickname' and then joins the (first) one that has the same nickname and has its "mainpage" (in all known cases the group's HTML URL) on the same server as after the '@' + the poster is a member. This shouldn'…
-
@petercxy @astroprofundis It's more like #WebFinger (RFC7033) having that feature .)
-
@herrabre Aliases via #webfinger works with #mastodon as well afaik, try .@mmn@hethane.se
-
@maiyannah @archaeme @moonman #WebFinger is activated by default on all installs. Except "private" instances that don't support federation.
-
@gargron I'm thinking doing a #WebFinger lookup to the server you got the reply/whatever from. It's sure to know _what_ it was replying to. And that response can give you URLs for further discovery. See:
curl -s 'https://social.umeahackerspace.se/url/64012' |json_pp
-
@cyberczar @betafive @orobouros @bobjonkman2 @dragnucs I'm pretty sure there is some instance-blocking functionality already in !Gnusocial. Back when Evan's company was the primary host of !StatusNet, some spammer instances arose that started randomly mentioning people by their full #webfinger addresses. After a short time, this stopped happening. That tells me that the spammers' instances were blocked.
-
@rozzin #webfinger test
-
Awesome. My #WebFinger at hethane.se works like a charm: https://social.umeahackerspace.se/attachment/53300
-
@postblue it adds stuff to your #WebFinger output and parses stuff from remote Diaspora profiles, and it's supposed to also send proper Diaspora-flavoured salmon slaps (but doesn't yet)
-
I'm looking into #Diaspora protocol stuff for the !hackfest but I can't seem to do a non-hacky method of looking up the profile's feeds etc. based on their URL. No metadata is embedded in GET or HEAD data from, say, http://status.hackerposse.com/url/7423 and a #WebFinger lookup on their server doesn't reveal data unless I use an acct: URI (http://status.hackerposse.com…
-
@pettter What you want is just a service which takes an #WebFinger acct: URI and presents the information in a humanly understandable fashion. It will take you about 10 minutes to read how to do it, fetch the data, and dump it into HTML. Then it will take you 10 hours to make an appealing design and 10 years to make anyone else actually look at it.
-
@mmn, my install never knew which full acct URLs it was supporting; þe olde #StatusNet #XRD code just ignored the domain altogether, until you rewrote it as the #WebFinger plugin (2013-09-30 17:13:03 / a0e107f17f27bc1dfc49de2a4493a461213e782e).
-
@mmn, that's exactly it. I didn't say you were wrong to break my lousy #hack on #webfinger, just that you did :p
-
Also, @mmn, I think at some point you broke #gnusocial's support for my #webfinger redirector that mapped from acct:rozzin@hackerposse.com to http://status.hackerposse.com/rozzin :p
-
I wonder if we could have the "widget share thingie" solved by making /notice/new for _not_ logged in people present a #WebFinger ID box and the "notice text" box - which will then redirect to their home instance based on the WebFinger ID. !gnusocial
-
@roland That depends on the consumer. Some #OpenID implementations do /.well-known/host-meta + XRD lookup from a #WebFinger ID, but many less sophisticated ones might require (as per OpenID spec) your provider URL, i.e. the profile URL containing your nickname.
-
@hannes2peer @erkan I use https://social.umeahackerspace.se/mmn as my OpenID on various sites. ... maybe it won't work now that !qvitter overrides the profile page though (it doesn't have the proper <head> elements). Haven't tried in a while. Should work for sites which can lookup mmn@social.umeahackerspace.se though (as #LRDD + #WebFinger provides the OpenID endpoints).