@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.
@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.
@sdk@codevoid.de That’s an interesting thought. I Know most are text files but at one time there was someone that used a python CGI Script. That person would have had to make a script for the follows.
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.
@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.
I’m back on #facebook! Visit my profile @ follow me here: http://shorturl.at/suwFH
txtnish people can follow me via gopher! @ gopher://codevoid.de/0/tw.txt
Hot take: Everybody whose handle is the word ‘Real’ followed by a name is DEFINITELY a fake/parody account. Fite me.
I hope the five people following my ‘misc’ repo on github are happy recieving an email containing only the placeholder commit message ‘xxx’ like 30 times a day.
@71m@timmorgan.org If your nick is mentioned with @ (i forgot yesterday, sorry) most clients should highlight it in your timeline if you are following the person mentioning you.
@Leo others see the URL for @ mentions of people they are not following. Probably they also added them thinking they are twtxt users.
@leo, @reednj_tw@twtxt.reednj.com: I had to remove your accounts to stop twtxt from crashing. Don’t know why. :-/
Does anyone else gets a crash wenn doing ‘twtxt following’? https://files.mdosch.de/2018-04/following.txt
@karen@server.gkbrk.com Welcome to twtxt. 😃 I recommend twtxt.xyz and #we-are-twtxt for followers.
Bad idea of the day: ‘mastogone’ – a script that identifies people you’re following who haven’t posted in more than a year
Bad idea of the day: Rearrange the frames of a movie so that each frame is followed by the remaining frame that has the minimum (or maximum) difference, in terms first of brightness and then of color
I also have a Mastodon account if ya want to follow me there. It’s also a mirror of my tweets. https://im-in.space/@kdy
Maybe without a new command? txtnish follow mdom http://new_url.com would just work and add a alias? And unfollow http://new_url.com would remove it?
What do you think about adding aliases to txtnish’ follow file? So mentions could be collapsed for different urls of the same twtxt file?
Maybe without a new command? txtnish follow mdom http://new_url.com would just work and add a alias? And unfollow http://new_url.com would remove it?
What do you think about adding aliases to txtnish’ follow file? So mentions could be collapsed for different urls of the same twtxt file?
So since Mastodon was mentioned a few times, I’m trying that out. Any recommendations on people to follow?
Re: support for other protocols, it seems like twtxt would be pretty easily adapted to work over the p2p file network DAT, though it’d need client support for DAT or some way to follow people via files and sync in the background, which might be simpler for clients to support but would still require changes to most clients.
@tdemin@tdemin.github.io good points, though another that I’ve noticed is that it’s difficult to tell who in your network is actually reachable with your tweets. My HTTPS cert went unupdated for a brief while and now I have no idea who is still following me since I got it working again, so it’s difficult to tell where I can really have a conversation. A centralized service can tell who’s following who, but that’s basically impossible in twtxt.
How cult leaders brainwash followers for total control | Aeon Essays https://aeon.co/essays/how-cult-leaders-brainwash-followers-for-total-control?utm_source=Aeon+Newsletter&utm_campaign=328e753676-EMAIL_CAMPAIGN_2017_06_19&utm_medium=email&utm_term=0_411a82e59d-328e753676-68693017
The latest #txtnish will check the url key to change the twturl you’re following. Like an inline 304.
The latest #txtnish will check the url key to change the twturl you’re following. Like an inline 304.
Okay, the plan for txtio: Use sqlite to store followings, tweets and config and use ncurses for the ui. Let’s see how that works out.
Okay, the plan for txtio: Use sqlite to store followings, tweets and config and use ncurses for the ui. Let’s see how that works out.
Maybe we shouldn’t add time sensitive metadata. Maybe # following = https://domgoergen.com/twtxt/mdom.txt https://enotty.dk/twtxt.txt …
@kas@enotty.dk Then let’s just say it has to be on top to make it easy. I’m not even sure how to encode follow? # follow = mdom https://domgoergen.com/twtxt/mdom.txt looks wrong.
Maybe we shouldn’t add time sensitive metadata. Maybe # following = https://domgoergen.com/twtxt/mdom.txt https://enotty.dk/twtxt.txt …
@kas@enotty.dk Then let’s just say it has to be on top to make it easy. I’m not even sure how to encode follow? # follow = mdom https://domgoergen.com/twtxt/mdom.txt looks wrong.
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.
@kas@enotty.dk, @freemor@freemor.homelinux.net (re: finger) That’s another neat thing about twtxt, it totally independent of any transport layer. ipfs, zeronet, finger, as long as the protocol has an url we could follow the ressource.
@kas@enotty.dk, @freemor@freemor.homelinux.net (re: finger) That’s another neat thing about twtxt, it totally independent of any transport layer. ipfs, zeronet, finger, as long as the protocol has an url we could follow the ressource.
@freemor@freemor.homelinux.net We tackle that problem when it arises. I’m currently following 60 (mostly dormant) users with 500k for all files with an update taking less than 2s.
@freemor@freemor.homelinux.net We tackle that problem when it arises. I’m currently following 60 (mostly dormant) users with 500k for all files with an update taking less than 2s.
#txtnish now requests gzipped pages if possible and you can call timeline with a single url to view the twtfile of someone you don’t follow.
#txtnish now requests gzipped pages if possible and you can call timeline with a single url to view the twtfile of someone you don’t follow.
@freemor@freemor.homelinux.net You have to set sync_followings to a remote plain text followings file. You can use we-are-twtxt, but any file will do. Better back up your followings before you test that. Seemed to work here, but who knows.
@freemor@freemor.homelinux.net You have to set sync_followings to a remote plain text followings file. You can use we-are-twtxt, but any file will do. Better back up your followings before you test that. Seemed to work here, but who knows.
I stumbled upon darebee.com in an unrelated hn thread and i’m really impressed, it’s a really easy follow regimen. Try the Totals program.
I stumbled upon darebee.com in an unrelated hn thread and i’m really impressed, it’s a really easy follow regimen. Try the Totals program.
@durcheinandr@durcheinandr.de, @freemor@freemor.homelinux.net Okay, following one self seems not so obvious as i thought. With commit 4b9b067 #txtnish displays the local twtfile.
@durcheinandr@durcheinandr.de, @freemor@freemor.homelinux.net Okay, following one self seems not so obvious as i thought. With commit 4b9b067 #txtnish displays the local twtfile.
allgebrah is leading, followed by umonkey and kas
allgebrah is leading, followed by umonkey and kas
#txtnish quickstart will import your twtxt followings and some of your configuration.
#txtnish quickstart will import your twtxt followings and some of your configuration.
@durcheinandr@durcheinandr.de Hi, welcome to twtxt! Just noticed that you are following me by disclose_identity. Very cool! :)
@durcheinandr@durcheinandr.de Hi, welcome to twtxt! Just noticed that you are following me by disclose_identity. Very cool! :)
Do we really need to scale? How many people can you follow, read and respond to? And websockets could really help.
Do we really need to scale? How many people can you follow, read and respond to? And websockets could really help.
@kas@enotty.dk, @david@post.aldebaran.uberspace.de As long as I can still upload my hand edited twtfile on any webserver and someone can follow me, twtxt hasn’t lost its way. :)
@kas@enotty.dk, @david@post.aldebaran.uberspace.de As long as I can still upload my hand edited twtfile on any webserver and someone can follow me, twtxt hasn’t lost its way. :)
@kdave@kdave.github.io The last commit will check for the environment variable TXTNIX_CONFIG_DIR but this won’t help if i move following to a state file.
@kdave@kdave.github.io The last commit will check for the environment variable TXTNIX_CONFIG_DIR but this won’t help if i move following to a state file.
@kdave@kdave.github.io Ah, okay, i misunderstood you there… :) Would you be okay with following moving to the state file?
@kdave@kdave.github.io Ah, okay, i misunderstood you there… :) Would you be okay with following moving to the state file?
But what to do with following? Are you hand editing it? Would it be okay to move the section to the state file?
But what to do with following? Are you hand editing it? Would it be okay to move the section to the state file?
// follow raur http://raur.nfshost.com/twtxt.txt
// follow raur http://raur.nfshost.com/twtxt.txt
// follow krt http://krt.marmaro.de/twtxt.txt
// follow krt http://krt.marmaro.de/twtxt.txt
// follow david http://post.aldebaran.uberspace.de/twtxt/david.txt
// follow david http://post.aldebaran.uberspace.de/twtxt/david.txt
// follow kdave https://kdave.github.io/twtxt.txt
// follow kdave https://kdave.github.io/twtxt.txt
I’m contemplating a announce_following option, disabled by default, to to anounce follow and unfollow commands in your twtfile.
I’m contemplating a announce_following option, disabled by default, to to anounce follow and unfollow commands in your twtfile.
https://github.com/mdom/twtxtpl/commit/cc8b checks if the twtfile was fetched by following a 301 and rewrites the url in your configuration file
https://github.com/mdom/twtxtpl/commit/cc8b checks if the twtfile was fetched by following a 301 and rewrites the url in your configuration file
My new hobby: Following other people’s “Discover weekly” playlists on @Spotify
part 3: make ‘tf’ run ‘twtxt follow “$@”’
@buckket did you consider having [following] in the twtxt file itself, so people could see who other people were following?
@ruebot I kinda wish the config was part of the twtxt file, so you could see who people are following