@lyse@lyse.isobeef.org Responding could be harmful
@prologic@twtxt.net That looks nice. So that if you link the post in another app it will show the message
@prologic@twtxt.net I guess as long as jenny just links to the post.
@prologic@twtxt.net I think those are fine because its just sharing someone elses post to people who follow you. Those people who follow you might not follow the orginal person and in return might never see that post unless its retoos/retweets. The thing that is harmful is likes.
@prologic@twtxt.net Nice. Now I know about forking replies.
@prologic@twtxt.net Its a way to make another conversation in a thread of posts?
@prologic@twtxt.net I think now I know what forked threads are and figured out how to use them but i don’t really know
@prologic@twtxt.net I don’t think I have used forked threads before
@prologic@twtxt.net Those sounds really cool.
Is something like “reyarn” a thing or not a thing?
@prologic@twtxt.net Yeah I never used it before
@prologic@twtxt.net In jenny there is the option to reply to forked threads
@prologic@twtxt.net That is cool. The name is cool. Like saying “yarn ballers” but that sounds weird and cool at the same time
@prologic@twtxt.net I guess anything that is open source and is not resctricted can be forked. I would assume jenny is the same but I can wait will movq replies.
@prologic@twtxt.net nope I don’t know why its yarn
@lyse@lyse.isobeef.org I never seen anyone mention wrong
@movq@www.uninformativ.de yeah, in a row. but yes, I like it :) got a nice terrace and a bit of garden too. :)
@prologic@twtxt.net Yeah I don’t know how I am going to know if someone wants to talk with me but I guess for now twtxt works.
@prologic@twtxt.net Yeah I am not one of these people who just have a twtxt file and end up posting a few things but not interacting with anyone. I do want to interact with the people of twtxt and yarn users. And not just twtxt users but I do care somewhat about the yarn users because really yarn is twtxt but with additions to make the experience better and a webui and the such like multi users. On top of that yarn and the twtxt clients add things like threads that are even helpful for twtxt users.
@prologic@twtxt.net I joined so its better with me lol
@prologic@twtxt.net I don’t know how to code in go or anything really. Not even really know how to do html and css only basic things.
@prologic@twtxt.net Yeah this is hosted at codeberg pages. Yeah the same issue would happen with github pages.
@prologic@twtxt.net I don’t know any other way to host my file at my domain unless I make a sub domain. I am going to ask codeberg if they offer access of logs.
@prologic@twtxt.net Your the one who wrote the page and did not even realise it was there. lol how nice (not a bad thing just funny)
@prologic@twtxt.net Yeah I do think Jenny adds most of the extensions.
@prologic@twtxt.net First I would have to be able to get to my logs and I don’t think i can
@akoizumi@social.kyoko-project.wer.ee We were talking about having links on the yarn.social page for some guide on how to setup jenny + mutt
@movq@uninformativ.de I did not mention you and instead of replying I made a new post oops.
The thing is I don’t know how to search the web logs on Codeberg or even if they are public. That is the issue with just regular text files. The thing with having the follower list in the twtxt file is that then it knows to track friends of friends like with yarn.
If not having www is an issue when I will add it in. Good to know its something I have to change
@movq@uninformativ.de Do you know how I would find people that reply to my posts or replies or even mention my users? Prologic tried to contact me and unless I found him on the yarn pod then I would not know he exists and wants to talk to me. The user agents would work but I don’t know if I can view my web server logs from codeberg pages and I don’t know how to monitor my logs for mentions. What about the way yarn does it by added people you follow to your twtxt file and having friends of friends like yarn does it be a thing for jenny. Just an idea
@prologic@twtxt.net That is why yarn is better then something like activity pub. Everything over on activity pub tries to work with Mastodon not because its better but because its the most popular. Twtxt clients on the other hand tries to work with the yarn additions because most of the additions improve things even for twtxt users.
@prologic@twtxt.net There is also a link to the blog post on the yarn.social site about how to setup jenny with mutt.
@prologic@twtxt.net I have added that to my twtxt file. Even if I can’t see the metadata the people from yarn can. Not a big deal to add the metadata and it helps yarn users
@prologic@twtxt.net I never tried out any of the other clients except jenny with mutt. The best thing about yarn vs something like Mastodon is that its more promoted of the specification of twtxt files instead of server part. Twtxt can be hosted on some free static site host or some git server even so its really low resouces. Just a basic text file. As far as I know yarn is mostly just a web ui around twtxt and an extnetion to the specification to add some more usability and modern things. Anyone can join decentrilized network by having a twtxt file somewhere. If you want to support the specification of twtxt then that is really something most projects don’t do and they promote the server software mostly.
@prologic@twtxt.net Yeah I saw my profile picture on the yarn pod. Its nice that there is also mobile apps for yarn.
@movq@uninformativ.de There might not even be any benefit to moving that to yarn.social. Besides the yarn site should promote using yarn not twtxt even though there is a little bit of information on the site.
@prologic@twtxt.net I don’t think Jenny does much of anything with the avatar and description but I do know yarn does and its not a bad thing to include the metadata for those users.
@prologic@twtxt.net Yeah I don’t even know how to use them once I added myself to the registries. The jarn search engine is similar to the registries thing but its easier to search and find things from. Also I assume its easier to use it in the yarn pods and whatever elese to get new posts. I would always like to see yarn work with regular twtxt because there is advantges to plain twtxt.
@prologic@twtxt.net I do think the post about how to setup jenny + mutt over on the uninformativ.de blog is still a great post. I used that post to see the steps to set it up and it works fine. Though I can write some blog post with some more documentation for things like auto publishing. The big issue with plain twtxt is that I would have not seen your post unless I looked on twtxt.net when I was looking at yarn a little bit more. Twtxt does overcome the issue by introducing the registry but I can’t figure out any way to use them for Jenny and almost no one uses them in the first place. So I can’t see anyones replies or mentions unless I am following them. Yarn does overcome the issue by friends of friends as you would know as the creator of yarn.
@prologic@twtxt.net Yeah I can try and do that for yarn users.
@prologic@twtxt.net Thanks
@akoizumi@social.kyoko-project.wer.ee cool to see that you fixed the css
@akoizumi@social.kyoko-project.wer.ee Cool if I end up just running my own yarn pod but for now twtxt on my site hosted by codeberg works fine
@xuu@txt.sour.is hey
@akoizumi@social.kyoko-project.wer.ee yo does this work?
@jason@jasonsanta.xyz Hey Jason! Welcome to the twtxtverse!
@jason@jasonsanta.xyz Hey Jason! Welcome to the twtxtverse!
@mckinley@twtxt.net really the language authors should have added those to the standard spec by now. That is just obscene.
@mckinley@twtxt.net really the language authors should have added those to the standard spec by now. That is just obscene.
@abucci@anthony.buc.ci Dependendies suck 😆
Too many moving parts 🤦♂️
@abucci@anthony.buc.ci Its not better than a Cat5e. I have had two versions of the device. The old ones were only 200Mbps i didn’t have the MAC issue but its like using an old 10baseT. The newer model can support 1Gbps on each port for a total bandwidth of 2Gbps.. i typically would see 400-500Mbps from my Wifi6 router. I am not sure if it was some type of internal timeout or being confused by switching between different wifi access points and seeing the mac on different sides.
Right now I have my wifi connected directly with a cat6e this gets me just under my providers 1.3G downlink. the only thing faster is plugging in directly.
MoCA is a good option, they have 2.5G models in the same price range as the 1G Powerline models BUT, only if you have the coax in wall already.. which puts you in the same spot if you don’t. You are for sure going to have an outlet in every room of the house by code.
@abucci@anthony.buc.ci Its not better than a Cat5e. I have had two versions of the device. The old ones were only 200Mbps i didn’t have the MAC issue but its like using an old 10baseT. The newer model can support 1Gbps on each port for a total bandwidth of 2Gbps.. i typically would see 400-500Mbps from my Wifi6 router. I am not sure if it was some type of internal timeout or being confused by switching between different wifi access points and seeing the mac on different sides.
Right now I have my wifi connected directly with a cat6e this gets me just under my providers 1.3G downlink. the only thing faster is plugging in directly.
MoCA is a good option, they have 2.5G models in the same price range as the 1G Powerline models BUT, only if you have the coax in wall already.. which puts you in the same spot if you don’t. You are for sure going to have an outlet in every room of the house by code.
@lyse@lyse.isobeef.org we had a crazy amount of rain today, could barely get home, so much water on all the roads and such.
Does anyone of you use PGP encrypted mail, or any kind or email encryption? Why? Why not?
@prologic@twtxt.net odd is it maybe a wrong mime type thing? Should be text/calendar. Some http servers can mistakenly mark them application/octet-stream
@prologic@twtxt.net odd is it maybe a wrong mime type thing? Should be text/calendar. Some http servers can mistakenly mark them application/octet-stream
@movq@www.uninformativ.de the real question is… Can it ScreamTracker3?
@movq@www.uninformativ.de the real question is… Can it ScreamTracker3?
@lyse@lyse.isobeef.org hah! I cut some out to fit into my pods 4k limit.
Yeah that does studder a bit. To be honest I have no idea what I was thinking there. This excerpt was written a good year ago.
@lyse@lyse.isobeef.org hah! I cut some out to fit into my pods 4k limit.
Yeah that does studder a bit. To be honest I have no idea what I was thinking there. This excerpt was written a good year ago.
@abucci@anthony.buc.ci always nice with a easy fix!
@prologic@twtxt.net I think we could use deltachats new decentralising app format for it: https://delta.chat/en/2022-06-14-webxdcintro
@lyse@lyse.isobeef.org I do wonder how we could build a decentralized way to do this 🤔
@prologic@twtxt.net and others, video call tomorrow/tonight?
testing twtxt using jenny
👋 Hello @burglar@txt.sour.is, welcome to txt.sour.is, 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! 🤗
👋 Hello @burglar@txt.sour.is, welcome to txt.sour.is, 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! 🤗
@prologic@twtxt.net correct type parameters. 😅
@prologic@twtxt.net correct type parameters. 😅
@movq@www.uninformativ.de I usually get up at 05:30, no matter how late I fall a asleep, get in early, get home early 😀
@prologic@twtxt.net on yarn.social I cannot see the link for the list of pods
@mckinley@twtxt.net Haha, while composing I was wondering two or three times whether I should throw my thoughts in an HTML page instead. But out of utter laziness I discarded that idea. ¯_(ツ)_/¯
@prologic@twtxt.net Error handling especially in Go is very tricky I think. Even though the idea is simple, it’s fairly hard to actually implement and use in a meaningful way in my opinion. All this error wrapping or the lack of it and checking whether some specific error occurred is a mess. errors.As(…) just doesn’t feel natural. errors.Is(…) only just. I mainly avoided it. Yesterday evening I actually researched a bit about that and found this article on errors with Go 1.13. It shed a little bit of light, but I still have a long way to go, I reckon.
We tried several things but haven’t found the holy grail. Currently, we have a mix of different styles, but nothing feels really right. And having plenty of different approaches also doesn’t help, that’s right. I agree, error messages often end up getting wrapped way too much with useless information. We haven’t found a solution yet. We just noticed that it kind of depends on the exact circumstances, sometimes the caller should add more information, sometimes it’s better if the callee already includes what it was supposed to do.
To experiment and get a feel for yesterday’s research results I tried myself on the combined log parser and how to signal three different errors. I’m not happy with it. Any feedback is highly appreciated. The idea is to let the caller check (not implemented yet) whether a specific error occurred. That means I have to define some dedicated errors upfront (ErrInvalidFormat, ErrInvalidStatusCode, ErrInvalidSentBytes) that can be used in the err == ErrInvalidFormat or probably more correct errors.Is(err, ErrInvalidFormat) check at the caller.
All three errors define separate error categories and are created using errors.New(…). But for the invalid status code and invalid sent bytes cases I want to include more detail, the actual invalid number that is. Since these errors are already predefined, I cannot add this dynamic information to them. So I would need to wrap them à la fmt.Errorf("invalid sent bytes '%s': %w", sentBytes, ErrInvalidSentBytes"). Yet, the ErrInvalidSentBytes is wrapped and can be asserted later on using errors.Is(err, ErrInvalidSentBytes), but the big problem is that the message is repeated. I don’t want that!
Having a Python and Java background, exception hierarchies are a well understood concept I’m trying to use here. While typing this long message it occurs to me that this is probably the issue here. Anyways, I thought, I just create a ParseError type, that can hold a custom message and some causing error (one of the three ErrInvalid* above). The custom message is then returned at Error() and the wrapped cause will be matched in Is(…). I then just return a ParseError{fmt.Sprintf("invalid sent bytes '%s'", sentBytes), ErrInvalidSentBytes}, but that looks super weird.
I probably need to scrap the “parent error” ParseError and make all three “suberrors” three dedicated error types implementing Error() string methods where I create a useful error messages. Then the caller probably could just errors.Is(err, InvalidSentBytesError{}). But creating an instance of the InvalidSentBytesError type only to check for such an error category just does feel wrong to me. However, it might be the way to do this. I don’t know. To be tried. Opinions, anyone? Implementing a whole new type is some effort, that I want to avoid.
Alternatively just one ParseError containing an error kind enumeration for InvalidFormat and friends could be used. Also seen that pattern before. But that would then require the much more verbose var parseError ParseError; if errors.As(err, &parseError) && parseError.Kind == InvalidSentBytes { … } or something like that. Far from elegant in my eyes.
@abucci@anthony.buc.ci perfect, thank you :)
@prologic@twtxt.net I think I saw something on the wiki. Ill check again tonight.
@prologic@twtxt.net golang seems to work on it, so Ill give a try on compiling yarn on it tonight. Would be fun if it works.
@prologic@twtxt.net
https://mangopi.cc/mangopi_mqpro
Search for it on amazon.
@lyse@lyse.isobeef.org yup :)
@prologic@twtxt.net can Yarn pods be consumers to other yarn pods?
@prologic@twtxt.net can Yarn pods be consumers to other yarn pods?
@abucci@anthony.buc.ci I think so. IndieAuth is what I’m a big fan of. All Yarn pods are IndieAuth providers for example (if there are any concumsers out there, we have to work on a consumer ourselves…)
@prologic@twtxt.net thank you, I like them as well, getting closer to autumn now, my favourite time of year for landscape photography in the morning and late evening :)
@prologic@twtxt.net feel free to do so :) I do not plan to have it open for registration though. I might buy a domain and run a public one later on. But for not the one I run was for me.
@prologic@twtxt.net i see your reply has twtxt account for my name in it - that account got removed some time ago.
@abucci@anthony.buc.ci thank you :) I’m taking some more over the weekend, I’ll share them as well :)
@prologic@twtxt.net oh, what illness did you get?
@prologic@twtxt.net I installed my own on my vps :)
@abucci@anthony.buc.ci doing well, 12 in the afternoon here, just came home from a walk in the woods with our dog, really warm and sunny today.
Hi, I am playing with making an event sourcing database. Its super alpha but I thought I would share since others are talking about databases and such.
It’s super basic. Using tidwall/wal as the disk backing. The first use case I am playing with is an implementation of msgbus. I can post events to it and read them back in reverse order.

I plan to expand it to handle other event sourcing type things like aggregates and projections.
Find it here: sour-is/ev
@prologic@twtxt.net @movq@www.uninformativ.de @lyse@lyse.isobeef.org
Hi, I am playing with making an event sourcing database. Its super alpha but I thought I would share since others are talking about databases and such.
It’s super basic. Using tidwall/wal as the disk backing. The first use case I am playing with is an implementation of msgbus. I can post events to it and read them back in reverse order.

I plan to expand it to handle other event sourcing type things like aggregates and projections.
Find it here: sour-is/ev
@prologic@twtxt.net @movq@www.uninformativ.de @lyse@lyse.isobeef.org
@carsten@yarn.zn80.net Nice images!
@niplav@niplav.github.io if he’s willing to be even more nerdy he could use https://lojban.org/publications/cll/cll_v1.1_xhtml-section-chunks/section-evidentials.html and possibly color-code them in some less important color than red
@win0err@kolesnikov.se I agree with @prologic@twtxt.net about the text size. Adding content="width=device-width" to your viewport meta tag will help massively with scaling on different device widths.
Eg. The first screenshot is the current site with a device width of 440px and the second is with the updated viewport meta tag.


Other than that, I like the aesthetic of it 😊 It gives me early-ish internet vibes, which I wasn’t online for (I’m a ‘90s baby) but I’ve seen some pretty early websites.
@prologic@twtxt.net: 1. I use classic twtxt client written in Python from console, I like simplicity; 2. Thanks for the feedback about my website! It’s better viewed with old 800x600 monitors, haha
@prologic@twtxt.net, thanks for the information! I’ll update my twtxt.txt file :-)
I grepped access logs and found at least three subscribers! @apex@rawtext.club, @prologic@twtxt.net, and @darch@neotxt.dk, hi there!
Seems I forgot how to use my twtxt client
twtxt auf home.bonn.cafe installiert - von github.com:win0err/twtxt
Hmm, @prologic@twtxt.net / @lyse@lyse.isobeef.org: Should we remove the section “Traditional Human-Readable Topics” from the spec? Or mark is as deprecated? I haven’t seen this being used in the wild for years. 🤔
@chronolink@chrono.tilde.cafe Replies are not part of the original twtxt format. They were added later as an extension by Yarn.social: https://dev.twtxt.net/doc/twtsubjectextension.html (only the section “Machine-Parsable Conversation Grouping” is used these days)
@prologic@twtxt.net Oh.. reading comprehension is strong today.. you went to US and now back.