Skip to main content

Missing in global directory

!iSurf Support

When does a new account generally become listed in the global directory? #newhere and thanks! Loving Friendica so far. I did try searching....

I'm still globally invisible :(

This is an interesting question since I am in the process of configuring a new Friendica node and not visible to the Fediverse yet. Is there something special I need to do?

@Shelenn Ayres to fully understand the problem, could you tell us where your node is physically located in the network?

I have not made the public yet. I did set it for approval only registration. When I log with the first account, I do not see anything when selecting the global community from the menu using Frio.

These are the user settings:


If you are the admin of your node, logon as admin (if different from your own username) and go to the admin panel under the section: "Policies" you will see this field. Populate this with a known Global Directory" (that interacts with other directories). Ideally choose one that is geographically close to you.


Two weeks and no listing for me in global directories. Could it be this?:

Two weeks and no listing for me in global directories. Could it be this?:

"Global Directory
This configures the URL to update the global directory, and is supplied in the default configuration. The undocumented part is that if this is not set, the global directory is completely unavailable to the application. This allows a private community to be completely isolated from the global network."

This really sounds like it could be it. Then again, I'm new here, so apologies if I seem a know-it-all.
@iSurf Support #isurf support

Three weeks. Not in global directory.

One month and still no entry in the global directory

Hello @Brian Millan I guess you've properly set to be listed in the global directory (GD). I think there are a range of factors that contribute to this problem.

Your node has quite a lot of users but is geographically far away in the network from the GD.

I'm hosting one of the global directories: I tried to manually increase the pulling interval from this GD (located in Southeast Asia) of your node (in North America). I noticed that most of the time, the pull is not successful and on the few occasions when it was successful it pulled only three profiles as specified by the current code.

I can see in my GD's database your own profile URL being scheduled for pulling (that means getting the relevant public information from your profile). But by the current rate of success it may take a very long time for new profiles on your node to be listed.

... show more

Thanks Andy, I see now. Distributed, decentralized systems are quite interdependent on each other and net conditions aren't they? (rhetorical). Of course this is all fun to me and I was interested to find out the reasoning. Adam said to me at one point, don't worry, it will find it's way in eventually. Thanks again!
@Andy H3
This entry was edited (6 months ago)

@Brian Millan actually we'd like to thank you for highlighting this issue by persistently following up on this. I'll be speaking to the developers of the GD code and will use your case to show the current shortfall in the current design. By the way, you're now listed in this global directory at least..

Hey @Andy H3 , thanks for following up on things this weekend.

This was an item on my to-do list to follow-up on, as my node reports to my own GD at and @Brian Millan hadn't shown up last time I checked, which was at least a couple of weeks after I mentioned it should show up eventually. I didn't expect it to take this long, however.

Perhaps we could open up a thread somewhere for a separate discussion about the issues you've had polling some of that information from my system. I'd like to know what kind of errors have been reported and why the hit rate would be so low. It would be something I would like to help see sorted out.

Hi @Adam Clark I think we should open an issue here:

I run this console command:
bin/console server-poll [url=][/url]
and ended up mostly getting "unsuccessful" responses (despite seeing your sever online) .

I was thinking about increasing the timeout settings, but I'm not sure yet if the source code actually permits this. I'd like to run some more tests and see how the poll responses compared to ping values.

One thing that is note worthy is that your GD in California [?] seems to experience a similar issue than my GD in Thailand or the main one in France, when polling from the isurf node in Canada . Definitely something we need to look it.

There's definitely something odd with that 'server-poll' console command itself, as it seems to bail on any error even though it's queued up a lot of work to do. So rather than skipping problems and moving on with the rest of it's work, it just seems to give up.

However, is that the same mechanism that is used for getting the profiles from the friendica nodes initially? I'm not sure what process is used to get the directory aware of a profile in the first place.