1. 3

    I run a SYS Dedicated Server with Proxmox as a VM Host. I recommend PM if you wanna get into virtualized hosting, it’s rather neat.

    • Shaarli (Bookmarks)
    • Rainloop (IMAP/SMTP Client, though I’m switching it off)
    • Nextcloud
    • Airsonic (Music Streaming)
    • Cachet (Status Page, on shared hosting)
    • Invoice Ninja (forsSide-business stuff)
    • TinyTinyRSS (though looking for replacements, Feedly hasn’t been very pleasant, I have about 600 feeds on there)
    • Postal (Internal Mail Infrastruture)
    • YouRLS (URL Shortener, even got a neat Domain for it)
    • Gitea (for my private projects or before I publish it to github)
    • Skeletor (Selfwritten Analytics tool, currently not used)
    • PFSense (VPN, DNS and Firewall)
    1. 5

      try selfoss for a RSS aggregator/reader. IMO the best user experience among self-hsoted tools in this regard

      1. 2

        Thanks, I’ll try and see if it can handle my workloads <3

      2. 3

        I was using Proxmox before but I found it easier and more efficient to use docker as there isn’t reserved memory for each container like you have with a VM.

        1. 2

          Hm, yeah, but I have lots of Containers in Proxmox too (LXC) which also works better for IPv6 connectivity. I need the VM mostly for PFSense, which is BSD and doesn’t run too well in a container (it doesn’t run at all).

          PM also has a lot more functions that I like than Docker, especially towards failover with data persistence.

        2. 2

          RSS reader written in Python (and not PHP): newspipe. I haven’t test it out yet but it looks solid.

          1. 1

            I’ve experimented a bit. While it looks rather nice, the category functionality is probably not quite sufficient. I rely heavily on a hierarchy of categories to sort out my feeds…

        1. 9

          Android Oreo superpowers, coming to a device near you

          Yeah right…

          7.0 Nougat runs on 12.3% devices.

          7.1 Nougat runs on 1.2% devices.

          I have 4-5 androids at home, none of them even run Nougat (yay, Google f***ed up update scheme with vendors and carriers). So no, I don’t expect a single one near me.

          1. 4

            I, on the other hand, have had my device reliably and quickly updated since I bought it running Android 5.0, and will get Oreo. YMMV.

            1. 1

              What device do you have?

              1. 2

                Nexus 5X.

          1. 4

            I guess I’m confused. The promise here is that you won’t need to deal with merge conflicts if you use a VCS based on patch theory. However, almost the first thing the author does in this article is resolve merge conflicts. To me, it doesn’t really matter much that internally it’s not really a merge conflict but one of these digle things. From a UX perspective, I don’t really see the difference. Can anyone help me out?

            1. 3

              Check these out:

              The video is about yet another VCS called Camp, but it applies to Darcs and Pijul.

              1. 2

                This is all internal to the VCS, the user still needs to produce a text file with a strictly linear ordering that is valid.

                This simplifies the design of the VCS as there is no point where the user must be asked to create a “valid” state of the repo to represent, the digles mean the VCS never needs to ask the user to “resolve” the state of the repo.

                It doesn’t do much, if anything, to the day-to-day use of the VCS for the user, as most merge conflicts occur not because the state of the file is unrepresentable, but because the users made changes that are logically incompatible with each other.

                1. 1

                  the state of the file is unrepresentable,

                  When do conflicts like that happen in other VCS? Can you give an example?

                  1. 1

                    Take this snippet as an example:

                    int foo(int arg1, char arg2);

                    Charly and Lana fetch the code on their computer. Lana renames “foo” to “bar”, and push her code on the server.

                    In the meantime, Charly, during his trip to italy, renames it to “baz” and commit the change locally in the plane. He then arrives to the hotel, get a network acces the pull the changes. He gets a merge conflict because this funxtion cannot be named “bar” and “baz” at the same time. As both changes affect the same line, the file cannot be represented entirely.

                    1. 3

                      Is what you describe not the case where users made changes that are logically incompatible with each other?

              1. 15

                I would also find this useful, and it’s a tag I would follow. I’d prefer formalmethods to verification or correctness, because I think the former is a bit broader (though some people do admittedly use it in a more narrow sense). The latter two imply very “applied” work to me, while I’d personally like somewhere to sneak in formal work that isn’t directly applied to verification, like logic programming, automata theory, logical semantics, etc.

                These are a few articles I’ve submitted under the generic compsci tag that I think would fit at least a broad interpretation: 1, 2, 3, 4, 5.

                1. 4

                  it’s a tag I would follow

                  As a relatively new user, I may not understand the use of tags completely. It seems the default behavior is following all tags and the primary use is to filter by tag. Thus, the choice of tags should be primarily driven by the need of a few users, who want to hide a complete class of articles.

                  1. 2

                    There are per-tag RSS feeds

                    1. 3

                      In addition to that, I use them manually to catch up on a handful of subjects I find interesting, by clicking on the tag, e.g. /t/lisp. Sometimes I read lobste.rs often enough that I see almost everything that gets posted in every category (except a few I filter). But other times I’m away for a few days, and the tags are a useful way of checking if I missed anything good in the areas I care most about.

                1. 3

                  Grmbl. It’s not an actual product yet.

                  The best actual product I have seen is the USD 1100 SONY’s DPTS1 on which I think GoodEreader.com’s own kick-started product is also based.

                  1. 1

                    Have you seen Onyx BOOX Max?

                    1. 1

                      One thing I’ve always loved about Sony e-ink products is that they are super easy to use with just about any OS, software, whathaveyou. There is no huge cloud connected account that only works with certain formats, it’s a microsd card you can copy PDFs to.

                      I’m very tempted by this posting, wish I could actually get my hands on it for a reasonable price.

                      1. 1

                        It looks like the DPTS1 was discontinued in January :(

                      1. 16

                        Thank you a ton for this, whoever is behind it. It could probably use a description of how much of what Docker offers, could be achieved with LXC alone, but in a more orthogonal way — i.e. integrating better with the existing ecosystem.

                        1. 7

                          I’ve seen projects that only provide a Docker image as a means of deployment, which IMHO is fairly awful.

                          1. 4

                            That’s really bad. It’s not unique to Docker, though—at work we have an application running in AWS which is “deployed” by cloning an already-running instance. Whoever set it up the first time neglected to document what they did. (To be fair, I guess we’re the only people suffering from our poor deployment management in this case.) Virtualization and containerization are not fixes for the sins of the past, just ways of packaging them up nicely so you can pretend they don’t exist.

                        1. 14

                          I don’t find this article to be particularly convincing, but I’m also just so, so, so sick of arguing about REST. So I think I’m just gonna leave it at that.

                          1. 10

                            BTW, I highly recommend Steve’s Nobody understands REST or HTTP post back from 2011. Especially to the author of this article.

                            1. 3

                              Thanks. I’m hoping to finish up DHAs soon, I just got really, really burned out on this topic.

                          1. 1

                            One of my favourites. I haven’t checked how much it differs, but there’s also another version: https://www.cs.cornell.edu/fbs/publications/SMSurvey.pdf