friendica/friendica-directory
7
3
Fork 3
Code Issues 17 Pull requests Releases 17 Wiki Activity

Add push operation to directory sync targets #29

New issue
Open
opened 2019-03-31 12:45:43 +02:00 by AlfredSK · 2 comments
AlfredSK commented 2019-03-31 12:45:43 +02:00 (Migrated from github.com)
Copy link

If 'Friendica node X' is using global directory server A and that directory server has enabled directory sync target B the users of 'Friendica node X' should also appear on directory server B.

They don't appear and also 'Friendica node X' isn't listed on the server list of directory server B. I think this happens because the sync is 'pull only'. This leads to incomplete directories and the local directory admin can't do anything about it.

Example:
I'm running a Friendica node on venera.social (registration policy: open). The global directory is dir.libranet.de. dir.libranet.de has three sync targets. One sync target is the official directory dir.friendica.social.
The users of venera.social are listed on dir.libranet.de but not on dir.friendica.social. And venera.social is not on the server list of dir.friendica.social.

We should change that behavior to get consistent directory listings.

Directory 2.2.1
Friendica 2019.03

If 'Friendica node X' is using global directory server A and that directory server has enabled directory sync target B the users of 'Friendica node X' should also appear on directory server B. They don't appear and also 'Friendica node X' isn't listed on the server list of directory server B. I think this happens because the sync is 'pull only'. This leads to incomplete directories and the local directory admin can't do anything about it. Example: I'm running a Friendica node on venera.social (registration policy: open). The global directory is dir.libranet.de. dir.libranet.de has three sync targets. One sync target is the official directory dir.friendica.social. The users of venera.social are listed on dir.libranet.de but not on dir.friendica.social. And venera.social is not on the server list of dir.friendica.social. We should change that behavior to get consistent directory listings. Directory 2.2.1 Friendica 2019.03
MrPetovan commented 2019-03-31 14:43:58 +02:00 (Migrated from github.com)
Copy link

The sync directory target is currently pull only, there's no push operation yet.

The sync directory target is currently pull only, there's no push operation yet.
👍 1
MrPetovan commented 2024-04-30 02:37:22 +02:00
Owner
Copy link

The main directory currently has three directories in its poll queue, and all three are unreachable, this doesn't sound like priority work.

The main directory currently has three directories in its poll queue, and all three are unreachable, this doesn't sound like priority work.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
stable
v2.4.2
v2.4.1
v2.4.0
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v2.3.0
v2.2.1
v2.2.0
v2.1.1
v2.1.0
v2.1-rc2
v2.1-rc1
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0
Labels
Clear labels   
bug

Something isn't working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

No labels
bug
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: friendica/friendica-directory#29
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?