I tried to check your replies from my "hack platform" and while
requesting the host-meta file (from
http://eschenauer.be/.well-known/host-meta) I got HTTP/1.1 503 Service
Temporarily Unavailable
Let me know when all is up again and I'll give it another run.
Cheers,
--
Tuomas
Let me know when all is up again and I'll give it another run.
On 16 March 2011 10:56, Laurent Eschenauer <laurent.e...@gmail.com> wrote:
> Hello Tuomas,
>
>>
>> Let me know when all is up again and I'll give it another run.
Discovery seemed to work nicely and just "slaped" you (endpoint
http://eschenauer.be/salmon/user/laurent). Did you get it?
On 16 March 2011 10:56, Laurent Eschenauer <laurent.e...@gmail.com> wrote:
> Back online, thanks for letting me know how it works for you. Can you
> already confirm me that you are receiving slaps from identi.ca ?
Yes I am. (http://www.lobstermonster.org/profile/koski)
On 16 March 2011 10:56, Laurent Eschenauer <laurent.e...@gmail.com> wrote:
> You can also ping me by IM: I'm eschnou on freenode, and laurent.eschenauer
> at gmail.com on Gtalk.
Added the gmail one.
Cheers,
--
Tuomas
Discovery seemed to work nicely and just "slaped" you (endpointhttp://eschenauer.be/salmon/user/laurent). Did you get it?
On 16 March 2011 11:28, Laurent Eschenauer <laurent.e...@gmail.com> wrote:
>> Discovery seemed to work nicely and just "slaped" you (endpoint
>> http://eschenauer.be/salmon/user/laurent). Did you get it?
>
> Got your ping ! Thank you. So, it works, but strangely not from identi.ca,
> i'll have to dig deeper.
> I failed at verifying your signature, but that is another story. I captured
> the packet and will try to debug this later. One of the reason may be that
> you are not removing padding when base64url encoding the pieces of M (this
> has changed lately).
yeah, this might be possible. I have not touched it so much since the
SWAT0 times. My plan is to update all of these in the near future now
when I have a better idea how the architecture should be done.
On 16 March 2011 11:28, Laurent Eschenauer <laurent.e...@gmail.com> wrote:
>> > Can you
>> > already confirm me that you are receiving slaps from identi.ca ?
>>
>> Yes I am. (http://www.lobstermonster.org/profile/koski)
>
> Hmm.. will look into their source code to see if I miss something.
It's quite messy (sorry!) so you might loose time there (the minime
source i mean).
Maybe it would be the best to ask directly from the statusnet-dev mailing list.
Cheers,
--
Tuomas
Laurent,
We did an upgrade from StatusNet 0.9.6 to 0.9.7beta a few weeks ago. I'm testing unsolicited slaps (no subscription) across StatusNet sites and seeing the same problem.
I'll see if we can get that fixed ASAP.
-Evan
Laurent,
We did an upgrade from StatusNet 0.9.6 to 0.9.7beta a few weeks ago. I'm testing unsolicited slaps (no subscription) across StatusNet sites and seeing the same problem.
One thing (potentially) holding things up is - if you've moved the
location of your salmon endpoint at all StatusNet caches that value
very aggressively. I've found running a local StatusNet instance is
super helpful for debugging stuff like this.
There are a few other places where discovery will fail if certain bits
of info don't match - which are tough to debug remotely ...
--
James Walker :: http://walkah.net/
> On further investigation, StatusNet 0.9.7 seems to be working ok among
> itself; at least we can find no problems doing several ad-hoc tests both
> within our hosted cluster and between that and a StatusNet 1.0.x test site.
One thing (potentially) holding things up is - if you've moved the
location of your salmon endpoint at all StatusNet caches that value
very aggressively. I've found running a local StatusNet instance is
super helpful for debugging stuff like this.
Cool - keep up the great work! I'm excited to see node-ostatus coming along :)
Yeah that can do it -- I'll think about how to fix our end to rerun discovery on failure, should help in such situations.
- brion
- I see in my logs a webfinger request followed by a request for the user atom streamBut I never see any incoming salmon request, and don't see other errors.
On 18 March 2011 09:26, eschnou <laurent.e...@gmail.com> wrote:
>> - I post from the identi.ca web UI a message with mention of
>> @lau...@eschenauer.be
>> - I see in my logs a webfinger request followed by a request for the user
>> atom stream
>> But I never see any incoming salmon request, and don't see other errors.
>
> Problem solved.
Good news!
On 18 March 2011 09:26, eschnou <laurent.e...@gmail.com> wrote:
>Having my own statusnet instance and stepping through the
> code did help. I solved my problem by adding the following link in my
> activities atom stream:
> <link href="http://eschenauer.be/salmon/user/laurent"
> rel="http://salmon-protocol.org/ns/salmon-replies"/>
>
> I thought that this rel value was deprecated :-) Any plans to switch/support
> rel='salmon' ?
> Looking in more details in the status.net discovery flow, I have another
> issue: When you do a webfinger discovery, if a feed is discovered, then
> statusnet switch to a feed based discovery and ignore the content of the
> XRD. This explains why my salmon links exposed in my XRD never got
> discovered.
> http://gitorious.org/statusnet/mainline/blobs/master/plugins/OStatus/classes/Ostatus_profile.php#line1651
Dose this "service" discovering your data correctly:
http://www.madebymonsieur.com/ostatus_discovery/ ?
On 18 March 2011 09:26, eschnou <laurent.e...@gmail.com> wrote:
> I hope to have some time over the weekend to look into signatures.
I start to work on this the coming weeks too, so all the feedback is
much appreciated.
Cheers,
--
Tuomas