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

pixelfed proof doesn't work on pixelfed.de due to BIO character limitation #4

Closed
opened 2022年04月10日 23:22:21 +02:00 by meliache · 4 comments

According to the pixelfed instructions, have to paste the following snippet to my BIO:

This is an OpenPGP proof that connects my OpenPGP key to this Pixelfed account. For details check out https://docs.keyoxide.org/advanced/openpgp-proofs/
[Verifying my OpenPGP key: openpgp4fpr:FINGERPRINT]

I'm on the pixelfed.de instance and there I get the following error message when I do so:

The bio may not be greater than 125 characters.

Not sure if that's only the case in their instance and server version or also the case across other versions.

Obviously it's a limitation of having to hijack the bio. I was thinking about adding the keyoxide proof under my existing bio, but with the character limitation there's no way that there's place for that.

According to the pixelfed instructions, have to paste the following snippet to my BIO: ``` This is an OpenPGP proof that connects my OpenPGP key to this Pixelfed account. For details check out https://docs.keyoxide.org/advanced/openpgp-proofs/ [Verifying my OpenPGP key: openpgp4fpr:FINGERPRINT] ``` I'm on the pixelfed.de instance and there I get the following error message when I do so: > The bio may not be greater than 125 characters. Not sure if that's only the case in their instance and server version or also the case across other versions. Obviously it's a limitation of having to hijack the bio. I was thinking about adding the keyoxide proof under my existing bio, but with the character limitation there's no way that there's place for that.
Owner
Copy link

Didn't know there was a character limit on some instances. Could you try with just openpgp4fpr:FINGERPRINT? The docs probably shouldn't ask for the whole message to be added to the bio.

Didn't know there was a character limit on some instances. Could you try with just `openpgp4fpr:FINGERPRINT`? The docs probably shouldn't ask for the whole message to be added to the bio.

A shorter message works, including just a openpgp4fpr:FINGERPRINT string that you suggested. The default BIO message in the keyoxide pixelfed decs still exceeds the 125 character limit on of pixelfed.de, so I would add a comment to the docs, something like

Note

: Some pixelfed instances like pixelfed.de have character limit for the Bio, so feel free to shorten the Bio message as long as it contains openpgp4fpr:FINGERPRINT.

At the moment I use the 124 character BIO:

The following keyoxide.org proof connects my PGP key to this account:
[openpgp4fpr:546908C782383AD0E7D894EC1B8F95C8125DCE31]

(Sorry for being unresponsive on this issue for a long time, I'm not really active on codeberg except when I have an issue with a package hosted here and somehow I missed the notifications and this got forgotten until I logged in for an issue with another repository hosted here).

A shorter message works, including just a `openpgp4fpr:FINGERPRINT` string that you suggested. The default BIO message in the keyoxide pixelfed decs still exceeds the 125 character limit on of pixelfed.de, so I would add a comment to the docs, something like > **Note**: Some pixelfed instances like pixelfed.de have character limit for the Bio, so feel free to shorten the Bio message as long as it contains `openpgp4fpr:FINGERPRINT`. At the moment I use the 124 character BIO: > The following keyoxide.org proof connects my PGP key to this account: > [openpgp4fpr:546908C782383AD0E7D894EC1B8F95C8125DCE31] (Sorry for being unresponsive on this issue for a long time, I'm not really active on codeberg except when I have an issue with a package hosted here and somehow I missed the notifications and this got forgotten until I logged in for an issue with another repository hosted here).
Owner
Copy link

Sorry for being unresponsive on this issue for a long time

Been there, no worries.

The default BIO message in the keyoxide pixelfed decs still exceeds the 125 character limit on of pixelfed.de

Currently working on a big documentation overhaul, so I'll make sure to include this. In any case, I will no longer suggest people write that whole message, the fingerprint is sufficient.

> Sorry for being unresponsive on this issue for a long time Been there, no worries. > The default BIO message in the keyoxide pixelfed decs still exceeds the 125 character limit on of pixelfed.de Currently working on a big documentation overhaul, so I'll make sure to include this. In any case, I will no longer suggest people write that whole message, the fingerprint is sufficient.

@yarmo wrote:

Currently working on a big documentation overhaul, so I'll make sure to include this. In any case, I will no longer suggest people write that whole message, the fingerprint is sufficient.

Closing this one since the docs overhaul was completed a long time ago and since we don't recommend adding verbose snippet to the bio/description anymore (see https://docs.keyoxide.org/service-providers/pixelfed/). 🎉

@yarmo wrote: > Currently working on a big documentation overhaul, so I'll make sure to include this. In any case, I will no longer suggest people write that whole message, the fingerprint is sufficient. Closing this one since the docs overhaul was completed a long time ago and since we don't recommend adding verbose snippet to the bio/description anymore (see <https://docs.keyoxide.org/service-providers/pixelfed/>). 🎉
Sign in to join this conversation.
No Branch/Tag specified
main
new-claim-eveonline-143
add-guide
No results found.
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
3 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#4
Reference in a new issue
keyoxide/keyoxide-docs
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?