Hola. Si andas viendo este mensaje, contáctame para saber que me estás respondiendo. Puedes mandarme un mensaje o usar un micro-blogging con etiquetas.

We’ve barreled past the microblog line and flew straight over the e-mail chain line. This is just social blogging.

@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.

Ostorlab is going open-source, releasing our scanning engine, vulnerability detectors, and analyzers https://blog.ostorlab.co/ostorlab-open-source.html

About two years late, but I finally finished setting up an iOS Shortcut so I can post to my blog via ssh. http://a.9srv.net/b/

James Mills - Future of Yarn.social

🤔 👋 Reconsidering moving Yarn.social’s development back to Github: Speaking of which (I do not forget); @fastidious@arrakis.netbros.com and I were discussing over a video call two nights ago, as well as @lyse@lyse.isobeef.org who joined a bit later, about the the whole moved of all of my projects and their source code off of Github. Whilst some folks do understand and appreciate my utter disgust over what Microsoft and Copilot did by blatantly scraping open source software’s codebases without even so much as any attempt at attribution or respecting the licenes of many (if not all?) open source projects.

That being said however, @fastidious@arrakis.netbros.com makes a very good and valid argument for putting Yarn.social’s codebases, repositories and issues back on Github for reasons that make me “torn” over my own sense of morality and ethics.

But I can live with this as long as I continue to run and operate my new (yet to be off the ground) company “Self Hosted Pty Ltd” and where it operates it’s own code hosting, servicesa, tools, etc.

Plese comment here on your thoughts. Let us decide togetehr 🤗

#yarnsocial #github #opsnsource #copilot #microsoft

@mckinley@twtxt.net well.. we did used to have a long form blog on here.. but it kinda went by the wayside.

Got to love the sense of humour:

Blog.txt supports multiple options for the chronological order of posts. If you start writing new posts below old posts, the default post sort is descending. If you start writing new posts above all the old posts, like I do, then the post sort algorithm will default to ascending. But if the user would like to change the sort order of the posts, they can press the “End” button on their keyboard to reverse the default chronological order!

Trump’s Group has 30 days to remedy the violation, or their rights in the software are permanently terminated. SF Conservancy

I am out of popcorn, but might need some for this. 😂

Everybody is building one because, you know, why not? Why I built my own static site generator.

Any of y’all seen https://briarproject.org? It’s another fledgling decentralized chat like session but minus the weird blockchain.. it has group chat, forums, and blogs. Also can work via Bluetooth or tor.

briar://aaeutr6pvvr5pgachwlajy5x372xxjvs6btsmmk5kr4ygzps3k3eu

cyberpunk begins: NYPD have deployed robot dogs. Here’s a guide on how to combat them if you get robo-attacked. https://www.jwz.org/blog/2021/02/guide-to-combat-against-robot-war-dogs/

We had everything we needed, and none of the BS; cell phones, e-mail, instant messaging, SMS, file sharing, blogs, forums, and broadband internet were all widespread at that point.

@xuu@txt.sour.is @jlj@twt.nfld.uk @hxii@0xff.nu only if you look at the raw text file https://0xff.nu/blog.txt

@jlj@twt.nfld.uk oh dang the reply didnt add the reply. It was to @hxii@0xff.nu because Firefox shows his shruggy like ¯\_(ツ)_/¯

@prologic@twtxt.net @hxii@0xff.nu I’m certain that it is a markdown thing. Its that way on other markdown sites like Reddit. Because the underline is being escaped to prevent the underline style. Gotta double it up ¯\_(ツ)_/¯

@hxii@0xff.nu Recursion is the best recursion!

@xuu@txt.sour.is @hxii@0xff.nu example: https://txt.sour.is/conv/ls4ef4a

@hxii@0xff.nu There is another twter that uses !<wikiword wikiaddr> or !wikiword for their wiki intigrations.

@thewismit@blog.thewismit.com @prologic@twtxt.net I too wonder about this.

@prologic@twtxt.net @thewismit@blog.thewismit.com () possible, or a pod following any feeds it finds, if any one follows or not. So it has more twts cached

@prologic@twtxt.net @thewismit@blog.thewismit.com () Ya I get that error a lot. I mostly use the web on mobile as a result.

@thewismit@blog.thewismit.com Soo all good all round? 🤗

@xuu@txt.sour.is yikes the style sheet for blogs needs help.

@prologic@twtxt.net () Wrote up a blog post here: https://txt.sour.is/blog/xuu/2020/12/21/twtxt-auto-discovery

New Blog Post Twtxt Auto Discovery by @xuu@txt.sour.is 📝

New Blog Post Test Blog by @xuu@txt.sour.is 📝

https://whynotsecurity.com/blog/teamviewer/

@tdemin@tdemin.github.io @benaiah@benaiah.me I second Jekyll.

A short-and-sweet article on principles of successful teams: https://blog.brunomiranda.com/principles-of-successful-software-engineering-teams-41a65bfd56b3