kensanata / moku-pona Goto Github PK

Fetching jynx atom...:33: parser error : xmlParseEntityRef: no name
<title># On phlog revisions & the small internet (RE: visiblink)

Hitting this error kills my wholemoku-pona update. I'll ping jynx about the & which seems to be the issue, but maybe there's a safer way to handle validation errors without moku-pona dying all the way?

moku-pona add bitreich.org:70/0/news.atom.xml "bitreich"

I've tried that command which pulls the feed from gopher://bitreich.org/0/news.atom.xml. When I run moku-pona update it says it's unchanged, despite having no local cache version. The feed looks good to me.

If TLS Gopher is ever to take off, new tools should allow for it. So now here's the problem: We should attempt a TLS connection to the server and only fall back to normal behavior if this doesn't work (automatic downgrade bad) or we must mark the entries that should use TLS somehow. An extra field in the map? But that will break some clients, I presume.

Recently some phlog listings have begun duplicating when their phlogs update. I'm not 100% sure, but it looks like it's happening on individuals that have multiple phlogs on different servers. Maybe it's because there's more than one shared string in them, or maybe it's because I'm indicating server by adding paranthetical labels (sdf.org) (circumlunar.space).

You can see it here:
gopher://gopher.black/1/moku-pona/

tfurrows and yargo are the curent culprits.

Cannot construct client socket to alexschroeder.ch:70: Network is unreachable

This is killing moku-pona update completely rather than timing-out and continuing onto the next phlog in the list.

I'm using your latest script and it's pulling in RSS feeds properly now. I'm trying to get the publish command to work, but there are two issues.

• the published updates.txt file introduces newlines between every line for some reason
• the RSS feed files are not copying to the publish folder

The links in the updates.txt file to rss feeds is converted to be relative, so that's good.

$ moku-pona remove jynx
Removed 1 subscription

$ moku-pona add gopher://1436.ninja/1/Phlog jynx
$ moku-pona update

Fetching jynx...unchanged

I've narrowed down the issue to the query_gopher function. The socket connects, but when the selector is sent, nothing comes back in the response and the query is skipped. I've tried port 7070 (which he also uses) to no avail. I verified connecting via netcat that sending the /Phlog selector does return the phlog listing.

(tried leaving this on your other wiki, but the formatting all fell apart)