domgoergen.com

No description provided.

Although that would seperate the network in clients that can or can’t support some protocols. Not to mention if someone would mention me with my ipfs address and other with my http address

⤋ Read More

Although that would seperate the network in clients that can or can’t support some protocols. Not to mention if someone would mention me with my ipfs address and other with my http address

⤋ Read More

What about benaiah first idea for #issue48? It would be easy to parse, looks very unixlike and doesn’t clash with the current syntax? I would implement it for txtnish, if it wouldn’t be the only implementation… :)

⤋ Read More

What about benaiah first idea for #issue48? It would be easy to parse, looks very unixlike and doesn’t clash with the current syntax? I would implement it for txtnish, if it wouldn’t be the only implementation… :)

⤋ Read More

@freemor@freemor.homelinux.net Or we resort the timline to have the newest entries on top, then you could just request the first x bytes of every feed. But archiving is definitly the pragmatic solution. Get back to me if you want to have that in txtnish. Or maybe someone want to submit a PR?

⤋ Read More

There are so many alternatives like ipfs or scuttlebutt, but i fear that we loose the simplicity of the old protocols. That in my mind is the main attraction of twtxt.

⤋ Read More

I recently tried to write a command like client to GNU social, but after reading the specs on ActivityStreams, Webfinger, PubsubHubbub and Salmon i soon lost interest… :)

⤋ Read More