003.00 POST: @aewens@tilde.team, welcome to the party!

@aewens@tilde.team what is up! welcome to the show!

how i found out about twtxt btw: gopher://fuckup.solutions/0/enkiv2/medium-backup/2018-06-15_Exocortex-tools-part-I–social-media-automation-with-very-small-shell-scripts-62d995242a57.txt

@khuxkm@khuxkm.tilde.team aaaaaaaaaaaaaaaaa

@jan6@tilde.team all quiet. status ok.

@freemor@freemor.homelinux.net they always claim to have a video of me having fun but there is a sticker on my cam and the webcam module is blacklisted. 🤨

@ben@tilde.team some kind of cron job to poll the registry? sumthin.

@ben@tilde.team howdy ben

@kas@enotty.dk I forgot a DNS record 🙈

@robbinaer@robbinaer.info weird as I see you logged in there 🤨

@robbinaer@robbinaer.info Maybe a DNS issue as I moved my domain to inwx yesterday. Can you try again?

@nblade@nblade.sdf.org: Stuff is heavy on the mind. What is a lightweight lifestyle worth? Trash everything under this value. You can always rebuy it.

@freemor@freemor.homelinux.net No, I think the old DOS edlin program is the standard text editor LOL.

@dave@davebucklin.com No, I don’t think I’ve ever done that

@freemor@freemor.homelinux.net I also always try to have a few ssh servers with several ports available for me to use. My favorite port is 443. Once had a firewall that wouldn’t allow SSH on 22 but 443 was acceptable because it expected encryption on it.

@freemor@freemor.homelinux.net: As long as they are dimmable or relate to the screen brightness. I’m often working in the dark with 1% screen brightness.

I just recently found an issue with my custom client. It was ignoring microseconds on timestamps. Which meant I was missing some twtxt from people. I got that fixed and I know see all of them.

@mdom@domgoergen.com my own custom client I wrote, I use cron to run the update my timeline every 20 mins. My update process also processes 10 curl calls at time. I did that to save time when I poll everyone.

@mdom@domgoergen.com metadata is there now. I was one commit behind.

Do you have ideas for a new spec? Maybe we can collect them on irc? join freenode/twtxt

@sdk@codevoid.de Although i’m a gopher fanboy, I wouldn’t use it for twtxt. It’s really a optimal fit.

@mdom@domgoergen.com Or limit the the amount and use random 10 followers or so…

@mdom@domgoergen.com did you think about not putting all followers into the twtxt file, but a URL to a follower list? Think performance. If the network grows to 10000 users, you’d have 10000 extra lines in each twtxt file.

@nblade@nblade.sdf.org If everybody is happy with the format, sure! Writing a new spec is on my todo list for a long time. Maybe that’s a good reason to do it.

@nblade@nblade.sdf.org The newest txtnish can show the users other users are following: txtnish following mdom (if mdom is my nick on your system)

@mdom@domgoergen.com Nice! activated

@mdom@domgoergen.com That’s interesting. So does txtnish read that metadata? or would an end user just look at the file to see it? Is the meta data going to be the standard?

@mdom@domgoergen.com what metadata feature is that?

@freemor@freemor.homelinux.net It’s nice to be way ahead of the curve no? LOL.

@kas@enotty.dk the only thing I can think is that people are finally re-figuring out that static sites are really fast because the content doesn’t need to generated on the fly. I noticed there were a lot of static content generators out there.

@kas@enotty.dk WTF! That’s a good one.

@mdosch@mdosch.de: 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@mdosch.de: Yes, #txtnish uses curl and can therefore handle all curl supported protocols.

@sdk@codevoid.de A comment might not be in the spec, but I know several of the twtxt files I’ve looked at have them. I know my kit bashed twtxt client ignores those lines and I’m sure other clients do too.

@nblade@nblade.sdf.org: 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.

@nblade@nblade.sdf.org: Either that, or provide URL to a follower file: #followfile https://codevoid.de/tw.following.txt

@sdk@codevoid.de you know the more I think about it, it might make sense to have it the twtxt file. It would just need to be a comment line something like “#follows sdk gopher://codevoid.de/0/tw.txt” on a single line. That way it would be easy to parse out those follows by finding the #follows.

@sdk@codevoid.de a random mix into the the twtxt file seems less clean to me. The former would be easier to implement and simpler for another program to get and parse.

@nblade@nblade.sdf.org: 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.

@metamurks@www.metamurks.org It’s not really live. Check my ‘File Storage’ on gopher :-)

@metamurks@www.metamurks.org Have fun in captcha hell :(

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@www.metamurks.org Really? I’m super happy with DDG. But I haven’t heard of searx as of now.

@mdom@domgoergen.com Shall we have an additional twtxt list: we-are-onion.txt? I’m here http://codevoid4p3lowez.onion/?q=twtxt

@freemor@freemor.homelinux.net I always find amazing that people don’t understand that. People just don’t understand that everything can be a “server”

@nblade@nblade.sdf.org 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@freemor.homelinux.net I thought so too. Color me surprised when I surveyed my follow programmers in my dept and only 3 out 12 knew what I was talking about.

My twtxt file is now also available without emoji variable: https://codevoid.de/?q=twtxt

@freemor@freemor.homelinux.net 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 :)