1. 3

      oops I didn’t find it with a quick search

    1. 5

      I usually try some kind of command line tool that interacts with a http API so I can get a feel of the package management if any, the libs available, how to read the stdlib and libs documentation… or a basic http/gopher/irc server.

      1. 1

        My lobste.rs packages for helm and ivy are not listed, color me disappointed 😬

        1. 1

          I’ve settled on soft-morning on emacs https://github.com/mswift42/soft-morning-theme Not sure it exists for other editors.

          1. 54

            Getting married :)

            1. 6

              Congrats!

            1. 4

              A reminder I created a Gopher version too. Unfortunately I don’t host it because I’m slightly concerned about hitting the servers too hard as a third party; maybe I’ll get around to fixing that.

              1. 3

                I’ve got one too :)

                gopher gopher://sdf.org/1/users/julienxx/Lobste.rs

                1. 2

                  In the past year I’ve had to send out one abuse report for excessive traffic to lobste.rs. A crawler was making multiple simultaneous and systemic page requests and impacting service for everyone else. That is something that is difficult to do accidentally: any caching, rate limiting, or request economization is probably sufficient–a protocol front-end like Gopher or Finger aren’t, prima facie, excessive or inappropriate in the same way this scraper was.

                  That said, the IRC bot announces new story submissions using push (email) notifications. I did this to avoid polling out of the same concern you have here. We are in control of our entire stack, and so have the luxury of being able to solve resource or request problems end-to-end as folk discover or develop means of interacting with the site and community. Any of you are welcome in #lobsters if you have questions or concerns about whether your software is a burden on the servers or our community.

                  1. 2

                    Thanks for the warning! Both my finger & gopher toys are hitting the /hottest.json endpoint and they do some caching of the response for several minutes.

                    Given the popularity of these protocols I guess they’re not adding too much pressure on the lobste.rs stack :)

                    1. 2

                      Both my finger & gopher toys are hitting the /hottest.json

                      That is what it’s for. The two most popular endpoints are / (17.7% of hits over the past year) and /rss (18.9% of hits over the past year). /hottest.json by comparison is 0.7% of hits for the same time period.

                      Given the popularity of these protocols I guess they’re not adding too much pressure on the lobste.rs stack

                      Correct. And good work @julienxx, @calvin, and other folk developing on or for Internet protocols that are not HTTP.

                1. 6

                  Nice one!

                  Given that finger(1) is a standard tool @$WORK, I like this even more! :^)

                  Edit:

                  Hmm… the last two posts are clumped together like so:

                  [1] - Dad style programming jokes
                  http://github.com/wesbos/dad-jokes
                  Submitted Wed Jan  9 10:09:11 2019 by 8bithero | programming
                  [2] - Get lobste.rs stories with finger(1)      URL:https://lobste.rs/s/3xpycv
                  Submitted Wed Jan  9 10:05:56 2019 by julienxx | meta, show, unix
                  

                  Quite meta - yes, I know ;^)

                  Also, how do I get the 2nd and subsequent pages?

                  1. 3

                    I’m curious what you do for work that finger is still a standard tool.

                    1. 2

                      We’re running a modified version of fingerd(8) which gives us some extra information like people’s email addresses, their location, etc. - lookup, essentially.

                    2. 1

                      Thanks, I fixed the issue with URL-less stories. There is no page 2 at the moment, only the 25 hottest stories.

                      1. 2

                        That was super-speedy! Thanks! :^)

                        While we’re at the subject of URLs, any chance for both, the main story and the comments, to be included?

                        1. 1

                          I could do that, thanks for the suggestion :)

                          1. 1

                            Added the link to comments.

                      1. 4

                        One thing I changed in my work PRs is explaining in details why this PR exist and what are the big changes, what can break, what to pay attention to… instead of just referencing a ticket. I think it makes it easier to review.

                        1. 7

                          Having worked on a code base that is on its 3rd version control system and 4th ticketing system, I’ll tell you - put the comment in the commit message! It’s more likely that the info will survive there than migrated correctly in the ticketing system. This can make for some duplication, but isn’t too bad.

                          The other point I usually make in favor of commit messages is that unlike other code comments, they reflect an exact point in time and

                          1. 1

                            they reflect an exact point in time and

                            stroke?

                            1. 3

                              oops, thanks for catching that.

                              an exact point in time and

                              code changes afterwards might make them (obviously) out of sync with the comment. Regular comments can linger past the code they are commenting, but a commit message is tied to the code at that time.

                          2. 4

                            I have found that often my “rationale” sections on PRs are the longest-lasting written description of the business reasons behind changes. JIRA is not a reliable source of human information so much as it is a glorified to-do list on most projects I’ve been on.

                          1. 4

                            I’m @julienxx@mastodon.sdf.org mostly posting about programming and gopher.

                            1. 4

                              Working on my making my OpenBSD tilde server. So far I have SSH, Gopher, HTTP and Git figured out. I still need some more services, a good skel and it should be good to go.

                              1. 6

                                Here is a shot I submitted to r/unixporn. It’s i3 with a Solaris CDE inspired theme I created. My computer is a Dell XPS 9360, a Vortex Vibe keyboard and a new Microsoft Intellimouse. Time is spent mostly in Emacs coding. Since I dont’t use an external monitor, I use i3 with one app per workspace usually.

                                1. 1

                                  What’s the file manager there, if I may ask?

                                  1. 1

                                    It’s SpaceFM with MacOS classic icons.

                                  2. 1

                                    Damn man, what a beautiful theme. Wouldn’t mind if you shared it :)

                                    1. 1

                                      Sure, everything should be here https://github.com/julienXX/i3config

                                  1. 4

                                    Between copyright, first amendment, free speech and guns I guess it’s really the most American story I’ve ever read 😬 The issue is interesting, too bad it about a friggin gun.

                                    1. 5

                                      Hi I’m Julien, I wrote some technical stuff on http://julienblanchard.com. Nowadays it seems I update my phlog more frequently gopher://sdf.org:70/1/users/julienxx/Log (no feed yet).

                                      1. 5

                                        Anything I could make better besides the code?

                                        Text escaping. Quotes on this page turn into… something eldritch.

                                        calvin commented: I wrote one, but haven’t deployed it anywhere.

                                        http://gopher.floodgap.com/gopher/gw?gopher://sdf.org:70/0/users/julienxx/Lobste.rs/szbati.txt

                                        1. 7

                                          It gets better with every requote.

                                          Somebody, somewhere, is reading utf-8 bytes and interpreting as latin1 characters, then outputting utf-8.

                                          1. 10

                                            Just about the vintage experience I’d expect from Gopher :^]

                                          2. 2

                                            Updated the code to replace some of the problematic chars, hopefully it should look better now.

                                            1. 1

                                              Seems it related to how Floodgap parses the thing. With a real gopher client it looks okay :/

                                              1. 1

                                                Hmm actually it looks weird too sometimes. I’ll have a look. Thanks for the heads up!

                                              1. 9

                                                I wrote one, but haven’t deployed it anywhere.

                                                1. 1

                                                  Oh cool I’ll have a look at it to see what I can steal from your implementation :)

                                                1. 4

                                                  I didn’t know what was Gopher before and still not sure what it is (will read more on that). I find Lobster already a pretty good interface without much distraction since it’s mostly text, so I don’t know what I would really use it for. What would be the use of this over lobster?

                                                  Nice work and it’s loads really fast.

                                                  1. 4

                                                    Gopher is an old protocol, I mean it predates the world wide web so it’s not about making an alternative UI to lobste.rs on http:// but on gopher:// for people who like to live in a plain-text world. See https://gopher.floodgap.com/overbite/relevance.html for more informations on gopher.

                                                    1. 6

                                                      live in a plain-text world

                                                      Except that gopher doesn’t guarantee plain-text (in practise any file type can be served). IIRC the main advantage of Gopher is that it has a standard format for navigation.

                                                      1. 4

                                                        Interestingly enough, Gopher and the web are roughly the same age - Gopher was publicly released in 1991, the same year as Tim Berners-Lee’s original announcement to alt.hypertext.

                                                    1. 1

                                                      I use a Vortex Vibe, it’s programmable but I don’t do it, I’ve just remapped caps-lock to control.

                                                      1. 1

                                                        Did my first internship coding some PHP on an Indy. Loved this system.

                                                        1. 1

                                                          Using fastmail and very happy with it, protonmail looks like a nice alternative too.

                                                          1. 2

                                                            I keep a journal of my workday for the last 6 months and I wrote this article to explain how I do it https://lobste.rs/s/ksmgwe/journaling_my_life_at_work_using_github