4 ms·
> By convention, the client looks under /satellite/ by default. If that path is already taken, place a satproto_root.json file at the domain root containing { "
by neilv 7mo ago
> By convention, the client looks under /satellite/ by default. If that path is already taken, place a satproto_root.json file at the domain root containing { "sat_root": "my-custom-repo" } — the client checks this first.
Would a `/.well-known/` be helpful here?
https://en.wikipedia.org/wiki/Well-known_URI https://en.wikipedia.org/wiki/Well-known_URI
- noman-land 7mo ago.poorly-known
- 9dev 7mo agoUnfortunately. It's a great solution to a problem lots of tools face. A pity that people trying to establish new standards aren't aware of it aparently.
- extraduder_ire 7mo agoI'm a little disappointed there's no standard for /.well-known/list that points to things made available under /.well-known/ on that domain. Doesn't need to be everything, just ones you want discoverable. Only other way to do it is trying every one you know.
- 9dev 7mo agoGood idea actually. You could just make /.well-known an index page
- chrismorgan 7mo agoAh, just like AT Proto when it was released, introducing compatibility hazards and security vulnerabilities by putting stuff in the root rather than in .well-known. Sigh.
- pfraze 7mo agoDid we?
- taintballs69 7mo ago[flagged]
- chrismorgan 7mo agoYes: https://news.ycombinator.com/item?id=35820368 https://news.ycombinator.com/item?id=35820368.
- pfraze 7mo agoAh, that's right. Forgot about that one.
- taintballs69 7mo agoNo. That is for the host/domain entirely not a specific stream. I might want several directories in the future, and even if I don't, I might want it separate from my .well-known robots.txt. Many, many reasons I can think of not to blend these. Bad idea.
- pavon 7mo agoThe current design has the same limitation of applying to the domain as a whole, but has potential name clashes that .wellknown would avoid.
- bschmidt2000 7mo ago[dead]