!QmwrMtJYbkKKLHCnlr:federator.dev

Socialhome

23 Members
https://socialhome.network || Servers: https://the-federation.info/socialhome || Code: https://git.feneas.org/socialhome/socialhome || Docs: http://socialhome.readthedocs.io9 Servers

Load older messages


Timestamp Message
29 Mar 2020
13:47:27@jaywink:federator.devjaywinkor, maybe I've nuke-blocked the user
13:47:29@hankg:feneas.orghankgReplies in general yes but specific replies may not
13:47:52@hankg:feneas.orghankgI forget what the rationale was for that but it made zero sense to me even after it was explained
13:48:05@jaywink:federator.devjaywinkin this case how I've implemented socialhome they should be delivered
13:48:23@jaywink:federator.devjaywinkie "if the sender got the original, socialhome will relay replies there too"
13:48:24@hankg:feneas.orghankgOh good you hypothetically fixed it then?
13:48:38@hankg:feneas.orghankgIt does that outside the federating protocol?
13:49:25@jaywink:federator.devjaywinkthe protocol relies on participation entities which socialhome doesn't implement :D so, internally we just send replies to anyone who would have got the original post delivered to
13:49:52@jaywink:federator.devjaywink participation entries are important on jumping on to posts which is why we should add the, but just haven't had time
13:50:00@jaywink:federator.devjaywinkbut in this case Alain has received the original
13:50:07@jaywink:federator.devjaywinkand socialhome has no way of unsubscribing :D
13:50:42@jaywink:federator.devjaywink could you give more details on the delivery issues you refer to hankg ?
13:50:55@alain:zenfolie.orgAlainHere's the diasp.org link: https://diasp.org/posts/65fd2362-e4a5-48f6-8ef1-0699190d8642
13:51:53@hankg:feneas.orghankg
In reply to @jaywink:federator.dev
could you give more details on the delivery issues you refer to hankg ?
When I was implementing the API I was pulling posts from a secondary server running the software. I noticed that a post that had a dozen comments or so when viewed on diasp.org only had three or four on the secondary server. I assumed it was a bug
13:52:01@jaywink:federator.devjaywink Alain: I have all the replies. You have none?
13:52:16@hankg:feneas.orghankgA bug in the federating protocol...however in the IRC discussion with the core dev team they said it was expected and explained why
13:52:20@alain:zenfolie.orgAlainI have none.
13:52:29@jaywink:federator.devjaywink
In reply to @hankg:feneas.org
When I was implementing the API I was pulling posts from a secondary server running the software. I noticed that a post that had a dozen comments or so when viewed on diasp.org only had three or four on the secondary server. I assumed it was a bug
Sure but there could be a ton of reasons for that, none of which might be related to the protocol
13:52:48@hankg:feneas.orghankgI think of things from a UX point of view and disagreed with their assessment but it was a moot point
13:53:03@jaywink:federator.devjaywinkfor example, diaspora does relaying from the original server. If that author is blocking the commenter, those replies will only be on the server that did the reply
13:53:06@jaywink:federator.devjaywink * for example, diaspora does relaying from the original server. If that author is blocking the commenter, those replies will only be on the server that did the reply
13:53:28@hankg:feneas.orghankgIt wasn't a case of blocking or limiting or something
13:53:44@hankg:feneas.orghankgthey had an explanation but to me it sounded like "it's a feature not a bug" rationalizations for bad UX
13:54:12@jaywink:federator.devjaywink yeah difficult to say without exact details. AP is the (current) future anyway so shrug ;)
13:54:45@hankg:feneas.orghankgYup
13:55:10@jaywink:federator.devjaywink Alain: not even my one reply there?
13:55:22@alain:zenfolie.orgAlainNope.
13:58:17@jaywink:federator.devjaywink

well, these errors don't look very nice:

2020-03-29 02:05:25,237 base 23497 140627180594944 ['handle_send - failed to generate payload for https://socialhome.zenfolie.org/u/alain/, https://socialhome.zenfolie.org/receive/public/: Traceback (most recent call last):\n  File "/home/jasonrobinson/venv/src/federation/federation/outbound.py", line 174, in handle_send\n    payload["to"] = [NAMESPACE_PUBLIC]\n  File "src/lxml/etree.pyx", line 743, in lxml.etree._Element.__setitem__\nTypeError: Cannot convert list to lxml.etree._Element\n']
14:00:10@jaywink:federator.devjaywinksigh, that must have been relatively recent regression when I was trying to fix (and probably fixed?) notifications on mastodon side not triggering because they have this weird requirement that "oh if you do a mention we won't actually show it to the user unless they're also in the right addressing group", because why not
14:00:27@jaywink:federator.devjaywink Alain: thanks for notifying, will try patch today

There are no newer messages yet.


Back to Room List