session-ios
session-ios copied to clipboard
oxen-io
[BUG] [Minor] Names cropped
Code of conduct
- [X] I have read and agree to adhere to the Code of Conduct
Self-training on how to write a bug report
- [X] I have learned how to write a bug report
Is there an existing issue for this?
- [X] I have searched the existing issues
Current Behavior
Too long names go outside of the screen, and thus are cropped.
I'm afraid that setup won't work with current Session because of how onion requests work: the request bounces through the Oxen network, then the last hop is responsible for resolving the SOGS address and sending the request to it (and then relaying the response back). Because that last hop is a random service node, it's very unlikely that .onion resolution will work (unless the node just happens to have working Tor connectivity).
We have some plans to support direct Lokinet connections in Session later this year; at that point it might be easier to make Session also recognize .onion domains (but I am not a Session dev, and this is pure speculation on my part).
Cc @mpretty-cyro for comments.
alright, thank you! would be good to have this so you can have an anonymous open group.
supporting .onion would require all session clients to have a tor client and such is highly unlikely to happen as we have been dragging our feet to get lokinet in already which is higher priority than tor. once lokinet is in there will be no reason to have accessibility to .onion anyways as we provide a functionally equivalent (arguably superior) kind of connectivity to .onion with .loki.
supporting .onion would require all session clients to have a tor client
I was thinking that it would be opt-in support: i.e. in order to access one you need to set up a Tor client yourself and get it working (which is much less than the embedded lokinet support we plan to have).
But I agree that lokinet support is more important and will be a better experience.
