9
13
Fork
You've already forked keyoxide-docs
23

Discourse: attempt to have a more helpful warning #25

Merged
yarmo merged 3 commits from Aminda/keyoxide-docs:discourse into main 2024年03月04日 19:42:37 +01:00
Contributor
Copy link

This is the information I wish I had earlier, while it was known.

This is the information I wish I had earlier, while it was known.
discourse: attempt to have a more helpful warning
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
27985cc15d
 
This is the information I wish I had earlier, while it was known.
Author
Contributor
Copy link

I am uncertain if this is technically correct since I can access https://community.e.foundation/u/aminda/ in private browsing mode without having trust level basic, but then again Keyoxide fails to verify it and my verification with PrivacyGuides Discourse started working upon trust level bumb, so I think this would at least be a step in the correct direction.

I am uncertain if this is technically correct since I can access `https://community.e.foundation/u/aminda/` in private browsing mode without having trust level basic, but then again Keyoxide fails to verify it and my verification with PrivacyGuides Discourse started working upon trust level bumb, so I think this would at least be a step in the correct direction.
Author
Contributor
Copy link

I just intentionally browsed community.e.foundation for a bit to get trust level 1 basic and that made the proof verification succeed, so I am now confident that this PR is correct.

I just intentionally browsed community.e.foundation for a bit to get trust level 1 basic and that made the proof verification succeed, so I am now confident that this PR is correct.
discourse: _your Discourse account_, _on trust level_, _the proof verification_
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
fcc740b2cb
@ -8,3 +8,3 @@
+++
<p class="warning">Note: Claim verification does not work on some Discourse instances, depending on how they are configured.</p>
<p class="warning">Note: Your Discourse account must be at least on trust level 1 (Basic). If your profile page isn't accessible in private browsing mode, <a href="https://codeberg.org/keyoxide/keyoxide-web/issues/160">the Discourse instance configuration may prevent the claim verification from working.</a></p>
Member
Copy link

May I suggest we also link to the Discourse docs topic that explains the concept of trust levels?

May I suggest we also link to the [Discourse docs topic](https://meta.discourse.org/docs?topic=90752) that explains the concept of trust levels?
Author
Contributor
Copy link

Done

Done
Aminda marked this conversation as resolved
Discourse: link trust levels documentation in the warning
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
ci/woodpecker/pull_request_closed/woodpecker Pipeline was successful
ci/woodpecker/push/woodpecker Pipeline was successful
0cad5623cf

As promised, I ran the current wording through my local LanguageTool server and it applauded you for excellent wording.

Sadly I'm lacking the permissions to squash and merge this PR as you wished.

As promised, I ran the current wording through my local LanguageTool server and it applauded you for excellent wording. Sadly I'm lacking the permissions to squash and merge this PR as you wished.
Owner
Copy link

Great information to add, I was unaware of these trust levels!

Great information to add, I was unaware of these trust levels!
Sign in to join this conversation.
No reviewers
Labels
Clear labels
Contribution welcome
Get started contributing here
Good first issue
Good if you are new to the project or to open source contributions
Impact
External
 Affects the people using the project
Impact
Internal
 Affects on the people working on the project
Priority
Critical
 Work on right now
Priority
High
 Work on at earliest convenience
Priority
Low
 Work on in spare time
Priority
Medium
 Work on regularly
Review
Duplicate
 Already exists
Review
Off Topic
 Does not fall within the scope of the repo/project
Status
Backlog
 Is not being worked on yet
Status
Blocked
 Is waiting on something or someone
Status
Completed
 Is done
Status
In Progress
 Is being worked on
Status
Investigating
 Is waiting on research or questions
Status
Needs Decision
 Is waiting on a decision by the devs/contributors
Status
Needs Info
 Is waiting on additional information before it can be solved
Status
Needs Triage
 Is new issue that needs reviewing
Status
Testing
 Is being checked and verified
Status
Waiting For Review
 Is waiting on reviewers to approve
Status
Won't Fix
 Won't be fixed
Type
Bug
 Related to something not working as intended
Type
CI
 Related to continuous integration
Type
Documentation
 Related to documentation
Type
Enhancement
 Related to a new feature or an improved one
Type
New Claim
 Related to a new identity claim/proof
Type
Security
 Related to security
Type
Tests
 Related to code tests
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 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
keyoxide/keyoxide-docs!25
Reference in a new issue
keyoxide/keyoxide-docs
No description provided.
Delete branch "Aminda/keyoxide-docs:discourse"

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?