# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 224
# self = https://watcher.sour.is?uri=https://codevoid.de/tw.txt&offset=24
# next = https://watcher.sour.is?uri=https://codevoid.de/tw.txt&offset=124
*dummy tweet to fix my gopher page* #wontfix
*dummy tweet to fix my gopher page* #wontfix
In other news: I'm doing my first ever diet. I lost 5kg already. No big deal really. Just reduce calories. I don't understand all that fuss about diets... just eat a little less and stick to it.
In other news: I'm doing my first ever diet. I lost 5kg already. No big deal really. Just reduce calories. I don't understand all that fuss about diets... just eat a little less and stick to it.
As much as I love photography... working on the pictures for hours afterwards wears me out. But ususally the result rewards for everything. So I just keep working...
As much as I love photography... working on the pictures for hours afterwards wears me out. But ususally the result rewards for everything. So I just keep working...
@mdosch: Yes. I first thought gopher would be a good protocol for this purpose. But HTTP has the advantage, that you don't always need to fetch the whole file. You can do a HEAD and check for last-modified header.
@mdosch: Yes. I first thought gopher would be a good protocol for this purpose. But HTTP has the advantage, that you don't always need to fetch the whole file. You can do a HEAD and check for last-modified header.
@mdosch: Yes, #txtnish uses curl and can therefore handle all curl supported protocols.
@mdosch: Yes, #txtnish uses curl and can therefore handle all curl supported protocols.
@nblade: Check my tw.txt file. The specification does not allow a comment. I've added this now: 1970-01-01T01:00:00.000000Z▸FF:https://codevoid.de/tw.following.txt. I'd use the special date/time + FF: comment as trigger. This is backwards compatible and shouldn't really come up in anyones' timeline.
@nblade: Check my tw.txt file. The specification does not allow a comment. I've added this now: 1970-01-01T01:00:00.000000Z▸FF:https://codevoid.de/tw.following.txt. I'd use the special date/time + FF: comment as trigger. This is backwards compatible and shouldn't really come up in anyones' timeline.
I just read that more than 140 chars are prohibited per twtxt specification. Oops.
I just read that more than 140 chars are prohibited per twtxt specification. Oops.
@nblade: It's just an idea. Not a clean one thoug, as clients would not know upfront who serves such a fiele and who not. Another idea would ne to mix a number of random followers into the twtxt file, which are updated when a person tweets.
@nblade: It's just an idea. Not a clean one thoug, as clients would not know upfront who serves such a fiele and who not. Another idea would ne to mix a number of random followers into the twtxt file, which are updated when a person tweets.
Good night, textuniverse :)
Good night, textuniverse :)
@metamurks It's not really live. Check my 'File Storage' on gopher :-)
@metamurks It's not really live. Check my 'File Storage' on gopher :-)
Any thoughts about decentralized ways to discover twtxt users? I've set up https://codevoid.de/tw.following.txt which is my following list plus whatever comes in via user-agent. If everybody would set this up with the with an added .following we could fetch each others list and discover users that way.
Any thoughts about decentralized ways to discover twtxt users? I've set up https://codevoid.de/tw.following.txt which is my following list plus whatever comes in via user-agent. If everybody would set this up with the with an added .following we could fetch each others list and discover users that way.
@metamurks Really? I'm super happy with DDG. But I haven't heard of searx as of now.
@metamurks Really? I'm super happy with DDG. But I haven't heard of searx as of now.
My search forwarder https://codevoid.de/q=%s is now forwarding to the JS version of duckduckgo with a dark theme applied and safe search off. I've pretty much set my own preferences to it. If you prefer the html version, you can still just turn JS for DDG off and DDG will forward you. I find the html version totally usable, but it's not customizable at all.
My search forwarder https://codevoid.de/q=%s is now forwarding to the JS version of duckduckgo with a dark theme applied and safe search off. I've pretty much set my own preferences to it. If you prefer the html version, you can still just turn JS for DDG off and DDG will forward you. I find the html version totally usable, but it's not customizable at all.
Migration successful. My page (http version) is now running on gopherproxy-c. Unfortunately not without functionality loss. If you used my site as search engine, you need to replace the smiley with "q". The redirect is now handled by nginx and nginx can not read emoji variables.
Migration successful. My page (http version) is now running on gopherproxy-c. Unfortunately not without functionality loss. If you used my site as search engine, you need to replace the smiley with "q". The redirect is now handled by nginx and nginx can not read emoji variables.
Evil Bobs brand new gopherproxy-c is double as fast as gopherproxy-go. Amazing! (migration is in progress)
Evil Bobs brand new gopherproxy-c is double as fast as gopherproxy-go. Amazing! (migration is in progress)
I think the cloud is also the ISPs fault. If there would never have been any NAT and async connectivity, the world would be different.
I think the cloud is also the ISPs fault. If there would never have been any NAT and async connectivity, the world would be different.
@nblade Most programmers are just users that are writing/maintaining programs. Most can't even handle the underlying OS, let alone a Network or a Server.
@nblade Most programmers are just users that are writing/maintaining programs. Most can't even handle the underlying OS, let alone a Network or a Server.
@freemor My take on this is... let's let people ruin the web. Let centralized services control everything. But let us tech savvy people stick together and provide an alternative space for us. A space that's welcoming to those that want to join and learn. Maybe people will come over when their online actions show real life consequences. There are statistics about decreasing social media use in Generation Z. Maybe they want to learn from us Internet-Dinosaurs :)
@freemor My take on this is... let's let people ruin the web. Let centralized services control everything. But let us tech savvy people stick together and provide an alternative space for us. A space that's welcoming to those that want to join and learn. Maybe people will come over when their online actions show real life consequences. There are statistics about decreasing social media use in Generation Z. Maybe they want to learn from us Internet-Dinosaurs :)
@freemor This is completely contrary to what people want. People don't care about how something works. They want to use something that's premade and that they can use without learning anything about it. Decentralization is a technical Detail, nobody cares about. Just like security or freedom. It's all nice to have if it comes for free, no time investment and no convenience cuts. So the only way to establich decentralization is by making it better, cheaper and easier to use than centralized services. #sadtruth
@freemor This is completely contrary to what people want. People don't care about how something works. They want to use something that's premade and that they can use without learning anything about it. Decentralization is a technical Detail, nobody cares about. Just like security or freedom. It's all nice to have if it comes for free, no time investment and no convenience cuts. So the only way to establich decentralization is by making it better, cheaper and easier to use than centralized services. #sadtruth
You can now use https://codevoid.de/?q=%s as search provider in your browser. Requests that do not start with gopher:// will be forwarded to the non-JS version of duckduckgo. Gopher will be shown directly. I'm not logging anything. But you must be aware that your search terms would touch my server first.
You can now use https://codevoid.de/?q=%s as search provider in your browser. Requests that do not start with gopher:// will be forwarded to the non-JS version of duckduckgo. Gopher will be shown directly. I'm not logging anything. But you must be aware that your search terms would touch my server first.
iOS autotweet test #sorry
iOS autotweet test #sorry
The workflow app on iOS is magic. I now have a button that asks me to select a picture, then converts it to png, resizes it, strips the metadata, scps it to my jumphost, scps it further to my gopher jail and into my paste directory, constructs the http proxy URL and opens it in safari. All without user-interaction. Now I can share my mobile life with you guys! Prepare for cat pictures!
The workflow app on iOS is magic. I now have a button that asks me to select a picture, then converts it to png, resizes it, strips the metadata, scps it to my jumphost, scps it further to my gopher jail and into my paste directory, constructs the http proxy URL and opens it in safari. All without user-interaction. Now I can share my mobile life with you guys! Prepare for cat pictures!
Why do most new cool things depend on hipster tech like nodejs? *sigh* #dat
Why do most new cool things depend on hipster tech like nodejs? *sigh* #dat
This tweet was written on an iphone. (via http proxy to gopher to txtnish)
This tweet was written on an iphone. (via http proxy to gopher to txtnish)
@mdom: I'm using txtnish on FreeBSD and I had to switch it to gawk (not sure why BSD awk fails) and disable color. Just fyi. I didn't look into it any further.
@mdom: I'm using txtnish on FreeBSD and I had to switch it to gawk (not sure why BSD awk fails) and disable color. Just fyi. I didn't look into it any further.
I always thought about putting together some sort of micro-blog/journal where I can post my daily brainfarts and list them on my webpage. Now, after adding twtxt to my page I have exactly that. It's kind of cool.
I always thought about putting together some sort of micro-blog/journal where I can post my daily brainfarts and list them on my webpage. Now, after adding twtxt to my page I have exactly that. It's kind of cool.
I've started to manage my gopher content with RCS. Together with rcsvers.vim it's a no-brainer. It's pretty nice to have an automatic version created whenever vim is being closed.
I've started to manage my gopher content with RCS. Together with rcsvers.vim it's a no-brainer. It's pretty nice to have an automatic version created whenever vim is being closed.
Use the x-use-gopher header on your http proxies.. "curl -sI https://codevoid.de | grep ^x-u" bitreich.org, r-36.net, taz.de are already there. #gopher
Use the x-use-gopher header on your http proxies.. "curl -sI https://codevoid.de | grep ^x-u" bitreich.org, r-36.net, taz.de are already there. #gopher
@metamurks I use them a lot myself. Plaintext is beautiful.
@metamurks I use them a lot myself. Plaintext is beautiful.
...and I've also added my last tweets to my gopher hole. I don't know why, but this makes me happy.
...and I've also added my last tweets to my gopher hole. I don't know why, but this makes me happy.
Suggestion for the next #GDPR iteration: No landing pages allowed. Content must be served on the first request.
Suggestion for the next #GDPR iteration: No landing pages allowed. Content must be served on the first request.
"The job is payed extremely well!" - no job offer, ever.
"The job is payed extremely well!" - no job offer, ever.