@prologic Your solution seems reasonable to me. Thanks 🙏
@sorenpeter@darch.dk Your project is getting better and better. Thanks for sharing 🙏
Things I would add: RSS feed.
@dfaria Appreciate this 👌 Right now the algorithm is quite dumb – and I’d also hate to develop any algorithm that abuses any data from users. So definately needs to be things like:
etc/./
@sorenpeter@darch.dk Yup! Some good simple ideas there 👌
@sorenpeter@darch.dk Thanks for your positivity and support ! 🤗 This is exaxrly spot on, however I also realize getting things “right” is actually quite hard 😅
@sorenpeter@darch.dk Thank you. I understand these problems. But instead of blocking the domain unilaterally, it’s possible to adapt the algorithm to show only one post per day, for example. (In the case of replies, it would be different). This curation idea is interesting, but it doesn’t have to mean blocking domains. I strongly believe in indieweb and I don’t want to see this project fall into problems similar to the big silos (like Twitter and Facebook where whoever is in charge blocks accounts arbitrarily). For me the indieweb, as should be the case with the twtxt protocol, is the space of true freedom of expression. Thanks for understanding and sharing! 🌞
-run flag for go test to specify only one area of tests to be executed. Much more fun this way to quickly go back to writing code.
@lyse@lyse.isobeef.org How much emphasis do you place on test coverage?
To be fair cleaning up “noise” is quite hard to do. Obciously all the 1-way Mastodon feeds were easy because there’s just no way to interact with them!
@dfaria That’s fair. Also removed the block on your domain btw.
@prologic Of course, there are alternatives to make the “discovery” tab work better. If you don’t want so much noise (which I totally understand), just adapt the algorithm so that it only shows 2 or 3 posts from each domain. In the case of replies there was no such limitation. But that’s different from blocking the domain completely (and without any prior warning).
Executing all tests of the online registrations I’m building for the scouts takes now 70 seconds. Initializing a new SQLite database in RAM and creating all the tables for each test case sums up and takes its time. During development cycles I more often resort to the -run flag for go test to specify only one area of tests to be executed. Much more fun this way to quickly go back to writing code.
At least the service layer line coverage is a whopping 99.5%, branch coverage is 93.3% (the latter could still be bumped slightly). However, only 17.6% lines of the web layer are covered (I definitely should increase this by a lot). This still good test base, if I say so myself, came in extremely handy a lot of times when refactoring stuff. Esp. the service layer changed, web not so much. It slows development down quite a lot, that’s for sure. I reckon it’s easily five to ten times more effort to come up with useful tests than writing productive code, probably even more. I’m bad at guessing. But the confidence of not breaking stuff is sooo much more valuable. The tests certainly paid off in the past, zero doubt about that.
It takes a lot of discipline to first write all the tests in the service layer before doing the web stuff and finally see it in action and play around. It’s funny that I always have to force myself to do so, but in the end, I’m always happy to have done it exactly like that. It once again worked out very smoothely that way. But something inside me wants to fast forward. I wonder if that irrational part eventually fades away.
Having a code coverage report does make a night a day difference. It actually turns writing tests into a fun game for me. The older I get, the more I do enjoy writing tests. Rest assured, producing productive code is still cooler. :-)
I’m also sooo happy about vim-go. I can’t believe how much that sped up and boosted my development process.
Whoops, 57 minutes later, this message turned out much more elaborated that I initially envisioned. Oh well. ;-)
@bender You don’t know me and you’re already making arbitrary judgments about me. I only got upset because they didn’t warn me that they were going to block my domain. Nobody likes being canceled without warning. There were other civilized ways of letting me know that there was a problem with my domain instead of blocking it unilaterally. Bye-bye!
New at #ImperfectCognitions: Remembering Daniel Dennett https://imperfectcognitions.blogspot.com/2024/04/remembering-daniel-dennett.html
Novo evento na #FLUP: Palestra "Sou tradutor(a) freelancer. E agora?" https://sigarra.up.pt/flup/noticias_geral.ver_noticia?p_nr=174166
Pessoal, eu transferi minha página html e gopher para galegovski.com. :)
@dfaria@twtxt.net the difference is that these other servers does not post several times a day with content that are not informative/interesting to people outside your academic context, which can be perceived as noise.
What @prologic@twtxt.net have done is what I would call curation of the service he offers to the world for free (as in beer). It’s no one right to have their posts syndicated to the frontpage of twtxt.net, it’s simply a gift he gives to the world and he is free (as in speak) to wrap is anyway he sees fit.
@dfaria.eu@dfaria.eu I hope you stay around 🌞
Good Morning 🎧🎵 Cara de Espelho - Dr. Coisinho https://www.last.fm/music/Cara+de+Espelho/_/Dr.+Coisinho
@prologic@twtxt.net and @bender@twtxt.net for a start a single user twtxt/yarn pod could look like this 😉 
@bender I guess all I can do is unblock the domain and sit down and rethink the “Discover” view’s design and behavior? hmmm 🧐 Alternatively, build a new yarnd 2.0? as a single-user pod only?
@bender Yeah I could get behind that. Define minimalistic though? What features (if any) would we drop? Would it be mobile-first or desktop-first?
@bender I couldn’t agree more 🤣
@bender I never see problems on my end, so I suspect this has to be Cloudflare doing this occasionally. I’ll have to poke around there again. At least I have a close enough timestamp :D Maybe message me your IP and approximate timestamp?
Pessoal quando precisar fazer um google meet com alguém, usem o https://conferenciaweb.rnp.br/?auth=true achei muito rápido, talvez por ser de uma rede totalmente nacional. Dêem preferência ao nosso produto!
This happens more often than I would like. 😢
@prologic@twtxt.net now, the mention of multiuser pods brought an idea. What if you design, and code, single user pods that are extremely lean (extremely low processor, memory, and storage footprint), and brutally minimalist?