Threads for jcs

  1. 7

    One could also connect it with an ATA to a server running Asterisk to do coin detection and then build your own red box to bypass it :)

    1. 1

      I’m not articulate enough to say exactly why, but I very much want to do this for some reason. I’ve even got my old tone dialer from the 90s in the same drawer as a bunch of thumb drives.

      1. 2

        The idea of doing that much work and then not alphabetizing is amazing to me. Looks back at piles of cables everywhere in smug superiority knowing at least they aren’t in random order… er… wait.

        1. 1

          This is what I do, only I keep several cables per bag, with broader categories like USB-C or audio. I have so many Ethernet cables though that I have individual bags by length.

        1. 7

          Really cool project, and great to see homegrown home automation as opposed to it all running on a “cloud” which can disappear at any time.

          1. 8

            Maybe it’s my age showing, but I’m reluctant to deploy home-grown automation solutions because they inevitably break or others in the house get frustrated with them.

            My garage monitoring solution is an off-the-shelf Z-wave garage door tilt sensor that sends updates to my Z-wave network, which are picked up by Indigo running on a Mac Mini. This starts a timer and sends a Pushover notification to my wife and me if the garage door is left open for more than 10 minutes.

            1. 3

              Maybe it’s my age showing, but I’m reluctant to deploy home-grown automation solutions because they inevitably break or others in the house get frustrated with them.

              This was front of mind when building this project. I tried hard to reduce the surface area of breakage in this project by stripping the system image down a lot. Time will tell I suppose :)

              1. 2

                I’m with you there. I have the same setup, but with node-red. This particular sensor is on Zigbee, but the door controller is on Z-wave. I want local control, but for technical ownership of these problems I want as close to zero as possible.

                1. 2

                  Their is always a risk with external services being not available anymore, like Insteon Shutdown. But I really dislike “face-lifts” or behaviour/feature changes for apps. It’s annoying and most often this change doesn’t have a benefit for me. Something like a rearrangement of products in your favourite supermarket. I try to use simple solution to avoid the not working frustration. For my Hue lights I just used two modes (bright or dimmed) which I can set with a text message to my XMPP bot. I also use this bot to get the current outside temperature or to send me a reminder via email.

              1. 15

                A tip for taking photos of CRTs if you have an iPhone: take it as a live photo and then view it in Photos, tap the Live in the upper left corner, and change it to Long Exposure. The refresh lines will be gone and if you held the camera still enough, the screen will still be clear.

                1. 2

                  THANK YOU! I’m going to give this a shot this morning and hopefully update the pictures.

                1. 4

                  I’ve loved the video series so far. I hope to catch the live stream one day (although can be tricky to get US and AU time zones to overlap).

                  I reckon the only thing missing from this set up is a way to notify folks that jcs is going live. Perhaps a dedicated RSS feed would do? I use Feedbin Notifier to get push notifications from a subset of my subscriptions, so could add it there.

                  1. 4

                    Hi, I added a Pushover subscription link on the page.

                    1. 1

                      Great, thanks. Subscribed.

                      1. 1

                        It’s free to try out for 5 days and get notifications from jcs live and many others.

                        This text should probably be updated 😅 (surprised it’s 5 days - I don’t remember a time when the trial wasn’t 7 days.)

                        1. 3

                          Fixed, thanks. It changed from 5 to 7 days in 2015 after Apple complained (and then to 30 days last year).

                    1. 22

                      I’m unsure if Peter has the spare time, or if it’s just the bare minimum to keep the site up and not go up in troll-flames. There was a we need a new moderator-post some time ago but as far as I know there are no nee moderators.

                      It might not be unwillingness, but rather a lack of time. Pure speculation of course, but that’s the first thing that comes to my mind.

                      1. 16

                        We had a pretty responsive moderator back when @alynpost was around, but that is no longer the case. We had a remarkably interesting precedent of community-advised autocracy under @jcs and later @pushcx–that’s probably the most interesting/endearing part of Lobsters to me, and one that I think has mostly passed (much to my dismay). According to the mod log, we have been operating with only one mod for at least a few months.

                        @pushcx has made oblique references (if my reading was correct) to some non-Lobsters circumstances drawing attention away (which is quite fine, since there is in fact a life outside the red site). Regrettably, the structure of governance for Lobsters is not robust when that happens.

                        I have various critiques on how we get here, but I think it is sufficient to state that: Lobsters functions best with a very involved community, people focusing on tech instead of other things, and processes/mods engaged on a daily basis; but, I do not believe that we are currently in that operating regime.

                        Sorry to all of the folks who’ve put such effort into writing up good tagging proposals. :(

                        1. 17

                          :(

                          1. 9

                            <3 we’re doing our best, and I do believe the site will be around for many years to come

                          2. 16

                            Yeah, I agree that the site does need attention from mods to be its best, and there isn’t as much of that to go around lately. With that said, I do think very highly of Lobste.rs users, and I think all y’all should give yourselves credit. The quality of discussions has largely remained high even during periods when mods have been busy elsewhere, and I think that’s the result of everyone’s hard work, not just the few of us with authority.

                            My overall philosophy on things like this (but please understand that this is my personal view, not the view of the site) is that top-down moderation can only ever scale so far - but that’s okay, because when everyone in the community is committed to making it the best it can be, and feels empowered to gently guide things back on-track, that scales to any size.

                            1. 3

                              I can see how you’d get this impression from the mod log, but I’m certainly not alone. The mod channel on IRC also includes the chat mods (@355e3b and @aleph). We’re in different time zones on different schedules, so there’s pretty much always a running discussion as we talk through issues.

                          1. 3

                            Unfortunately, I believe this domain runs afoul of the rules for the .cat domain

                            1. 10

                              The non-user-generated content is translated into Catalan if your browser’s language is set to “ca”.

                              1. 1

                                so does https://www.nyan.cat/ and that has been around for 10 years. I guess nobody really cares?

                                1. 2

                                  https://twitter.com/huy/status/373161206317477888?t=3pap76DQ2Dk7n4tHMZz69Q&s=19

                                  They do seem to audit periodically (this is a tweet from the creator of nyan.cat).

                                  1. 1

                                    https://www.nyan.cat is available in catalan, if you use the menu in the upper left corner of the page. But I bet nobody really cares :)

                                1. 16

                                  On OpenBSD just prefix the command with -s and it will only be allowed to run once from cron.

                                  1. 1

                                    Thus finding the correct answer.

                                    There comes a time in every tool’s life where someone will use it outside its intended scope.

                                    At that time, reinvent the wheel to work for your needs. In this case, reinvent cron (either new forks, new implementations, or new tools altogether.

                                    Like OpenBSD’s cron.

                                  1. 5

                                    This is a great writeup of an interesting and attractive build, but looking at that low laptop-like monitor position is making my neck ache… 🙂

                                    1. 2

                                      Same! Most ergonomics guides I’ve read advise you to position your monitor with the top edge roughly at eye level. (“Eye level” as you’re looking straight in front of you, not hunched over.) Having a monitor on an adjustable arm is generally one of the big advantages of not using a laptop!

                                      1. 5

                                        I think the wide-angle photo of my desk made it look like the monitor was much more reclined than it is. Here’s a side photo.

                                        1. 1

                                          would be nice if you could share your window manager config. please ?

                                          1. 1
                                          2. 1

                                            Nope, I got it right at the first photo. It looks as painfully reclined as in the first set of pics.

                                      1. 4

                                        I could have sworn I implemented this already many years ago but it seems I’m imagining things. It was a “fork” link shown on each comment to moderators that would break it and its children into its own thread, which had a link back to its original position in the original thread. It wouldn’t happen automatically in response to voting because it would fragment things too much, but moderators could allow large off-topic threads to live on their own in a new root-level thread.

                                        1. 45

                                          Is this a paid position?

                                          1. 60

                                            Rather the opposite for you, I have a stack of past-due therapy bills you’re delinquent on.

                                            1. 7

                                              There’s always the option for cathartic revenge by assigning him the Victor Frankenstein hat.

                                              1. 10

                                                Please, let’s be reasonable here. He should delegate assigning the hat to one of the new mods.

                                          1. 4

                                            So, uh… I see that Passing the torch is tagged as “meta” and Migration Date and Plans is tagged as “announce” but otherwise, there’s nothing to distinguish these threads as anything particularly special. They aren’t, like, pinned to the home page, or listed at the top of the index, or highlighted as anything fancier than the rest of the stuff under their respective tag markers.

                                            I guess this means these threads are roughly as significant as any of their peers. Or, maybe I should just decide for myself, based on all the information I have available, and go with that, whether my hunch is right or wrong, and everyone else can just point and laugh, as usual.

                                            Anyway, figure they’ll get buried in a day, and we can all just move on with our lives.

                                            1. 2

                                              P.S. Thanks for pinning this as the top thread! Figure it’s relevant enough, since user action is prescribed for users interested in preserving or destroying information before the hand-off.

                                              1. 2

                                                Lobsters doesn’t have any thread/comment pinning features - this thread is at the top of the homepage solely due to upvoting of the story and its comments.

                                                FWIW, I originally tagged this thread meta and jcs retagged it with announce, as visible in the moderation log.

                                                1. 12

                                                  Actually, I cheated and made the hotness_mod of the announce tag really high so it will stay at the top of the front page for a considerable amount of time. It was already falling down to number 3 the other day.

                                              1. 6

                                                If you want to export your messages before the migration, I added JSON interfaces for your inbox and sent messages:

                                                1. 31

                                                  I will be deleting all private messages before handing over the database, just for increased privacy in the event someone doesn’t see this before the hand-off. I’ll have a backup in case there is some critical info in a message that gets deleted, but I’d rather err on the side of caution.

                                                  1. 2

                                                    Wait, so are all messages getting zorched or not?

                                                    1. 11

                                                      I will back them up, delete them from the database, then give the dump to @pushcx. So the site on his hardware will have no private message records in it, but if someone urgently needs something from the backup, I can manually fetch it for them.

                                                    2. 2

                                                      Great, then the only other thing for folks to do is change their email address if they don’t want me to see it - anything @mailinator.com should work fine.

                                                      1. 4

                                                        I’ll probably change all deleted accounts to have an email at @lobste.rs before the dump as well.

                                                        1. 30

                                                          Might I suggest @localhost instead? In case lobsters emails are valid someday.

                                                      2. 1

                                                        Perhaps there could be a setting that you don’t want your messages deleted?

                                                      1. 151

                                                        Hi jcs,

                                                        In an attempt to preserve a community which has been a large part of our lives for a better part of the last few years, @angersock @pushcx @355e3b @alynpost and a few other of the IRC folks feel that we can take over running the website. @alynpost will be able to provide the hosting in Santa Clara, CA under pgrmr’s infrastructure. @pushcx will assume the role of head administrator and take over the domain name along with the Twitter account. @355e3b and @aleph- will take over the care and feeding of the Rails codebase.

                                                        We will not be making any moderation changes at this time—continuity is the important thing.

                                                        Our transition plan is as follows:

                                                        • @pushcx will take over the domain name and Twitter account; @angersock will also have access to resolve emergencies.
                                                        • @pushcx will set up a GitHub organization to own the repository long-term.
                                                        • @alynpost will provision new hardware.
                                                        • @355e3b and @aleph- will take over the administration of the IRC channel on Freenode.
                                                        • @alynpost will invoice @angersock, @pushcx and @355e3b for the costs of running the server long-term.
                                                        • @pushcx and @alynpost will pick a deadline by which anyone who wants their private messages or email address deleted should request it. Once that date has passed, we will pick a date and time for the migration to occur.

                                                        This is solely to ensure continued hosting and maintenance of the website, and a continuation of the community. Long-term, if the existing moderators wish to step down, @pushcx will be responsible for picking new candidates.

                                                        We would also like to thank you for all of your years of work put into this.

                                                        ― #lobsters IRC regulars (aka the clawlateral committee)

                                                        1. 79

                                                          And I assume @tedu will be in charge of the TLS certificates?

                                                          1. 22

                                                            This comment made me super happy :D - Thanks!

                                                            1. 2

                                                              Joker!

                                                            2. 57

                                                              That sounds like a great plan, thanks for putting that together. I’ll feel better knowing the site will be managed by a group instead of falling all on one person.

                                                              1. 22

                                                                Glad to see your approval. :)

                                                                /u/pushcx should be the central point of contact for the migration deets. We’ll keep the community updated!

                                                                1. 26

                                                                  Great! We’re really happy to step up and take good care of a community we love.

                                                                  And, for the community: the first update is that I just started an email discussion with me, jcs, and alynpost to handle the technical details of the migration. I’ve migrated barnacl.es a few times, so I’m familiar with the procedure. My guess for a timeline is two weeks, but that’ll be adjusted if needed. I’ll post a comment in this thread when we’ve picked a date or there’s otherwise news.

                                                              2. 18

                                                                This sounds great. I’m thrilled to see people working together on this. :)

                                                                1. 10

                                                                  I got back from talking to the people planning out the transition (aleph, push, socky, goodger, alyn, 355, irenes) on Mumble and IRC - they’ve all been wonderful people putting in their best to ensure the community will experience a smooth transition and avoid any turmoil.

                                                                  1. 10

                                                                    Awesome, glad to have regulars and good people taking things over.

                                                                    I would strongly recommend, and as a lobste.rs regular personally request that as a group you take a bit of time to define some basic agreement about decision making and ownership, so that it is clear between you all, and also to the community.

                                                                    This is not a problem when there’s one guy in charge - it’s simple and clear and whether you agree with them or not you have consistency and stability (thanks @jcs !)

                                                                    When there’s more than one, you need extremely strong value alignment and high levels of trust. If you guys have not known each other for 5+ years and can meet in the same bar to share a beer, you need to talk about and get down some basics. Who makes decisions, how, when; who is in control of the domain / hosting / features / community management.

                                                                    Personally, I like the ‘benevolent dictator’ situation. It reduces ambiguity and facilitates short sharp clear decisions. Greater than 2 people needs work to define that recognises that you will eventually have a conflict, that some of you will come and go, and that there is no way you can all have perfect understanding of what each other wants for this community and what your values are.

                                                                    Not doing this is a valid choice too; equal to commitment to cede to whoever has ‘root’ and control of the hosting and then domains if a conflict happens, and requiring proactively thinking about forking / commuity splits.

                                                                    1. 6

                                                                      The way that I personally view it is, @pushcx will step into @jcs’s role and take over as the benevolent dictator.

                                                                      1. 2

                                                                        Is that what you’re thinking too @pushcx ?

                                                                        1. 10

                                                                          That’s the current plan I’m executing on, yes. I want to continue this excellent community. Lobsters is in a good place: we have a healthy, active userbase, the code is stable, bug-free, and has little need for new features, and I’m on sabbatical so I have plenty of time and attention to devote to a smooth transition.

                                                                          After the migration is complete I think it’s worth having a new meta thread about if we want to shift to a new community governance model. I’m comfortable being BD for years if not indefinitely, but there’s enough folks talking about community models that I want to have a dedicated discussion to explore examples and consider the option.

                                                                      2. 4

                                                                        One of the guiding principles we talked about a lot during the clawlateral committee meeting was that we wanted to stray as little as possible from the existing governance structure for the time being–the site has done well in its current incarnation, and @pushcx is we believe a good steward to carry on the precedent set by @jcs.

                                                                        The plan explicitly has redundancy in roles (think failover) for all important things you mentioned. We also tried to follow a principle of least-trust and a little bit of separation of powers for the failover folks, so that continuity of service is easy but forking and hijacking is hard.

                                                                      3. 6

                                                                        Thank you all. I work a lot, don’t know Rails, and don’t really have anything constructive to contribute, but this is far and away the best signal to noise community I’m involved with and I really appreciate it.

                                                                        If throwing money at the problem will help the new maintainers along please consider setting something up and I’ll chip in.

                                                                        1. 4

                                                                          They said they should be able to pay for everything out of pocket, as far as I know.

                                                                        2. 6

                                                                          Does this mean we can finally get an @angersock plushie?

                                                                          1. 2

                                                                            You guys were my first thought when I saw this post lol. Thanks for your continued commitment to the community ~

                                                                            1. 1

                                                                              Thanks @angersock, @pushcx, @355e3b, @alynpost!

                                                                              I’d hate to see lobsters die!

                                                                              1. 1

                                                                                I love how fast this plan was put together and I feel it will be in good hands. I was scared seeing this post and am excited to see the community I love will keep going and be in good hands!

                                                                              1. 5

                                                                                Added

                                                                                1. 2

                                                                                  fantastic ?

                                                                                1. 12

                                                                                  Added.

                                                                                  1. 3

                                                                                    Thanks!

                                                                                  1. 10

                                                                                    work: adding support for UDP Options to FreeBSD while trying not to mangle the network code too much.

                                                                                    !work: More work on drivers for my GPD Pocket. I figured out the ACPI junk to get most of the power related stuff attaching to i2c buses described there, but I have hit a snag with ig4 where it times out transfers. While avoiding looking at that I found OpenBSD has a driver for the gpio(chvgpio) so I am porting that to FreeBSD now.

                                                                                    1. 4

                                                                                      What are you planning to do for the Broadcom wireless?

                                                                                      1. 3

                                                                                        I am using a tiny usb dongle right now, tear downs have shown there is no way to replace the internal card. The wireless is the same as the pi3(though pci) and there is an effort right now to add support for the colocation controller on the soc. It might actually be a card that sees support in the next year or two.

                                                                                        1. 4

                                                                                          The corresponding Linux brcmfmac driver is ISC licensed.

                                                                                    1. 3

                                                                                      I appear to be hitting an ssl exception on this URL. Something about the certificate issuer being unknown.

                                                                                      1. 6

                                                                                        @tedu hasn’t gotten to the book about CA infrastructure yet

                                                                                        1. 2

                                                                                          Lol. Oh he has. @tedu went further to launch a small-scale experiment on the psychological effects of highly-technical users encountering SSL problems on the homepage of someone they expect understands security. Aside from personal amusement, he probably focused on categorizing them from how many ignore them to quick suggestions to in-depth arguments. He follows up with a sub-study on the quality of those arguments mining them for things that will appeal to the masses. He’ll then extrapolate the patterns he finds to discussions in tech forums in general. He’ll then submit the results to Security and Online Behavior 2018.

                                                                                          Every tedu story on Lobsters having a complaint about this is the fun part of the study for him. A break from all the tedium of cataloging and analyzing the responses. On that, how bout a Joker Meme: “If a random site by careless admins generate CA errors, then the IT pro’s think that’s all part of the plan. Let one, security-conscious admin have his own CA and then everybody loses their minds!”

                                                                                          1. 2

                                                                                            Not far from the truth.

                                                                                            1. 2

                                                                                              He’ll pay the $$$ and jump through hoops for DNS; but, the CA system— the line is drawn here!

                                                                                              1. 2

                                                                                                Well, domain names are scarce in a way that RSA keys aren’t, and have unevenly distributed value. My domain name was not randomly generated. :)

                                                                                                1. 1
                                                                                                  tedunangst.com name server ns-434.awsdns-54.com.
                                                                                                  tedunangst.com name server ns-607.awsdns-11.net.
                                                                                                  tedunangst.com name server ns-1775.awsdns-29.co.uk.
                                                                                                  tedunangst.com name server ns-1312.awsdns-36.org.
                                                                                                  

                                                                                                  Did you ask for people to add your nameservers to their resolver roots?

                                                                                                  Domain names and RSA keys are equally scarce. It’s all protection money, for root servers and for root CAs.

                                                                                        1. 6

                                                                                          Anyone know if any browsers explicitly define their caching semantics for what they store, for a live-streamed object which is never “terminated”? This isn’t server-push object replacement, after all, but one object which has internal framing, and so keeps getting larger. So if the 4kB/sec claim on the page is right, then if you leave the browser open for a day then that’s a third of a GB. I know people who can forget their browser tabs for days on end.

                                                                                          1. 4

                                                                                            I remember on older webcams, their web interfaces could stream video via motion JPEGs, which just sends endless JPEG frames to the browser. I don’t think it was a problem back then even for those old browsers.

                                                                                            1. 1

                                                                                              I don’t think it was a problem back then even for those old browsers

                                                                                              Even if it was a problem, this was the nineties we’re talking about. People would barely even notice if you crashed their browser or computer and they had to restart it, so long as you didn’t crash it much more than once an hour or so.