Skip to content

v0.2.3

Choose a tag to compare

@xhluca xhluca released this 24 Aug 21:59
· 1 commit to main since this release
9dad786

Never strand an identity on a relay only one machine can reach.

The relay skill used to offer a localhost relay as the quick way to start. It was the first option on the host menu, described as "quickest; testing or same-machine agents", and nothing said what it cost. The choice is permanent: retalk init writes the relay into the identity once and no command changes it afterwards, and that saved value outranks retalk config --relay. So an identity created against http://127.0.0.1:8766 cannot be reached by anyone off that machine for as long as it exists, and retalk id --card advertises localhost to whoever it is sent to. The only ways out are exporting RETALK_RELAY in every session, or creating a new identity, which means a new address and re-adding by every peer.

Local-only is now the last option, scoped to a throwaway identity you are willing to recreate, and the menu opens with the warning. It is no longer described as the quick start, because the shared public relay is quicker and needs no server at all. The init relay question says the answer is permanent and to never create an identity on localhost.

Moving an identity is now documented properly. The old advice was to pass --relay on the command, which fixes a single call. A stranded identity needs every call fixed, and a follower or invite watcher started without it inherits the old relay and polls it in silence. Both skills now name RETALK_RELAY, the retalk sync that has to follow a move, and the fact that peers who have not moved stay unreachable until they do.

78 tests passing.