Show Navigation
Notices tagged with webfinger
-
@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 https://social.umeahackerspace.se/.well-known/webfinger?resource=acct:mmn@social.umeahackerspace.se | json_pp
...
"href" : "https://social.umeahackerspace.se/api/statuses/user_timeline/2.atom",
"rel" : "http://schemas.google.com/g/2010#updates-from",
...
The Atom feed, just like an PubSubHubbub enabled feed, has metadata for the subscription endpoint:
curl -s https://social.umeahackerspace.se/api/statuses/user_timeline/2.atom | grep rel=.hub
<link href="https://social.umeahackerspace.se/main/push/hub" rel="hub"/>
To this hub you do the subscription dance for the feed URI (i.e. the Atom link from before): https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html
The activitystreams signalling - please note that this is optional, that is something else.
-
@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 acct:mmn@hethane.se (which is actually just the human-friendly way to address a lookup endpoint).
The main issue is that the aliases/redirects need to live for as long as people remember the old identifier. Which is likely to be indefinitely.
-
@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't cause issues because people don't join malicious groups. Because people always do the right thing. Right?
-
@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 sta…
-
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-ha…
-
@pettter What you want is just a service which takes an #WebFinger acct: URI and presents t…
-
I wonder if we could have the "widget share thingie" solved by making /notice/new for _not_…
-
@roland That depends on the consumer. Some #OpenID implementations do /.well-known/host-met…
-
@hannes2peer @erkan I use https://social.umeahackerspace.se/mmn as my OpenID on various sit…
-
@mcscx2 there's the #SubMirror plugin which lets you replicate RSS/Atom and some non-workin…
-
If there is a callback URL delivered (which is not necessarily the notice's URI), such as a…
-
URL for notice should not have to be the same, but there should be a common lookup method (…
-
Cool that !sdf is running a !gnusocial node. But if it's run as a subdirectory, I highly re…
-
@mcscx (also, what should be shown is local part of #WebFinger acct: uri and then somehow li…