https://github.com/blabber/harbour-gophish

A native gopher client for SailfishOS
https://github.com/blabber/harbour-gophish

gopher-client sailfishos

Last synced: 9 days ago
JSON representation

A native gopher client for SailfishOS

• Host: GitHub
• URL: https://github.com/blabber/harbour-gophish
• Owner: blabber
• License: mit
• Created: 2017-11-01T20:32:39.000Z (about 7 years ago)
• Default Branch: master
• Last Pushed: 2017-12-07T12:02:16.000Z (about 7 years ago)
• Last Synced: 2024-12-01T20:47:01.023Z (about 2 months ago)
• Topics: gopher-client, sailfishos
• Language: QML
• Size: 52.7 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
gophish

=======

gophish is a native gopher client for SailfishOS.

Supported item types

--------------------

* `0` - text files

* `1` - gopher directories

* `7` - search queries

* `h` - HTML documents

  * traditional `GET` requests

  * `URL:` links

Encoding

--------

[RFC 1436](https://www.ietf.org/rfc/rfc1436.txt) defines ASCII as the encoding

used by the gopher protocol, but this seems to be outdated by now. Being a

modern client, gophish supports two supersets of the ASCII encoding:

* UTF-8 (preferred)

* Latin-1

When first contacting a server, gophish will send a UTF-8 encoded selector.

This should be no problem, as long as the server is not using non-ASCII

characters in selectors (which is a bad idea anyway).

gophish tries to decode the data retrieved from the server using UTF-8 and if

that fails, it falls back to Latin-1. Once gophish had to fall back to Latin-1,

the server is marked as being Latin-1 encoded internally and all following

communication, including the selectors, will be encoded in Latin-1.