Searching txt.sour.is

Twts matching #ToS
Sort by: Newest, Oldest, Most Relevant

When it comes to performance issues, I honestly think the solution is just “don’t follow so many people”. You only pull the feeds you read, and once one’s feeds are too much for the computer to handle, they’ll almost certainly have far too much content for a person to actually read.

⤋ 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

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

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

@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

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

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

@kas@enotty.dk And to make it even worse, most clients interpret the data as win1252. But does any twtxt client autoconvert to utf8 in case another charset is send? I think it probably okay for every client to assume it’s utf8.

⤋ Read More