a beautiful robot, dancing alone · showgirls über alles: kylie, angèle · masto · last.fm · listenbrainz · lovekylie

  • 4 Posts
  • 40 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle
  • Prerequisites

    • Internet-facing web server with reverse proxy and domain name (preferably SSL of course)
    • Server behind the reverse proxy with Rust environment

    Installation

    • Don’t bother downloading the source code to your server; installing it that way gives you a big debug executable
    • Instead just cargo install mollysocket
    • Move the mollysocket executable if desired
    • Run mollysocket once so that it will emit the default config

    Configuration

    • Fish the config file out of .config/mollysocket/default-config.toml and copy it somewhere.

    config.toml

    • In the new file, replace the allowed_endpoints line with allowed_endpoints = ['*']. The default 0.0.0.0 config appears to be a bug; this setting controls access to endpoints within the app, not IPs from outside. Leaving the original value causes mollysocket to reject everything.
    • Put a proper path in the db = './mollysocket.db' line rather than just having it land wherever you’re sitting.
    • Delete the mollysocket.db that was created on first run (even if it’s already where you’re intending to put it). This is just to make sure the web server creates it and has the correct permissions.

    Run script

    • The environment variable ROCKET_PORT must be set or the server will sit and do nothing. It’s best to create all of the environment variables mentioned in the README, whether that is in a user profile script or in a shell script that wraps startup. You can change any of these values, but they must exist.
    • export ROCKET_PORT=8020
      export RUST_LOG=info
      export MOLLY_CONF=/path/to/your/config.toml
      

    Proxy server

    • You’ll need to proxy everything from / to your mollysocket server and ROCKET_PORT.
    • Exclude anything that you may need served from your web server, such as .well-known.

    Things to know


















  • i agree, but my unpopular opinion is that mozilla has also proven this repeatedly, with nothing and nobody being universally better. privacy people love firefox, but i spend a lot of time with each major version’s release notes figuring out how to undo the new telemetry (increasing integration with pocket, firefox suggest, location that won’t turn off).

    my threat model is ‘they’re all evil, including mozilla’, so there are additional rings around everything





  • appimages just got less easy…

    i don’t know which update did it - i think it must have been os-level (i run pop_os, derived from ubuntu) - but appimages silently stopped working. double-click, nothing. finally i looked in the log out of desparation, which said ‘appimages require fuse’.

    more accurately, appimages require fuse 2 and the os had just upgraded to fuse 3. the fix is to heat-seek libfuse2, and don’t mess with any other fuse-related package as things can start wrecking themselves:

    sudo apt install libfuse2

    originally seen on an omgubuntu post


  • i believe one can’t stop collection, only aggregation, so use different platforms and different emails - and critically, a device that actually meets your needs - and hope for the best. i have a garmin with an email on a domain i own. my phone is android, using a google profile that’s empty of any voluntary info and tied to a gmail address used for nothing else.

    it’s child’s play to aggregate this, but otoh, two companies will work to combine the data only if they have a common goal.