In-reply-to » @bender I taught the whole ecosystem šŸ˜ @prologic @eapl.me The question I was asked the most was: How do I discover people? Someone came up with a fantastic idea, instead of adding the new twt at the end of the feed, do it at the beginning. So you can paginate by cutting the request every few lines.

Twtxt was made for nerds, by nerds.
Iā€™d like to change that. Itā€™s by nerds/hackers, for nerds/hackers and friends of these. It doesnā€™t have to be hacky all the time, as you donā€™t need to be a nerd to have a blog.
But, for that to happen, someone has to build the tools to improve UX.

by design there really is no way to easily discovers others
Yeah, I agree, and although there are directories of email addresses, usually you donā€™t want that, unless you are a ā€˜public figureā€™.
I couldnā€™t say that a microblogging is a ā€œsocial networkā€ by default, as a blog is not either. At the same time, people would expect to find new people and conversations, as youā€™d do in a forum.

I think of two features on top of the current spec:

  • Clients showing a few posts of what your following are watching but you donā€™t, so perhaps you find something interesting to follow next. Or that feature of ā€œYour ā€˜followingsā€™ are following these accounts/peopleā€. (Hard to explain in english, but I hope you get the idea)
  • Sharing your .txt into some directory, saying ā€œHey, I have this twtxt URL, I want to be discoveredā€. Iā€™m thinking of something like the Federated tab on Mastodon.

ā¤‹ Read More
In-reply-to » @bender I taught the whole ecosystem šŸ˜ @prologic @eapl.me The question I was asked the most was: How do I discover people? Someone came up with a fantastic idea, instead of adding the new twt at the end of the feed, do it at the beginning. So you can paginate by cutting the request every few lines.

@bender@twtxt.net I tend to think of Twtxt like Email. It is truely decentralised. So therefore by design there really is no way to easily discovers others except through social interactions and a sort of ā€œword of mouthā€ of human exchanges of communications.

ā¤‹ Read More
In-reply-to » @bender I taught the whole ecosystem šŸ˜ @prologic @eapl.me The question I was asked the most was: How do I discover people? Someone came up with a fantastic idea, instead of adding the new twt at the end of the feed, do it at the beginning. So you can paginate by cutting the request every few lines.

@andros@twtxt.andros.dev and how will that help ā€œdiscover peopleā€? I am missing something, I am sure, as I donā€™t understand.

Twtxt was made for nerds, by nerds. So one would script a way to often (and/or ongoing) check your web server logs for new mentions, ā€œfollowsā€, etc.

ā¤‹ Read More
In-reply-to » @bender thinked about Gemini protocol. Why corporations shit this name with cryptocurrency and LLMs?

@doesnm@doesnm.p.psf.lt why? The Gemini protocol is an obscure, niche, good-for-nothing (yeah, I am trolling) protocol. Search for ā€œGeminiā€, and tell me in which page, on your search engine of choice, you see it being referred as a protocol.

ā¤‹ Read More
In-reply-to » Thank you @python_valencia for letting me show you the secrets of a decentralised plain text social network like twtxt. I hope you enjoyed the talk! ā¤ļøšŸ Media Media #python #twtxt

@bender@twtxt.net I taught the whole ecosystem šŸ˜
@prologic@twtxt.net @eapl.me@eapl.me The question I was asked the most was: How do I discover people?
Someone came up with a fantastic idea, instead of adding the new twt at the end of the feed, do it at the beginning. So you can paginate by cutting the request every few lines.

ā¤‹ Read More

Iā€™m not much a fan of registry limit/offset paging. I think I prefer the cursor/count method. And starting at zero for first and max for latest.

ā¤‹ Read More
In-reply-to » I need to figure out a way to back off requests to feeds that don't update often.

if it hasnā€™t updated in a while so i put the request rate to once a week it will take some time before i see an update if it happens today.

ā¤‹ Read More
In-reply-to » Wow, phishing is just around the corner šŸ‘€

@eapl.me@eapl.me Interesting! Two points stood right out to me:

  1. Why the hell are e-mail newsletters considered a valid option in the first place? Just offer an Atom feed and be done with it! Especially for a blog of this very type. This doesnā€™t even involve a third party service. Although, in addition he also links to Feedburner, what the fuck!? No e-mail address or the like is needed and subject to being disclosed.

  2. When these spam mailers want to prevent resubscribing, then for fuckā€™s sake, why donā€™t they use a hash of the e-mail address (I saw that in yarnd) for that purpose? Storing the e-mail address in clear text after unsubscribing is illegal in my book.

ā¤‹ Read More
In-reply-to » I think I should try self-hosting some Mastodon thingy again.

@prologic@twtxt.net In all seriousness: Donā€™t worry, Iā€™m not going to host some Fediverse thingy at the moment, probably never will. šŸ˜…

But I do use it quite a lot. Although, I donā€™t really use it as a social network (as in: following people). I follow some tags like #retrocomputing, which fills my timeline with interesting content. If there was a traditional web forum or mailing list or even a usenet group that covered this topic, Iā€™d use that instead. But thatā€™s all (mostly) dead by now. ā˜¹ļø

ā¤‹ Read More
In-reply-to » I need to import my yarn cache. It's sitting at about 1.5G in registry format. That should make things interesting...

@xuu@txt.sour.is Wow, thatā€™s a giant graveyard. In my new database I have 16,428 messages as of now. Archive feed support is not yet available, so itā€™s just the sum of all the 36 main feeds.

ā¤‹ Read More
In-reply-to » Wait! What's going on?! šŸ§

@prologic@twtxt.net Gemini has an answer for you:

This is a conversation thread from a twtxt network, detailing a userā€™s (movq) frustration with the Mastodon ā€œexport dataā€ feature and their consideration of self-hosting a fediverse alternative. Hereā€™s a summary:

  • movqā€™s initial issue:
    • movq is concerned about the volatility of their data on their current Mastodon instance due to a broken ā€œexport dataā€ feature.
    • They contacted the admins, but the issue remains unresolved.
    • This led them to contemplate self-hosting.
  • Alternative fediverse software suggestions:
    • kat suggests gotosocial as a lightweight alternative to Mastodon.
    • movq agrees, and also mentions snac as a potential option.
  • movqā€™s change of heart:
    • movq ultimately decides that self-hosting any fediverse software, besides twtxt, is too much effort.
  • Resolution and compromise:
    • The Mastodon admins attribute the export failure to the size of movqā€™s account.
    • movq decides to set their Mastodon account to auto-delete posts after approximately 180 days to manage data size.
    • Movq also mentions that they use auto-expiring links on twtxt to reduce data storage.

ā¤‹ Read More
In-reply-to » I think I should try self-hosting some Mastodon thingy again.

The Mastodon admins say that itā€™s probably because of the size of my account (~600 MB), so the export process times out. And I understand that. Here on twtxt, I always use auto-expiring links when I post images or videos. It just gets too much data otherwise. I think Iā€™ll just set my Mastodon account to auto-delete posts after ~180 days or something like that. Nobody cares about old posts anyway.

ā¤‹ Read More
In-reply-to » Thinking about adding a little ā€œfocusā€ feature to my window manager: It hides all but one window, no wallpaper, no bars.

@lyse@lyse.isobeef.org @bender@twtxt.net It already is a tiling window manager, but some windows canā€™t be tiled in a meaningful way. I admit that Iā€™m mostly thinking about QEMU or Wine here: They run at a fixed size and canā€™t be tiled, but I still want to put them in ā€œfull screenā€ mode (i.e., hide anything else).

ā¤‹ Read More
In-reply-to » I now subscribed to most feeds in my Go tt reimplementation that I already followed with the old Python tt. Previously, I just had a few feeds for testing purposes in my new config. While transfering, I "dropped" heaps of feeds that appeared to be inactive.

I need to import my yarn cache. Itā€™s sitting at about 1.5G in registry format. That should make things interestingā€¦

ā¤‹ Read More
In-reply-to » I now subscribed to most feeds in my Go tt reimplementation that I already followed with the old Python tt. Previously, I just had a few feeds for testing purposes in my new config. While transfering, I "dropped" heaps of feeds that appeared to be inactive.

neat! my watcher is currently sitting at about 75 MB following over 1500 feeds. only about 200 are currently somewhat active.

-rw-r--r--. 1 xuu  xuu   69M Mar 25 20:46 twt.db
-rw-r--r--. 1 xuu  xuu   32K Mar 25 21:34 twt.db-shm
-rw-r--r--. 1 xuu  xuu  5.6M Mar 25 21:34 twt.db-wal
sqlite> select state, count(*) n from feeds group by 1;
hot|7
warm|8
cold|183
frozen|743
permanantly-dead|857

ā¤‹ Read More
In-reply-to » Thanks, @movq!

There are 82.108 read statuses, but only 24.421 messages in the cache. In contrast to the cache with the messages, the read statuses are never cleaned up when a feed was unsubscribed from. And the read statuses also contain old style hashes, before we settled on the what we have today. Still a huge difference. Hmm.

ā¤‹ Read More
In-reply-to » I now subscribed to most feeds in my Go tt reimplementation that I already followed with the old Python tt. Previously, I just had a few feeds for testing purposes in my new config. While transfering, I "dropped" heaps of feeds that appeared to be inactive.

Thanks, @movq@www.uninformativ.de!

My backing SQLite database with indices is 8.7 MiB in size right now.

The twtxt cache is 7.6 MiB, it uses Pythonā€™s pickle module. And next to it there is a 16.0 MiB second database with all the read statuses for the old tt. Wow, super inefficient, it shouldnā€™t contain anything else, itā€™s a giant, pickled {"$hash": {"read": True/False}, ā€¦}. What the heck, why is it so big?! O_o

ā¤‹ Read More