Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)FA
Posts
0
Comments
72
Joined
2 yr. ago

  • So I tried adding SSL and I still couldn't get Voyager to work with a self hosted instance.

    If anybody has figured out how to get a self-hosted lemmy to work with an app I'd love to know how. For the moment I'm using NodeBB which is fine.

    I have Caddy and Lemmy running in containers on an Alpine Box, for which the hostname is "john", it is configured to have a static IP at the router 192.168.1.200. Caddy is set to network_mode: "host".

    Here were my steps:

    1. Install bind-utils for dig/nslookup for debugging
    2. On the server install dnsmasq and add address=/john/192.168.1.200
    3. Add the tls internal directive to the caddyfile:
       
          
      http://lemmy.john {
          reverse_proxy :1236
          }
       https://lemmys.john {
          tls internal
          reverse_proxy :1236
           }
      
        
    4. Restart the container
    5. Set the DNS in the WireGuard config on iOS
    6. Use a http server to make the .crt files accessible on the iOS device python3 -m http.server
    7. Install the intermediate profile on the ios device (I installed root, intermediate and lemmys just to be sure)
    8. Open https://lemmys.john in Safari and ensure it loads normally, as a typical site would.
    9. Copy the URL to the Voyager App login

    When I try to open it from the account it says "Problem connecting to lemmys.john. Please try again”. It definitely loads fine in Safari, so there must be something particular to the app that I’m missing.

    Edit: unless this is an issue with the nginx reverse proxy inside the container 🤔

  • Translation is very different from generation.

    As a matter of fact, even AI generation has different grades of quality.

    SEO garbage is certainly not the same as an article with AI generated components and very different from a translated article.

  • Further TL;DR

    In preparation for an IPO:

    Reddit: you must now only use our app to prop up our add revenue. No third party apps (unless you pay us handsomely)

    Everyone: no thanks, just make our own alternative

  • Well, no, neither approach is better than the other, it’s apples and oranges.

    There will always be a place for installing native applications. In the least analysis, the container itself should probably have some dependencies packaged for the target program.

    The benefits of containerisation are obvious, but it’s been a lot of work and there are still edge cases to iron out.

    FreeBSD has had jails since 2000. Linux, however, only got namespaces in 2008 and the first bubblewrap release on GitHub was 2016.

    I’ve been using chroots and containers for development for about 2 years now and it’s been fantastic, however, I’m still grateful I don’t have to jump inside one every time I need to write a python script.

  • Snap is a sandboxed environment to install applications in.

    Flatpak is a more portable implementation of the same broad idea, it downloads a chroot and runs applications from within using a separate program called bubblewrap (one could, in theory, use chroot to run apps from within the downloaded flatpak images, bubblewrap offers further isolation through things like namespaces and cgroups etc. )

    Snap, unlike flatpak, is a Canonical specific implementation that has a reputation for breaking a lot of things.

  • Yes it’s easy, install WireGuard in a container, port forward to it and copy the profile to your other devices.

    When you connect to the WireGuard network on the second device, you’ll have access to your internal network and hence your nas.

    I also use a reverse proxy so I can remember computer names rather than ip.

  • PL can have a large impact on features, bugs, bug reports, troubleshooting, performance and documentation. Particularly when dev resources are limited.

    It’s hard to see how this opinion holds any water.

    Rust is a great choice for a shell built as an interactive shell that doesn’t have to be core to the OS. Over C++ this also makes development more accessible to young programmers.

  • I absolutely love void. Second to that I would say endeavour, it’s just arch with zfs, a wm and an installer.

    If you’re interested in learning more try , I use oddlama’s installer. With binary packages, distrobox and flatpak, the small amount of compile time is a much smaller issue.

    Alternatively, if you’re thinking about Fedora maybe play with Silverblue, it forces you to learn a bit of containerisation which is handy

  • From the first result on Google:

    The Wayland Display Server project was started by Red Hat developer Kristian Høgsberg in 2008

    So yeah, I suspect Red Hat does in some way contribute to development. As I’m sure does Microsoft, Canonical etc.

    None of this happens in a vacuum.