You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are requests to create a .onion version of Monerica.com. The challenge to do this however are that the architecture doesn't lend itself to the typical conventions people may use when doing this.
The read-only version of the site that users typically go to (when they simply go to monerica.com) is hosted in GitHub Pages and then connected to CloudFlare. This makes it unclear how to setup a .onion link for these reqeusts.
To fully enable Monerica.com there needs to be another .onion for the application where people submit to the site, the app. version of the site, this is hosted in a VPS separate from the other version of the site people see who aren't submitting data to the site.
There is a 3rd version as well which is yet another sub domain for the blog. version of the site that is hosted in another application which is the Monerica Blog.
All 3 instances of these Monerica.com applications would need to have a seamless experience to use Tor correctly. Even just doing the read only page and linking to the other sub domains for the application and blog is unclear. Ideally they would all be 1 .onion link but this seems complicated.
Any guidance first on how to have a .onion for the version of the site in GitHub Pages would be helpful.
The text was updated successfully, but these errors were encountered:
There are requests to create a .onion version of Monerica.com. The challenge to do this however are that the architecture doesn't lend itself to the typical conventions people may use when doing this.
All 3 instances of these Monerica.com applications would need to have a seamless experience to use Tor correctly. Even just doing the read only page and linking to the other sub domains for the application and blog is unclear. Ideally they would all be 1 .onion link but this seems complicated.
Any guidance first on how to have a .onion for the version of the site in GitHub Pages would be helpful.
The text was updated successfully, but these errors were encountered: