If enabled, members will automatically login to an ejabberd server that has to be installed on this machine with synchronized credentials via the "auth_ejabberd.php" script.
Delete everything. Give clones a chance to catch up (2 hours would be best) and then try a normal connection sequence with the regular flow.
I think what's happening is although I don't connect (and get an error message) you, at least see a connection request.
joltrast still hasn't confirmed that it happened again. if it does i think it's my hub's fault. i'll start this over again anyway, better than trying to debug why it doesn't federate properly. i have two clones, so there's no real loss.
I just tried to connect to you now. Pressing connect from the profile pic does nothing. trying toconnect from your profile page reproduces the original error.
I ran into that on hub . toot .cat, when trying to add a hubzilla contact. But it still seemed to add the contact anyway.
Text you want to hide.
Vader is Lukes father!
But I don't think the spoiler tags federate well.
// The photo cache default is 1 day to provide a privacy trade-off, // as somebody reducing photo permissions on a photo that is already // "in the wild" won't be able to stop the photo from being viewed // for this amount amount of time once it is in the browser cache. // The privacy expectations of your site members and their perception // of privacy where it affects the entire project may be affected. // This has performance considerations but we highly recommend you // leave it alone.
Also not seeing your comments Max
This can be the common federated network issue when updates can be delivered with a delay depending on a number of factors.
@Joltrast There is nothing we can do with this. Decentralisation have not only positive sides but negative as well.
When one hub is showing 15 comments and the other 7, it's a problem especially if it's a heated conversation :)
one hub has 500 users with a lot of queues....another has 25 users with a queue of just 5 posts/comments ...it's all very relative.I've tried everything in 7 or more years, from diaspora to mastodon ... and everything in between.I have seen millions of problems with these distributed decentralized networks.in diaspora I saw shocking things about the delays of comments and posts, and disappearance...in mastodon, gnusocial I saw that people and comments do not even appear in certain nodes...it's a complicated life.
Diaspora communications are notoriously unreliable and receiving profile update messages (indeed any messages) are pretty much random luck. We'll check the timestamp of the xchan_name_date at a higher level and refresh this record once a month; because if you miss a profile update message and they update their profile photo or name you're otherwise stuck with stale info until they change their profile again - which could be years from now.
They are both Hubzilla accounts. Neither of them show my diaspora profile correctly. The hubs are Zotum.net (this one) and hub.toot.cat
I can fix this in Hubzilla code but don't sure if we need it because as I quoted above the workaround already exists.
the problem was found and has a fix
Don't sure that it was exactly the same issue fixed but very close to it for sure
Hi! It's good to see you guys! Make sure to vote in the end of this video :3 Spotify, iTunes, google, etc ready! https://open.spotify.com/artist/7CSdLmKke7VF...