(I am sorry if this isn't the right place to report bugs about the viewer)
Some kind of a user profile/timeline is presented.
"Forbidden"
yes, the public gateways need some love. I think they get hammered with too many requests.
We should collect good caching configurations for nginx/apache/you name it to relife the nodejs processes from the load.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Now even the post is not available. Instead the following message is displayed:
User has not chosen to be hosted publicly
you need to opt-in to public web hosting. hmm, trying to find the bit in the code where that happens:
https://github.com/ssbc/ssb-viewer/blob/master/index.js (can't see it!)
aha, this post explains it %Fli0kemExYgucD1fLJm50qD5WptN6wZpsfIXddQpvNI=.sha256
to change you public web hosting, you have to write an about message with a publicWebHosting field.
using sbot (to install sbot, first install node with nvm, then run npm install -g scuttlebot)
sbot publish --type about --about "@your.public.id.here" --publicWebHosting
Doable, but why patchwork can't do it? Thank, you.
well, someone just needs to decide to add that ;) then do it
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Any one there? If this hasn't been implemented please keep it open with the low-hanging-fruit label for those who may want to start contributing.
@steelman
I've moved this issue to the Patchwork repository, maybe @mmckegg can comment on whether he wants publicWebHosting implemented (or how it should be done)?
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
@dominictarr
aha, this post explains it
%Fli0kemExYgucD1fLJm50qD5WptN6wZpsfIXddQpvNI=.sha256
Is this supposed to be publicly accessible? I get HTTP 400 when I try to open https://viewer.scuttlebot.io/%Fli0kemExYgucD1fLJm50qD5WptN6wZpsfIXddQpvNI=.sha256
@ksze https://viewer.scuttlebot.io/%25Fli0kemExYgucD1fLJm50qD5WptN6wZpsfIXddQpvNI%3D.sha256
Profiles have been implemented as well, e.g. https://viewer.scuttlebot.io/@6ilZq3kN0F+dXFHAPjAwMm87JEb/VdB+LC9eIMW3sa0=.ed25519
@christianbundy But it's still not doable via the Patchwork client, right?
Oops, that's correct. I forgot that I'd moved this issue from the viewer repo to the Patchwork repo.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
(to clarify for anyone reading along, it being assigned to me doesn't mean I'm going to implement it, it's just so stalebot doesn't close it again)
Most helpful comment
(to clarify for anyone reading along, it being assigned to me doesn't mean I'm going to implement it, it's just so stalebot doesn't close it again)