No Branch/Tag Specified
feed-list
main
exponential-backoff-feed-fetch
twt_hash_v2
xuu-patch-1
variable_hash_encoding
logout_under_settings
profile_ui
lists_ui
fix_vlun_enumerate_users
footer_overflow
authheadergroups
new_reply_fork_icons
sandstorm_support
Fix_missing_id_for_Poderator
css_icon_Amoled
uiux_darch_backup
uiux_darch
fix_register_spam
ullarah-newtextarea
disable_daily_stats
0.15.1
0.15.0
0.14.0
0.13.1
0.13.0
0.12.0
0.11.0
0.10.0
0.9.0
0.8.0
0.7.4
0.7.3
0.7.2
0.7.1
0.7.0
0.6.2
0.6.1
0.6.0
0.5.0
0.4.1
0.4.0
0.3.0
0.2.0
0.1.0
0.0.12
0.0.11
0.0.10
0.0.9
0.0.8
0.0.1
0.0.2
0.0.3
0.0.4
0.0.5
0.0.6
0.0.7
Labels
Clear labels
Activity Pub integration
Something isn't working
Improvements or additions to documentation
This issue or pull request already exists
New feature or request
Good for newcomers
Extra attention is needed
This doesn't seem right
Further information is requested
This will not be worked on
Apply labels
activitypub
Activity Pub integration
area/backend
area/ci
area/cli
area/desktop
area/hosting
area/mobile
area/packaging
area/ui
browser/chrome
browser/edge
browser/firefox
browser/safari
bug
Something isn't working
dependencies
discussion
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
on hold
question
Further information is requested
security
stale
tests
wontfix
This will not be worked on
No Label
activitypub
area/backend
area/ci
area/cli
area/desktop
area/hosting
area/mobile
area/packaging
area/ui
browser/chrome
browser/edge
browser/firefox
browser/safari
bug
dependencies
discussion
documentation
duplicate
enhancement
good first issue
help wanted
invalid
on hold
question
security
stale
tests
wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Blocks
#388 [Yarn.social]: Move and merge Hosting service
yarnsocial/yarn
Reference: yarnsocial/yarn#590
Reference in New Issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
Work-in-proggress branch:sandstorm_support
yarnd
now runs in Sandstorm 🥳For the first part (Authentication and Authorization) we probabpy need a custom "Session" manager if
SANDSTORM=1
(from the environment) and to implement Auth handling provided by Sandstorm as trusted headersAfter this the rest should be pretty straight forward 👌
Yeah, I think pulling in auth is probably the one thing that really needs one to understand the specific app code in question.
For web publishing I need to check on the status of the getPublicId little app, but that will get built entirely in the sh scripts, and shouldn't impact your code at all, until you call that to get the URL for DNS config. The proxy is similar: We can set everything up entirely in sh scripts and then all you have to do is proxy your outgoing network requests to it. (Which is arguably a decent standard feature for apps to support anyways, I think.)
Have you had any inspiration on the account integration portion by chance? I am excited about this still.
Ahh yes I think I know how to do this, but I think I had a question of you actually -- mostly to seek your opinion. Let me finish up some refactoring work and then get back to this 👌
Hey, I wanted to follow up on this and see where it sat on your radar. I don't think I ever found out what the question was. =) Decentralized social has had a bit of a resurgence because of recent Twitter news, and Sandstorm has some exciting stuff in the pipeline as well.
Hey! This is still on our radar! But we need more man power :)
Do you have anyone in the Sandstorm community that might be able to work with me on this? I need help!
I think I can add a lot of the Sandstorm-specific stuff at least as an external components run by the package, if we hit a blocker I can probably ask Ian for help (he's one of our leads who does a fair bit of Go, but his todo list is very large), but probably the big bits on yarnd itself would be ensuring we can configure yarnd on first run totally within the web interface, and making sure we can point the requests for outbound servers to go through a proxy.
That would be a big help! The part I got stuck with was users and how users should be authenciated and passed to
yarnd
too. We may run into that again too, I'm not sure, been a while since I looked at the standstorm branch I had in progress...Do you have any support for different types of authentication providers presently or is it just login/password?
Sandstorm provides both a unique (i.e. authenticated) ID as well as a "preferred handle" i.e. username as HTTP headers with every request. In theory, you could even just patch the handle into their username and their ID into their password, though we don't guarantee the handle is unique, so someone who chose the same handle would fail to work in that case.
So the ideal case on Sandstorm would be that if not logged in, check the header, and use it to log them in, and if they do not exist, create them using that header info.
That's the conclusion I ended up with as well. Which means (to answer your first question) in order to support Sandstorm properly we'd have to implement a SandstormAuth. Currently we have support for Username/Password, MaglinkAuth (Email Login) and soon IndieAuth login.
Yeah, I think it'd be best to properly handle Sandstorm auth integration the same way to handle other types of authentication, so you don't have to explicitly think about Sandstorm when doing future code changes.
Are your other auth providers implemented in single files or single PRs or anything such that I could see what the scope of work is to add an auth provider to yarn?
Yes most logic is contained here
Okay, so I have this building and made a couple changes you'll want to also include:
in ./preflight.sh, fix the shebang to work in newer distros
in .sandstorm/Vagrantfile, switch to Debian bullseye
in .sandstorm/setup.sh, let's bump the Go version
also, we need
make
(for building) andgnupg
(for signing) so add them to setup.sh tooHere's my poor man's pull request, @prologic
Reopening for tracking. Second post caused this stream of stack trace:
Current progress merged in (minus a few trivial ones):
Proxy auth support
54f946613b
Sandstorm packaging support
cac89f130e
Fix proxy auth
3a881be264
Use proxy auth as middleware
60acef3ddd
The next part of this project depends on me. I need to figure out how to get web publishing figured out, which requires I figure out how to do web publishing myself first.
Okay, so more details on that stack trace:
If I post some things, and then click "Discover", the UI fails to load for me, and when I reload it, my old posts appear to be gone. But they still exist in the feed txt file. I posted three more times, and then hit Discover, and they also are now gone. ...But all five still are in the feed txt file.
Fixed in
f5a9213e
Fixed in
f5a9213e