1. 6

      Continuing to write a Mattermost bot in Go that keeps score of channel arguments. The first draft is done but it could use a lot of polishing

      1. 8

        That is so…disheartening. But not surprising

        Edit: The Youtube results, not your work (to be clear)

        1. 2

          Thanks for your sensitivity :) but yes I agree. Though if you use the filters for category and channel size the results are a lot less disheartening.

        1. 5

          Going to build a Mattermost bot in Go. It’ll moderate arguments going on in the channel and keep track of points for each participant. And since it’s all good fun, I’ll probably code in a way for folks to try and bribe it by direct messaging it with a sufficient offer

          1. 6

            This is a bit of a rant but I really don’t like software that invents its own query language

            So this post should have the rant tag

            1. 3

              Users can suggest tags.

            1. 17

              I strongly disagree with a CVE tag. If a specific CVE is worth attention it can be submitted under security, most likely with a nice abstract discussing it like the Theo undeadly link or the SSH enumeration issue. Adding a CVE tag will just give a green light to turning lobste.rs in a CVE database copy - I see no added value from that.

              1. 7

                I agree. I think it comes down to the community being very selective about submitting CVEs. The ones that are worth it will either have a technical deep-dive that can be submitted here, or will be so important that we won’t mind a direct link.

                1. 2

                  Although I want to filter them, I agree this could invite more of them. Actually, that’s one of @friendlysock’s own warnings in other threads. The fact that the tags simultaneously are for highlighting and filtering, two contradictory things, might be a weakness of using them vs some alternative. It also might be fundamentally inescapable aspect of a good, design choice. I’m not sure. Probably worth some contemplation.

                  1. 2

                    I completely agree with you. I enjoy reading great technical blog posts about people dissecting software and explaining what went wrong and how to mitigate. I want more of that.

                    I don’t enjoy ratings and CVSS scores. I’d rather not encourage people by blessing it with a tag.

                  1. 6

                    I object!

                    Just kidding, thanks for the hard work @alynpost

                    1. 11

                      You should add Paperkast to the list of sister sites.

                      1. 2

                        Done. Thank you very much for the suggestion.

                        1. 1

                          Maybe there should be some sort of standardized directory?…

                          1. 2

                            How is https://github.com/lobsters/lobsters/wiki not a standardized directory?

                            1. 4

                              I suppose it is, but it was not obvious to discover.

                              1. 1

                                I also wish I’d discovered it sooner. However, other than nesting it under the “Wiki” link at the bottom page, I don’t see a solution that wouldn’t start cluttering up the site with information most people won’t need.

                                1. 3

                                  It’s linked from the about page.

                            2. 1

                              Can you expand it a little bit?

                          1. 5

                            Sounds interesting, might solve a problem I have at work, too bad it’s coupled to github =(

                            1. 3

                              What would you prefer it to use as the underlying storage? (I am trying to understand what people actually want.)

                                1. 4

                                  I was thinking of storing everything, including the comments in a git instance, which would work independently of what git frontend you are using, but then I would have to speak git protocol from the browser which sucks. I may have a look at git.js

                                  1. 3

                                    Looking at git.js documentation :(

                                    “I’ve been asking Github to enable CORS headers to their HTTPS git servers, but they’ve refused to do it. This means that a browser can never clone from github because the browser will disallow XHR requests to the domain.”

                                    1. 1

                                      Anything self-hosted would be viable, but everything on git would be even better, although probably more complicated. We use gerrit at work (which sucks at several levels), and mostly anything third-party is very much disallowed. Maybe you could create an abstraction that would speak Github API to github and git protocol to other servers where this would work?

                                      The other possibility could be a sort of optional backend/proxy, so, if the git server doesn’t have CORS, you could spin that optional server.

                                      1. 2

                                        After thinking about it some more, there’s a lot that GitHub offers that I would have to reimplement myself. Authentication, for one thing. If it was used in a stand-alone mode in enterprise, some kind of authentication would be still needed. People would probably want SSO. Then there are notifications. GitHub sends you an email when you are mentioned in a bug. I would have to somehow interact with company’s mail server. And so on. This is my hobby project and I don’t really have time to go into that amount of complexity.

                                        1. 1

                                          Sure, makes sense. It’s still a cool project, nonetheless, so, congrats =)

                                    2. 2

                                      sounds like a job for the backend

                                  2. 1

                                    The only issue that I have with it is sharing my organization details. Although you could do it manually, I’m always a bit annoyed about this.

                                1. 4

                                  Well, the same thing as the last time: porting my IRC daemon from C to Go. I’ve had some problems with motivation, though that has sorted itself out and now I have before me the task of rewriting about 4000 lines of fairly straight-forward “business logic” code. It’s mind-numbingly boring and fairly time-consuming.

                                  Since this is part of an over-ambitious project where I replace most GUI/TUI applications that I use, this rewrite being a warm-up exercise for Go in a problem domain that I’m comfortable with, I am considering starting a blog-of-sorts. I’m not sure if I could keep it alive for long as one needs to remember to describe the steps he takes and put them in context for readers which, needless to say, takes its time, but also as a side effect often provides interesting insights. There’s definitely a lot to write about.

                                  What does one use to share a stream of short updates? I don’t feel like spamming an aggregator with them would be very productive and summarizing events at fixed time intervals seems like a hassle.

                                  1. 4

                                    I’d recommend http://jrnl.sh/ if you want to quickly do streams of updates directly from command-line.

                                    I personally like my fork which has one additional feature: native exporting directly to HTML https://git.timetoplatypus.com/timetoplatypus/jrnl

                                    1. 2

                                      Keeping a log/record of things you have learned, wanted to share, or ran into in an issue tracker for the project would work probably. Possibly just a markdown file? Makes it easy to at a later date write about the process from beginning to end.

                                      1. 3

                                        Looks good. Definitely interested to hear if the project is open source. I like the snappiness and minimal amount of JavaScript

                                        1. 19

                                          I ran across a pretty interesting talk about zig here.

                                          Note: I got a good laugh at the end of the talk where he said he made tabs in the source a hard compile error. Well played Andrew. ;)

                                          1. 9

                                            I personally loved the whole “Ya I know saying Zig is faster than C is a big statement since programming language performance is measured as a fraction of C, but I’m telling you it’s an improper fraction”

                                            1. 1

                                              Agreed. It was a good presentation – there were a few memorable moments like that.

                                          1. 3

                                            Been using jrnl to keep notes of things I’ve done or ideas I intend to execute on.

                                            1. 1

                                              jrnl is great. I use it as my personal journal.

                                            1. 2

                                              Should have an option to emit TAP

                                              1. 1

                                                +1

                                                I’ll definitely look into that, thanks

                                              1. 1

                                                Why do you have a AUTHORS() macro? Isn’t that why version control is for?

                                                1. 2

                                                  Yep, version control can provide that, but I didn’t want to rely on it being present. I think from a developer standpoint, it’s convenient to know then and there who wrote a particular test (compared to perusing a changelog to find who wrote it). I used this at work and that was my experience, at least.

                                                1. 3

                                                  Nice! Really like the minimalist approach of it.

                                                  1. 3

                                                    Thanks!

                                                    I’m certainly aiming for a minimal front-end. As I write new features, I try to hold to a quote I once heard: “if it needs a manual to work, it’s not ready for production”. Obviously there are exceptions to this, but the spirit of the saying is that features should be as intuitive as possible. So I’m comfortable with the backend code getting sophisticated (and ideally not complicated) as long as writing the tests remains straightforward. I measure straightforwardness by how easy it is to explain a new feature using an example. If it’s difficult to explain using an example, it’s not ready

                                                  1. 1

                                                    This would be a useful extension to tldr

                                                      1. 1

                                                        Ugh, I searched and didn’t see it. Thanks.

                                                        1. 1

                                                          Yup, no problem.

                                                      1. 5

                                                        Love finding writings like this where the author has clearly worked on something very specific, and can articulate nuances that you’d either never think about or wouldn’t think existed (for example, buildings that are numbered zero)

                                                        1. 3

                                                          We need something like that for every category in one place. Plus, premade components in common languages that enforce their best practices by default with escape hatches for some stuff where it makes sense. minimax’s link is a good start.