prologic
twtxt.net
"Problems are Solved by Method" 🇦🇺👨💻👨🦯🏹♔ 🏓⚯ 👨👩👧👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)
↳
In-reply-to
»
Not sure which conversation you mean, @eaplmx (it's already quite late here), but here's my take: I think twtxt it's not heavy enough. For a real feed format I would like to have a clear separation between titles and content. And more options for the content. Plaintext and HTML at least. Twtxt is plaintext, but lots of folks (me included) actually use markdown in their yarns. However, the actual format being used is not advertised anywhere. To make things worse, I actually prefer reStructuredText over markdown. For podcasts some enclosure-like thing would be nice as well. Twtxt being line based also really limits structuring of longer content by hand. Just can't produce a nice source file.
⤋ Read More
@mckinley So… What are you proposing exactly? 🤔 If not some kind of metadata field declaration?
↳
In-reply-to
»
Recent updates to LibWeb have fixed the icons on the Yarn web client in Ladybird and the SerenityOS browser! Unfortunately, it still isn't possible to post using LibWeb browsers but we'll get there. :^)
⤋ Read More
@mckinley Looks not too bad 👌
↳
In-reply-to
»
👋 Hey all users of this pod (twtxt.net -- I just merged @darch's PR that replaces PicoCSS with SimpleCSS. You may want to refresh or clear your browser cache to get the new look 😅
⤋ Read More
@akoizumi@kyoko.nerdpol.ovh Yeah there a few things that are broken but most things are okay 👌
↳
In-reply-to
»
@darch Also the pop-up when you click on external links in a Twt is broken. I tried to for example in the Twt (screenshot attached) and it didn't work :/
⤋ Read More
In fact even in this Yarn, the whole Image Gallery feature that @ullarah@txt.quisquiliae.com originally did is not completely broken 😅 I’ll let you ponder on that for a while, but we should probably do something about this before cutting a new release for sure 👌
↳
In-reply-to
»
Not sure which conversation you mean, @eaplmx (it's already quite late here), but here's my take: I think twtxt it's not heavy enough. For a real feed format I would like to have a clear separation between titles and content. And more options for the content. Plaintext and HTML at least. Twtxt is plaintext, but lots of folks (me included) actually use markdown in their yarns. However, the actual format being used is not advertised anywhere. To make things worse, I actually prefer reStructuredText over markdown. For podcasts some enclosure-like thing would be nice as well. Twtxt being line based also really limits structuring of longer content by hand. Just can't produce a nice source file.
⤋ Read More
@mckinley We’ve talked about this once before and in fact even tried to formalize it but in the end we couldn’t agree on a way to do it or even if it was a good idea… Worth revisiting this again? Like @lyse@lyse.isobeef.org I’ve also looked at JSON Feed and wasn’t entirely convinced either.
↳
In-reply-to
»
@tkanos So basically it counts the mentions? We definitely need some feed normalization database, too many broken mentions out there. :-)
⤋ Read More
We definitely need some feed normalization database, too many broken mentions out there
What if we use some kind of heuristics based on a client’s cache? Or some kind of similarity search? Hmm 🤔
@darch@neotxt.dk Also the pop-up when you click on external links in a Twt is broken. I tried to for example in the Twt (screenshot attached) and it didn’t work :/
↳
In-reply-to
»
who would like to play a game? https://wiki.kyoko-project.wer.ee/wiki.cgi/among-sus
⤋ Read More
@akoizumi@social.kyoko-project.wer.ee Sorry man, I looked at this briefly last night when I went to bed (on my phone) but I “didn’t get it” 😅 Sorry!
↳
In-reply-to
»
💡 TIL: Today I learned that there is nothing special about
⤋ Read More
pkg/ inside of Go projects. It is just like any other sub-package structure you might otherwise define in your project. It just adds an extra part to your imports. I think it's actually confusing at best and just unnecessary typing and an unnecessary sub-structure. Just keep your packages in the top-level and be done with it 👌
@lyse@lyse.isobeef.org Yeah I agree, and that does happen.
It’s also been merged and my pod upgraded 👌
@darch@neotxt.dk There are a few minor regressions. But maybe they were intentional? The “In-Reply-To” used to limit the text to some width and use an ellipsis via CSS to cut it off a bit.
👋 Hey all users of this pod (twtxt.net – I just merged @darch@neotxt.dk’s PR that replaces PicoCSS with SimpleCSS. You may want to refresh or clear your browser cache to get the new look 😅
↳
In-reply-to
»
Writing and running full e2e integration tests using Go and for Go CLI applications. Lookingo into one of:
⤋ Read More
@lyse@lyse.isobeef.org Hmmm good points but yeah it depends on the program 👌
↳
In-reply-to
»
Guys, I have a bad news, I went through the twtxt-osphere :
- I found 1289 twtxt account
- among those 721 are accessible ( 712 http / 9 gemini / 0 gopher)
- but only 111 account are still active in 2022 :S (107 http / 4 gemini / 0 gopher).
⤋ Read More
Somehow I think “influence” is the wrong word here 😂
↳
In-reply-to
»
Recent updates to LibWeb have fixed the icons on the Yarn web client in Ladybird and the SerenityOS browser! Unfortunately, it still isn't possible to post using LibWeb browsers but we'll get there. :^)
⤋ Read More
@mckinley Looking better and better all the time 👌
↳
In-reply-to
»
Guys, I have a bad news, I went through the twtxt-osphere :
- I found 1289 twtxt account
- among those 721 are accessible ( 712 http / 9 gemini / 0 gopher)
- but only 111 account are still active in 2022 :S (107 http / 4 gemini / 0 gopher).
⤋ Read More
@tkanos Haha that’s amazing work 👌 And those sort of numbers more-or-less line up with the [search engine and crawler[(https://search.twtxt.net/stats) (which needs a bit more attention and love, maybe some more features too?)
↳
In-reply-to
»
Bosses Think Workers Do Less From Home, Says Microsoft
An anonymous reader quotes a report from the BBC: A major new survey from Microsoft shows that bosses and workers fundamentally disagree about productivity when working from home. Bosses worry about whether working from home is as productive as being in the office. While 87% of workers felt they worked as, or more, efficiently from home, 80% of managers disagreed. The sur ... ⌘ Read more
⤋ Read More
Bosses Think Workers Do Less From Home, Says Microsoft An anonymous reader quotes a report from the BBC
Bosses are idiots. This kind of mentality is both outdated and stupid. For some of us we actually work longer hours and get more done with less distractions. Can we stop using the term “boss” and “manager” already FFS?! 🤦♂️ Here’s an idea, be a leader, help those around you, lead by example. Ugggh “middle management” 🤬
↳
In-reply-to
»
Writing and running full e2e integration tests using Go and for Go CLI applications. Lookingo into one of:
⤋ Read More
@lyse@lyse.isobeef.org Yeah I agree errors should be tested too. That’s why Main() has the func Main(w io.Writer, args []string) error 😅 So you can actually assert on the error returned. For a CLI however, I’m not particularly a fan of logging errors to stderr too much (if at all). And re go-cmdtest FWIW a Terminal combines stdout and stderr too by default when displaying the output of a program 😅 – However I filed an issue against the cmdtest project and now I’m not so sure I want to continue using it, I may as well just figure out how to run the test binary under coverage and write the tests myself in Go.
↳
In-reply-to
»
Writing and running full e2e integration tests using Go and for Go CLI applications. Lookingo into one of:
⤋ Read More
@tkanos Yes a long time ago
↳
In-reply-to
»
💡 TIL: Today I learned that there is nothing special about
⤋ Read More
pkg/ inside of Go projects. It is just like any other sub-package structure you might otherwise define in your project. It just adds an extra part to your imports. I think it's actually confusing at best and just unnecessary typing and an unnecessary sub-structure. Just keep your packages in the top-level and be done with it 👌
@lyse@lyse.isobeef.org You are right of course ! 👌 but what we’re talking about here I think it’s probably very experienced program is from one language coming to another language so there isn’t much learning the new patterns of such? Anyway 🤷♂️
↳
In-reply-to
»
Writing and running full e2e integration tests using Go and for Go CLI applications. Lookingo into one of:
⤋ Read More
@lyse@lyse.isobeef.org Oh btw… The reason a io.Writer is left out for “stderr” is that normally I tend to just set the logging output to os.Stderr, like log.SetOutput(os.Stderr) anyway and its not usually something I end up testing. Not sure if this is the best approach, but I’m only really interested in testing the “output”(s) and either error or non-error cases.
↳
In-reply-to
»
@tkanos a quick question, I'm using twet (thanks for the recommendation), how do the clients announce between them that you have replied to a previous twt?
⤋ Read More
@eaplmx Yup 😅
↳
In-reply-to
»
💡 TIL: Today I learned that there is nothing special about
⤋ Read More
pkg/ inside of Go projects. It is just like any other sub-package structure you might otherwise define in your project. It just adds an extra part to your imports. I think it's actually confusing at best and just unnecessary typing and an unnecessary sub-structure. Just keep your packages in the top-level and be done with it 👌
@brasshopper Bingo! That’s just it 👌 Idioms.
That’s why you keep hearing about:
Idiomatic Go
Some years ago when I still actively developed in Python i twas:
Zen of Python
Every language has its strengths and weaknesses, like you , I really hate it when the Java or C++ crowd come bring their sillyridiculouss structures to nice languages like Go 😅 (I felt the same way about Python 2.x -> 3.x too, I just couldn’t write Python anymore 😅)