Currently if someone links a tor url in the chat the user will be unable to open it unless they engage in the tedious process of opening TOR Browser, or using Brave Browser's simple TOR setup. Moho should automatically rewrite the kiwifarms onion address to the clearnet one. This should take into account the user editing the url after its sent as well.
Currently if someone links a tor url in the chat the user will be unable to open it unless they engage in the tedious process of opening TOR Browser, or using Brave Browser's simple TOR setup. Moho should automatically rewrite the kiwifarms onion address to the clearnet one. This should take into account the user editing the url after its sent as well.
Expected Behavior: Always rewrite https://kiwifarmsaaf4t2h7gc3dfc5ojhmqruw2nit3uejrpiagrxeuxiyxcyd.onion to https://kiwifarms.st
The onion address is rewritten to https://kiwifarms.st wherever it appears, keeping the path, query and fragment - so a link to a thread still lands on that thread. A mention written without a scheme gains https://, which also makes it clickable where it previously was not.
Done as the message is drawn rather than as it is stored, which is what covers a URL edited after it was sent: an edit redraws, and the rewrite is part of drawing. The same holds for backlog fetched before this existed and for a quote of either.
Also applied at the click itself, in the main process, because not every link comes from a message body - a picture fetched from the site carries an onion address of its own, and "open in browser" on one of those handed the system a name it could not resolve.
The daemon still speaks to the onion over its own Tor client; nothing about how moho connects has changed.
Finished in [`03f9353`](https://git.salastil.com/Salastil/moho/commit/03f9353).
The onion address is rewritten to `https://kiwifarms.st` wherever it appears, keeping the path, query and fragment - so a link to a thread still lands on that thread. A mention written without a scheme gains `https://`, which also makes it clickable where it previously was not.
Done as the message is drawn rather than as it is stored, which is what covers a URL edited after it was sent: an edit redraws, and the rewrite is part of drawing. The same holds for backlog fetched before this existed and for a quote of either.
Also applied at the click itself, in the main process, because not every link comes from a message body - a picture fetched from the site carries an onion address of its own, and "open in browser" on one of those handed the system a name it could not resolve.
The daemon still speaks to the onion over its own Tor client; nothing about how moho connects has changed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently if someone links a tor url in the chat the user will be unable to open it unless they engage in the tedious process of opening TOR Browser, or using Brave Browser's simple TOR setup. Moho should automatically rewrite the kiwifarms onion address to the clearnet one. This should take into account the user editing the url after its sent as well.
Expected Behavior: Always rewrite https://kiwifarmsaaf4t2h7gc3dfc5ojhmqruw2nit3uejrpiagrxeuxiyxcyd.onion to https://kiwifarms.st
Finished in
03f9353.The onion address is rewritten to
https://kiwifarms.stwherever it appears, keeping the path, query and fragment - so a link to a thread still lands on that thread. A mention written without a scheme gainshttps://, which also makes it clickable where it previously was not.Done as the message is drawn rather than as it is stored, which is what covers a URL edited after it was sent: an edit redraws, and the rewrite is part of drawing. The same holds for backlog fetched before this existed and for a quote of either.
Also applied at the click itself, in the main process, because not every link comes from a message body - a picture fetched from the site carries an onion address of its own, and "open in browser" on one of those handed the system a name it could not resolve.
The daemon still speaks to the onion over its own Tor client; nothing about how moho connects has changed.