Various small improvements to the README #110
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: friendica/friendica-directory#110
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "waldyrious/friendica-directory:readme-tweaks"
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?
Minor tweaks to a couple passages in the README :)
@ -3,3 +3,3 @@
This standalone software is meant to provide a global public directory of [Friendica ](https://github.com/friendica/friendica) profiles across nodes.
This is an opt-in directory, meaning that each node can choose not to submit its profiles to global directories, and each user can individually choose not to be submitted.
This is an opt-in directory, meaning that each node can choose not to submit its profiles the global directory, and each user can individually choose not to be submitted.
While the Friendica project runs a global directory, it isn't meant to be the only global directory. Still, a node can only publish to a single global directory, which doesn't need to be the one ran by the Friendica team.
I would change the language to "to a global directory" instead.
Hmm, I did wonder if that was the intent, but found it weird for there to be multiple "global" directories, so I picked the phrasing that seemed more intuitive.
Would something like this be acceptable?
That's good too, the reason for the "global" qualifier is that each node maintain its own "local" directory of local users (at
/directory
on your node)Oh, thanks for the context! Yeah, I can see the logic, but indeed the term has the unfortunate connotation of implying there's a single overall aggregate directory. I'll try to incorporate this info in the README without using the word "global" :)
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.