1.  

    This was discussed on that other link aggregation site earlier. Blue Coat was mentioned in that thread, and that works by stripping SSL locally before sending it onto the internet. Basically, that should be impossible to get around.

    Other web filters work by both redirecting DNS to a block page, or, if a custom DNS is set, it does a reverse DNS lookup for the server IP.

    1.  

      Do you know what product is being used to block the .rs ccTLD? Are you able to describe technically how the blocking is being accomplished?

      EDIT: When you’re next logged in at work, I’d appreciate it if you could get a screenshot or error message of the site being blocked and email it to me.

      1.  

        Stuff like mass-market browsers are designed for the lowest common denominator of user behavior.

        It shouldn’t be surprising that more and more people fall outside Mozilla’s supported use cases, as Mozilla keeps pushing “our way or the highway” on how their users have to use their browser.

        1.  

          You could always use toe gopher mirror, unless the protocol is blocked.

          1.  

            I can’t use Lobsters at work because of the rs TLD. I actually wish someone would just give it another URL so I could hit it

            1.  

              Last month an iOS user reported they had difficulty selecting the comment link at all. We confirmed the problem and got it fixed.

              Would you mind if I transcribed your comment here in to a ticket? If you haven’t tried in the last month it’s worth seeing if the above patch was sufficient. Otherwise we’ll confirm it and see what we can do.

              1.  

                I’ve personally always struggled with Lobste.rs on mobile. On my iPhone in portrait mode, I’ve never been able to long press the comment count on the right side, in order to pop up the menu that allows me to open up the comments in a new tab. Lobste.rs seems to ignore my long press. I can, of course, just tap it, but then I lose my place on the main page.

                As a result, I always have to use Lobste.rs in landscape mode. So I wouldn’t say the website works perfect on mobile…

                1.  

                  I didn’t think I’d get as much great tips from a listicle, much better than I expected. Kudos!

                  1.  

                    the binary is somewhat large (due to flutter needing to have its entire library in there)

                    I briefly looked into using Scala for Android apps a while back and I remember there were a number of people who talked about tree shaking plugins in their build process (build tools that would check to see what functions are actually used and remove all the other unhandled paths). I never actually went down this path, so I’m not sure if/how well they worked, but maybe there’s something similar for flutter/dart to get file sizes under control?

                    1.  

                      Yeah, so many things have been eroded by Unix and the web - VMS, (everything is a POSIX app there) Mac OS, (Unix hijacked it, and now the web and mobile ports will slowly eat at its native ecosystem) AS/400, (everything new runs in the (slow) AIX compatibility layer due to IBM cost-cutting) and now Windows.

                      1.  

                        I picked up 99% if my SQL knowledge on the job. My first job offered to pay for Microsoft certificates test taking, so I went and got the MCTS in SQL Server 2008. It was a good introduction to all the various features of SQL Server. Not sure that this qualified me as an expert, but I definitely have a decent feel for the SQL server feature set. I suspect there are similar resources for MySql, Postgresql and so on.

                        Since then, it’s mostly just been the odd thing here or there. If SQL interests you, I definitely recommend either getting a book, or reading up on things like window functions, (recursive) common table expressions materialized/indexed views, window functions, how aggregates work, and so on. Digging into the exclusive functionality of the database you use is also recommend There’s some interesting stuff under the hood if you take a look.

                        Probably the most frustrating thing about SQL, however is that most abstraction features, like functions, stored procedures, or views do not compose well from a performance perspective. One layer of them usually works well, two or more is often trouble.

                        1.  

                          Haha, well, to each their own… I happily use Tree Style Tab everyday myself. I am not sure how to browse the web without it anymore… (All of these add-ons have been (re)implemented to use WebExtension APIs that isolate the browser and add-ons from each other in the last year or so… perhaps they are quite different from the last time you checked them, depending on when that was.)

                          1.  

                            the output disappears (in the case of less) as if the pager never ran, so I can’t keep context around.

                            If you want to get rid of this sort of behaviour globally, disable “alternate screen” in your terminal.

                            In tmux, set-window-option -g alternate-screen off. In putty there’s Disable switching to alternate terminal screen under Terminal → Features.

                            1.  

                              absolutely! I work as “red team” (previously in adversary simulation, currently in more technical correctness types of situations), so very often I’m presented with:

                              1. some set of “things” I need to “do” (API calls native or web, some format I need to construct, some code I need to generate many copies of with minor variance, what-have-you)
                              2. a system that I’m not supposed to be on with limited tooling (“living off the land”)
                              3. with a large amount of repetition

                              so often the easiest way is to simply write something in a simpler format that generates the steps above so that attack chains can be more easily constructed.

                              A simple example was that I had Remote Code Execution on a host via two languages (one was the platforms scripting language, the other was native Unix/Windows shell), but only 100 characters at a time (as they were packed in images, with no bindings to Python). So, rather than attempt to write a Python binding or fight with make a generic system using the libraries provided, I:

                              1. wrote a simple description format (creds, commands to be run, host, &c)
                              2. wrote a compiler to the long horrible chain of things I just described that produced “ok” C
                              3. delivered that to team + client for proof of concept

                              it’s a weird example of basically partial evaluation, but it works for me, and is usually easier for me to digest than attempting to get all the moving pieces in one go.

                              1.  

                                Despite being a satisfied user of “the *nix way” of doing things, I am a bit saddened by the outlook of a *nix monoculture.

                                1.  

                                  This seems to be the way many OSS projects run now. The core is open source which usually has everything individuals need and then extras are proprietary which are needed for large corporate projects. Its called “Open Core” for people who want to search it. Gitlab even has the source for the paid features public but the license doesn’t let you use it without paying.

                                  It does have some issues though. The major one being what happens when someone replicates your paid features. Gitlab says they will accept pull requests that recreate their paid features but they also have the resources to create 20 more by next month. As a solo dev, having someone recreate your paid features could cut out all of your revenue.

                                  1.  

                                    Had a similar experience for devs of less known things. I bet ~90% of devs would love an email showing appreciation for their project but I imagine it would get kind of annoying after getting too many emails.

                                    1. 12

                                      Please consider having it published on F-Droid!

                                      1.  

                                        IMHO this is a very useful observation. Maybe we should build a culture that tolerates little paid gimmicks on top of open source projects so that you can justify what’s effectively a donation.

                                        1.  

                                          I second this. -c would be helpful in $PAGER as well so that everything above on your screen stays untouched.

                                          Personally, I’ve been rolling with this:

                                          $ type le
                                          le is an alias for 'less -FcmNqX --follow-name'