1. 1

    While these are welcome and substantial improvements, I find myself continually baffled by the trend of putting messenger functionality in everything. App fatigue is real and I feel like we’re just perpetuating it.

    1. 1

      You’re not wrong, but the value here isn’t an attempt to add “me-too” features to Nextcloud, from my understanding. The goal with Nextcloud Talk is to be able to have that messenger functionality in an entirely self-hosted place without relying on third parties. And Nextcloud is starting to develop a network effect significant enough that tying the messenger to Nextcloud is also valuable, instead of embedding XMPP/IRC/Matrix. (Though there is work being done to bridge Nextcloud and XMPP that I’m looking forward to.)

    1. 14

      So who wants to adopt the lobster for lobste.rs?

      1. 6

        why not zoidberg?

        1. 5

          I’m up for donating to a pool for this.

          1. 4

            Agreed with /u/gerikson, I’m up for a donation pool! Who wants to spearhead it?

            1. 15

              I could put together a pool to try to hit the Silver or Gold level. The link would point back to a note on the about page. There would be no reward for donating besides the warm glow of knowing you’ve helped support an organization that is the source of so much error handling in our code.

              Please take this ad-hoc poll by upvoting the single highest amount you’d donate towards this. Enough support and I’ll put something together. (If you made judicious use of your GPU a few years ago and have cryptocurrency to donate, please select the amount of USD you’d convert it into before sending it because I’m game for a fun lark, not a major project.) (Edit: tweeted)

              1. 59

                10 USD

                1. 17

                  1 USD

                  1. 9

                    50 USD

                    1. 4

                      100 USD

                      1. 1

                        This is in progress.

                        1. 1

                          500 USD

                    1. 3

                      I’m using RedHat’s other virtualization product, oVirt, for my personal homelab. It’s quite smooth and very well made.

                      I looked into OpenStack as well, but there’s so many disparate components it cases the installation instructions to be way too complex. I’ve been turned off by the sheer complexity of all the components. (Many of which are optional, so that’s even extra complexity.)

                      I plan on deploying OpenShift soon too, to learn me some Kubernetes. :)

                      1. 2

                        @pushcx, or whomever it applies, I wonder how much memory Lobsters is using?

                        1. 3
                          USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
                          lobsters 30353  0.7  3.0 399412 124800 ?       Sl   00:00   6:20 unicorn_rails worker[7] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30359  0.8  4.2 449504 173164 ?       Sl   00:00   6:39 unicorn_rails worker[10] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30364  0.7  3.0 396484 122156 ?       Sl   00:00   6:24 unicorn_rails worker[4] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30368  0.7  3.0 398528 123688 ?       Sl   00:00   6:16 unicorn_rails worker[3] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30372  0.7  3.1 400852 126092 ?       Sl   00:00   6:15 unicorn_rails worker[0] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30376  0.7  3.0 397540 123052 ?       Sl   00:00   6:19 unicorn_rails worker[8] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30380  0.7  4.6 465020 189584 ?       Sl   00:00   6:25 unicorn_rails worker[1] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30384  0.7  3.0 398656 122660 ?       Sl   00:00   6:15 unicorn_rails worker[6] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30388  0.8  3.0 399388 124456 ?       Sl   00:00   6:33 unicorn_rails worker[9] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30392  0.7  3.0 399352 124268 ?       Sl   00:00   6:05 unicorn_rails worker[5] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30396  0.8  3.0 396560 122720 ?       Sl   00:00   6:35 unicorn_rails worker[2] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 30422  0.7  3.0 400140 124288 ?       Sl   00:00   6:23 unicorn_rails worker[11] -c config/unicorn.conf.rb -E production -D config.ru
                          lobsters 32327  0.0  2.4 235416 97696 ?        Sl   Jan10   0:12 unicorn_rails master -c config/unicorn.conf.rb -E production -D config.ru
                          

                          It’s been two weeks since the service was bounced, so this is stable usage. I know there are issues with ps; if you have a preferred alternate measurement I can check it.

                          1. 1

                            I don’t know what specific problem of ps you are referring to, but if you want to check real memory cost of process (USS/PSS) under linux smem might be good tool.

                        1. 1

                          This is mostly a press release/advertisement of a mobile app. An interesting one perhaps, but I think this is pretty much marketing spam.

                          1. 3

                            I like this. It’s a good idea in theory but the practical deployment of it is surprisingly difficult (tooling is missing) and any mistakes means your website is blocked by the browser’s interstitial with no way around. This concept needed more time to bake, perhaps some tools/patches/plugins written first.

                            1. 2

                              It’s also an attack vector. If a site is compromised an attacker can pin their own cert.

                            1. 5

                              I’m not sure what kind of integration each of the sites would include. I think it would be nice to see a list of other Lobsters-powered websites, perhaps more like a wiki page than anything managed by the admins. A little bit of federation would be cool to port/collate the user’s profile across instances, but that’s about as far as I’d expect such integration to go.

                              1. 7

                                This week I have an in-person interview as a follow up to a phone screening. I hope I get the job! Along with that, I will be submitting my resume to a few more tech companies (both remote positions and a couple I found in the Phoenix valley) for system administration positions. Fingers crossed!

                                In programming news, I’ll be creating a WebRTC signaling server and TURN REST API proxy. I’m developing what amounts to a serverless P2P coder’s notepad, but unfortunately that’s not possible. You still need a couple of servers in today’s internet – the signaling server and the TURN server. (Yay NAT.) So I already have a TURN server, but with just a few hardcoded credentials; not something I can send out along with the JS application code. So using this RFC and coturn I’ll be able to generate ephemeral credentials for each WebRTC session. Hopefully, anyways.

                                1. 1

                                  Are you aware of ArchLinux’s netctl project? It’s based around systemd so it’s not portable to *BSD but the UX might be useful to draw inspiration from. Also, it’s an established project with the name ‘netctl’. :)

                                  1. 1

                                    Not until just now. Given that systemd will never be ported to OpenBSD, I’m Ok with the name collision. ;-)

                                    Thanks for the UX ideas!

                                  1. 3

                                    Would posts related to the Raspberry Pi fit within the tag? Or do they need to include something even smaller for the tag to be appropriately applied?

                                    1. 4

                                      That’s a great question. I specifically avoided mentioning Raspberry Pi since I don’t know the answer. This issue is bigger than the tag suggestion where lots of “embedded systems” over the years are running on what would previously be more like desktop computers. The Pi has quite a bit of hardware running OS’s such as Linux. Yet, it’s also constrained versus a “real” computer we’d use for day to day tasks such as web browsing.

                                      I’d say it comes down to the specs and intended use-case. We should keep this tag for resource-constrained systems that people go for to keep per-unit price dirt cheap, possibly tiny boards, and very hackable. Looking at them, the Pi 3 doesn’t look like a resource-constrained system with a quad core and 1GB of RAM. ;) Even the Pi Zero has 1GHz and 512MB of RAM. Whereas this Arduino’s specs are a lot more like what most embedded boards in consumer devices, appliances, etc would be with 16MHz MCU, 8KB of RAM, and 128KB of flash.

                                      https://www.arduino.cc/en/Main/arduinoBoardMega

                                      You couldn’t even fit a real Linux in that thing. Even the GRUB bootloader at 20-30K couldn’t fit in its RAM (assuming all of it is loaded on startup). So, with these tiny chips, there’s whole different types of OS’s, programming styles, debuggers (some physical), and so on to handle them. You can’t just drop your vanilla stuff on them accepting that it runs slower. You have to do different things or at least chop the software until the result is not much like a full version. For example, the smallest Linux I think got to 600K. It couldn’t even fit.

                                      So, things using MCU’s with tiny RAM and ROM amounts to point they can’t run normal OS’s and toolchains. That’s how I’m defining it. If yall are curious, while we’re at it, here’s the lowest end of embedded that’s still in use:

                                      http://www.embeddedinsights.com/channels/2010/12/10/considerations-for-4-bit-processing/

                                      Previous record holder… a one-bit MCU… with PDF guide to it in references:

                                      https://en.wikipedia.org/wiki/Motorola_MC14500B

                                    1. 6

                                      Can anyone comment to the FUD-meter on this article? I do realize that the article addresses this specifically, but wanted y’all’s input.

                                      1. 5

                                        I think the concerns are quite real. Facebook has a patent on GraphQL but does not liberally license it to users. Which means, currently, that every implementation of GraphQL from outside Facebook, and possibly even every server-side user, is in violation of that patent. Which is a risk. One that doesn’t really need to exist, given Facebook’s willingness to license patents liberally (see React). Facebook’s legal team has been notified, so hopefully this will be resolved.

                                        Until it’s resolved, as I understand it, every server implementation of GraphQL is definitely in violation of Facebook’s patent unless they already have talked with Facebook themselves. (i.e. I expect Github has talked with Facebook a lot already since they’ve been working closely together on a variety of topics already, but did Apollo Server/Meteor talk to Facebook? etc, etc). Client-side implementations, I don’t think so. I am not a lawyer, though.

                                        1. 5

                                          I think the concerns are quite real.

                                          The concerns are quite real, but to say that they’re unique to Facebook/React is bizarre and unfounded; software patents are a huge problem that plague everyone who uses software distributed under a license that doesn’t have an explicit patent grant.

                                          Everyone who uses BSD-licensed or MIT-licensed software is at risk if they operate in a jurisdiction that recognizes software patents.

                                          1. 1

                                            That’s one opinion, and the other one is that BSD and MIT license give implicit patent grant so you (licensee) are not at risk. On the other hand, that can be a risk to licenser (of “losing” patent). So one theory is that this is why Facebook came up with BSD+PATENTS: to replace implicit patent grant with explicit one so that they get protection in exchange of “losing” patent.

                                            You are saying BSD+PATENTS is better than BSD for users. But if BSD does not give any patent grant, why is BSD+PATENTS better than BSD for Facebook? After all, it’s Facebook’s decision, not users’.

                                            1. 1

                                              But if BSD does not give any patent grant, why is BSD+PATENTS better than BSD for Facebook? After all, it’s Facebook’s decision, not users’.

                                              Because accepting external contributions to an OSS codebase that doesn’t have a patent grant is a terrible idea if you operate a business in a jurisdiction that fails to recognize the invalidity of software patents.

                                        2. 1

                                          Over 9000

                                        1. 3

                                          I’d like to turn it around and ask you what you have self-hosted? Always curious what people have chosen. :)

                                          1. 1

                                            (not OP) I’m self-hosting Camlistore for backups (which has been working well so far) and a hacked-together RSS reader (because so many feeds only include a summary and a link to click through).

                                            1. 1

                                              I host my mails (OpenSMTPd as MTA, Dovecot as MDA until the OpenBSD-developers show some mercy and come up with their own implementation of IMAP), my website/s (static placeholder and blog, both via httpd, blog’s Wordpress), instant messaging (XMPP via Prosody, used to run Mattermost for a while), my backups (Arq, to three different physical locations), file synchronisation (recently switched to Nextcloud from ownCloud), torrents (via Transmission - and yes, really not for piracy), .. I’m sure I forgot something.

                                              1. 1

                                                Oh, new podcast! Thanks. :)

                                              1. 4

                                                It makes me sad there there are so many different instant messaging platforms in common use today and they are all proprietary and unfederated walled gardens.

                                                • iMessage
                                                • Skype
                                                • Facebook messenger
                                                • Snapchat
                                                • Google Hangouts
                                                • Google Allo
                                                • WeChat
                                                • SnapChat

                                                I would like for something like XMPP to be successful, but it seems more and more unlikely as time goes on.

                                                1. 4

                                                  I until recently would have agreed. However, I think that Conversations on Android showed that you can make a good client that people seem to be able to agree upon. Having something like that (a dominant, fully featured, yet simple to use) application, maybe web application could make things better again when using XMPP.

                                                  If not I hope that Matrix picks up some steam. It looks promising, however I think it’s too early. Currently the clients are very rough around the corners and only techy people seem to use it. That’s not a complaint, other than against myself, for not helping out - or not having time to.

                                                  This is all based on the assumption that the major reason for not using XMPP is the lack of easily working desktop/mobile sync, especially in combination with encryption. OMEMO to me is the best thing that has happened in a while.

                                                  1. 3

                                                    I’ve sometimes thought that the only reason we have good email interoperability is because there was no profit in running email systems back when the standard was written.

                                                    It seems that there’s no way to create a commons once a market develops. (I’m happy to be proven wrong, and would love to see counterexamples!)

                                                    1. 3

                                                      XMPP is evolving with the times. You can now get end-to-end encryption, and mobile-friendly optimizations that minimize polling and save battery life.

                                                      Android client: https://conversations.im/

                                                      iOS client: https://chatsecure.org/

                                                      Eventual codebase unification: https://chatsecure.org/blog/chatsecure-conversations-zom/

                                                      Riot/Matrix isn’t XMPP but is similarly open: https://matrix.org/docs/projects/client/riot.html

                                                      1. 3

                                                        Not to mention KakaoTalk, WhatsApp, and LINE, which are crazy popular in places that aren’t the US.

                                                        1. 3

                                                          You listed Snapchat twice!

                                                          1. 2

                                                            I think there is a slight difference with iMessage. When it comes to the Mac app, you could plug in all sorts of services that had XMPP as their baseline. This fell apart over time as Facebook, Google, etc. all closed up and in the High Sierra version of Messages you can only add smaller Jabber/XMPP services.

                                                            For a lot of those services, they did start out as open XMPP services, but it’s likely the case that they realized they didn’t want the competition on the client side.

                                                            1. 1

                                                              I think part of the issue has been XMPP’s lack of adoption of new market features, and how hard it’s been to keep up with the pace of innovation throughout the entire XMPP federated network. If those challenges can be made simple, I’d expect there to be an increase in adoption. I don’t know if that would be enough to start chipping away at the network effect however.

                                                            1. 1

                                                              I love the idea. You can take it a step further and send the error alerts to Sentry, either self-hosted or managed. I always appreciate when I see a project support Sentry alerts (Gitlab is an example of a big Rails project that supports sending errors to Sentry. Discourse, too, I believe.)

                                                              1. 6

                                                                For those looking for something similar for Zsh, there is larkey’s excellent work: https://github.com/larkery/zsh-histdb

                                                                1. 1

                                                                  See also, google-webfonts-helper. Seems like there is a healthy desire for an easy to use downloading tool from Google Fonts. I’m happy. :)

                                                                  1. 2

                                                                    FYI, the chrome frame is deprecated and isn’t recommended any more. So you shouldn’t include ,chrome=1 in the meta tag unless you’re specifically dealing with it. (And in that case, hopefully you could convince people to upgrade to Edge. Hopefully.)

                                                                    1. 2

                                                                      I saw the title and was initially quite apprehensive. But looking into it some more, it’s written by Paragonie who also provide commercial support for the C version of libsodium. Pretty cool, and I appreciate bringing most of the primitives to PHP developers running on platforms that don’t support PECL. (Oh how I’d wish they’d go away, but that’d hurt the internet more than it would help I think.)

                                                                      1. 3

                                                                        I don’t know Heroku at all, so these may not actually be a problem. Some easy to identify potential issues:

                                                                        • if you host it yourself (not using Heroku), you must always keep the service up for as long as the application lives (i.e. is available through the App Store) to avoid new/reinstalling app users from experiencing crashes;
                                                                        • It assume Heroku sends a 404 if your application is not available (anymore), not sure if this will always be the case, but maybe this is documented;
                                                                        • The app will keeping making the requests every time when a 404 is returned to retry?
                                                                        • What if someone (over time) takes over your exact URL and starts sending other HTTP responses?
                                                                        • Heroku costs money, it adds up to quite a bill over time;

                                                                        It seems quite risky to implement this kind of “backdoor”, even if you take care, makes me wonder if this whole thing was a joke to begin with?

                                                                        1. 1

                                                                          Well the expectation is that any application using this would do so on a temporary basis. The linked Quora answer deals with a situation of the author making a mobile app on contract and not getting paid. Once the kill switch was thrown, they got paid, and delivered the source code, minus the kill switch. In that scenario, this is totally worthwhile.

                                                                          To use it long term for your own personal app, that would be another situation entirely. Which would probably mean that you’d need to host the responding web server yourself. Though, since it’s just HTTP codes, it’s very simple to configure any HTTP-speaking server.

                                                                          1. 1

                                                                            Heroku’s lowest tier is free. That ought to be good enough for the size of deployment this seems to be meant for, and considering that it just sends back status codes.