- ### Viewing Thread #117 ###
- This is a new test thread.
- ---Reply #118
- This is a reply to the test thread.
- ---Reply #119
- This is another reply.
- ---Reply #120
- ____ _
- ---Reply #121
- Congratulations on your test.
- ---Reply #122
- Thanks.
- ---Reply #123
- Thanks. On the last one, I tried to write an ASCII art. Fail! I'm thinking installing this forum to play. No new line on posts :( But it works.
- ---Reply #124
- @123 I'm happy to hear you'd like to try! I've never thought of handling multiline input before for searches. I was thinking I could use escape characters, because I thought \n in search string literally would break spec
- ---Reply #125
- , ; , .-'"""'-. , ; ,
- ---Reply #126
- I'm here because of the lack of privacy on HTTP(S) - headers and JS send a lof of informations about the client (fingerprinting possible). Gopher solves the problem if over Tor/I2P hidden service.
- ---Reply #127
- I searched for a forum on Gopher and found yours. Please, implement multiline on posts and increase the number of characters.
- ---Reply #128
- @126 Glad to have you! I assume you saw this gopherhole has .onion support? @127 I created an issue! I'll post a link later.
- ---Reply #129
- 21 (github.com)
- ---Reply #130
- I've bookmarked the gopherhole. I'll see the link you sent.
- ---Reply #131
- Yes, I used Lynx + Tor. Gopher is perfect, thus sends no info about the client (I "wiresharked" my local traffic). Tor/I2P solves Gopher's lack of id/crypto/auth on site/data.
- ---Reply #132
- @130 thank you for bookmarking! @131 that's really cool! i love to hear it! i've never used i2p before!
- ---Reply #140
- server
- Reply to Thread
- View as File
- Return to Index