Phanpy decoding webfinger URLs
- Dominant language
- JavaScript
- Stars
- 1.5k
- Forks
- 186
- Avg merge
- 1d 36m
- Merged PRs (30d)
- 11
Description
### Site
phanpy.social
### Version
2024.12.28.119d4b0
### Instance
social.hardfork.ngo
### Browser
- Safari on Sonoma
### Bug description
When Phanpy fetches a webfinger account that resolves to a URL encoded string, it decodes the URL before fetching the actor. For example, if the actor resolves to `https://example.com/test%253example`, Phanpy will fetch `https://example.com/test:example` instead of fetching the encoded URL verbatim.
### To reproduce
_No response_
### Expected behavior
Fetch the encoded URL verbatim.
### Other
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing Phanpy’s WebFinger account-resolution flow to the point where the actor URL is fetched, using the example URL containing encoded characters. Confirm the current decoding behavior and make the fetch preserve the encoded URL verbatim; done means the actor request uses the original encoded URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100