👋 Hello @funbreaker@we.loveprivacy.club, welcome to We.Love.Privacy.Club, a Yarn.social Pod! To get started you may want to check out the pod’s Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗

Google Drive? Can he give direct link? Idk about he but twtxt feed can he hosted in s3!

@aelaraji@aelaraji.com https://github.com/sorenpeter/timeline/commit/555baefcd0e75e6a281472994e8eb7ae9b5d2a1c

@movq@www.uninformativ.de I will take that as a compliment

Wow, it seem my #Webmentions implementation works from Mastodon via brid.gy

Image

Yes it work: 2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :D

The .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.

Access to those files are closed to the public.

@eapl.mx@eapl.mx Yes, the idea is to add User Agent support to #Timeline.
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I’m not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from twtAgent.php to the acctual twtxt.txt
Help with making Timeline send proper User Agents to others would be much appreciated:)

@lyse@lyse.isobeef.org One person had came access it before, but no tried it

@prologic@twtxt.net Just that people thought twtxt sounded cool and maybe want to set it up themself

@eapl.mx@eapl.mx Super to see you got webmentions working too :)

EDIT: A webmention was send to: https://eapl.mx/timeline/webmention (Status: 202)

@johanbove@johanbove.info Thanks, I’m glad you like it.

@movq@www.uninformativ.de There was no time for discussion just after the presentation, but I had a chat with some folks later.

“A minimalist social network powered by plain text files” - my talk about #twtxt from #Piksel24 Festival is now on YouTube and slides can be found at http://darch.dk/twtxtalk-piksel

@bender@twtxt.net Given that I haven’t posted in so long, my lines of twtxt per unit time average is probably lower than most! I’m a bursty twtxter.

@<@chyrp.doesnm.cc https://chyrp.doesnm.cc/twtxt.txt> this is broken in jenny too, I figure. No nick breaks things.

@prologic@twtxt.net yeah it’s a light post. I was commenting more on how it’s comments are integed with bsky.

@prologic@twtxt.net i think we talked about it before blogs were removed

@shreyan@twtxt.net I see you got a shout out too 😆

This is so neat.

https://emilyliu.me/blog/open-network

When yarn used to have blogs I thought something like this would be a great feature. Having the blog comments tied to a twtxt subject for the blog post.

I’m giving a shot talk about twtxt/yarn/timeline tommow around noon CET at Piksel Festival in Norway. More info and link for live stream at: https://24.piksel.no
(So I will most likely not be joining the call)

@bender@twtxt.net The tagline of Timeline is “a single user twtxt/yarn pod” not just a yarn pod. Similar to GNU/Linux. When we came up with the concept of Yarn Social it was a way to rebrand twtxt with the extensions that makes conversations like this possible.

@doesnm@doesnm.p.psf.lt never!

@bender@twtxt.net hmm.. indeed.

@bender@twtxt.net the EF this feed is muted. Why is yarn busted? 😁 @lyse@lyse.isobeef.org @prologic@twtxt.net

Great to see another user @aelaraji@aelaraji.com - And I can confirm that my #webmentions works from your server

Image

Hey @aelaraji@aelaraji.com I’m running PHP 8.2 on my server

@bender@twtxt.net So turns out something is setting my HashingURI to the value {{ .Profile.URI }} and that is making my hashes wrong so it cannot delete or edit twts.

@bender@twtxt.net trying to figure out a bug in yarn.

@prologic@twtxt.net Cheers, mate, just saw this reply so thank you. And hope you are feeling better now!

I agree with what you say too. The whole thing is just an odd approach and can’t possibly be effective, all the while causing inconveniences or at worst, being plain weird and invasive like ID verification.

@doesnm@doesnm.p.psf.lt up to you. I have mine to rotate at 1,000 twtxts. I have vomited over 400, so far. I have some way to go till rotation. :-D

@movq@www.uninformativ.de I knew you would like it;)

You need quant computer to host these key services. Nobody will do that. ActivityPub/Twtxt instance can be hosted on calculator

@New_scientist@feeds.twtxt.net No they don’t.

@prologic@twtxt.net yes.

@prologic@twtxt.net just rebuild my image.. though git says i am already at latest

@prologic@twtxt.net All good mate.

@prologic@twtxt.net what do we make of Labor’s proposed social media minimum age ban, I.e ID verification, and the likes of Yarn? I haven’t been able to find out exactly how far the legislation goes, but some have said it’s broad enough to include any site that even has a comment section 🤔 but that could be FUD.

@prologic@twtxt.net I never got the root for this

@wbknl@twtxt.net I have thought of getting one. I wish there were easier tools for it than direwolf

@bender@twtxt.net Linux and Android. I would never iOS my friend.

@lyse@lyse.isobeef.org agree on the HTTP stuff. I mean we could mention that for optimization see RFC yadda yadda should be followed for caching. but not have it part of the spec proper.

@bender@twtxt.net 😜

@bender@twtxt.net 😛

@sorenpeter@darch.dk #NSFS #NotSafeForSorenpeter

@eapl.me@eapl.me Neat.

So for twt metadata the lextwt parser currently supports values in the form [key=value]

https://git.mills.io/yarnsocial/go-lextwt/src/branch/main/parser_test.go#L692-L698

@sorenpeter@darch.dk on 4 for gemini if your TLS client certificate contains your nick@host could that work for discovery?

@wbknl@twtxt.net are you still in Russia? It could be hard mailing anything to there these days. I read your “russia is eternally cold”, and became curious. Patagonia is the only place I know on South America that it has rounded mountains, though they can be anywhere. Originally from Chile, or Argentina? My curiosity doesn’t need feeding, by the way. It’s all good if it doesn’t. :-)

This morning (and a little bit of the afternoon) the idea of having a full referenced archive of twtxts on the web has consumed me a bit. I am talking about something similar to the email archives one see online, but for twtxts, and a more personal level. Such archive would be available, even if the involved feeds are long gone, because feeds will be treated as received emails.

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

@bender@twtxt.net they revel in their blindness. Roll within their stink.

@wbknl@twtxt.net Welcome to the twtxt-iverse!