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

  • 2 Posts
  • 19 Comments
Joined 2 years 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














  • is that somewhat new?

    it’s somewhat… janky.

    you can ‘migrate’ an account, to use the masto term that will make it easier to search. this:

    • makes it so your old account can’t post
    • puts a ‘pointer’ on that account so that you get its mentions (i think)
    • puts a note on that profile that you’re really you-at-new-place now
    • causes all accounts following you to auto-follow the new place

    it does not:

    • remove you-at-old-place from other people’s follower·ing lists; old you eventually shows as dormant, but you’re still in their lists until and unless they clean house
    • take any posts with you; you-at-new-place starts with an empty profile
    • copy over any profile information
    • copy over any post filters

    i’m not clear on how long your old posts linger at old-place, and you might have to export/import your following list.

    it’s possible, i’ve seen lots of people do it, but it gets more unappealing the longer you’ve been actively using the account. unless you’re like me and have posts set to self-destruct within days. and you can imagine the difficulty of actually moving the posts - if i were an avid shitposter and i moved house to noshit·social, then all my garbage would be dumped in the yard in violation of policy.



  • i have both and i parallel scrobble to both using pano scrobbler (phone) and strawberry player (desktop). you can sync your scrobble history from last.fm into listenbrainz, either one-time or on a continuing basis (though the latter seems to run the risk of duplicates). i chose to do it once and then feed them in parallel going forward.

    as a discovery tool, listenbrainz is a bit anemic, except for once a year, and last.fm has declined for me over time.

    first the good

    listenbrainz does a year-in-music that shows your listening patterns and also top things you might have missed - my 2022 year in music is here. i scooped up a lot of stuff from that list.

    now the bad

    listenbrainz’s recommendation engine is only so-so, not terrible, not brilliant.

    many commercial streamers and scrobblers only understand last.fm, so if you stream a lot you may not be able to keep listenbrainz updated except through manual syncing.

    last.fm’s recommendation engine has declined over time for me and its community is stagnant, so i don’t see a lot of neighbour activity. it remains better than listenbrainz week by week, but only marginally.

    oss stats

    i remix and embed stats from the listenbrainz api on my own websites (profile link). doing this from last.fm requires an existing api key (which it seems they’re no longer issuing), and of course they can rug-pull that api at any time, not like we’ve seen that lately. but listenbrainz stats recalculate only daily.

    caveat

    my experience of these is different to most people’s, as data geeks don’t tend to listen to the candyfloss music that i do.

    pootriarch@lastfm · listenbrainz · popheads community


  • mastodon struggled with scaling in the beginning, everytime elon strung more than four syllables together. a lot of admins there didn’t know what the spikes would do - this is not a criticism, i would have had no idea either - and most new users piled into one or two big instances, as is happening here.

    the more tech-savvy of the initial waves migrated to smaller instances, the instance admins figured out where the pain points were, and i think there were changes to mastodon itself. i expect all of these are coming for lemmy, and it’s going to be lumpy here for a while just as it was in masto.

    having lived through that, i came into a smaller instance here immediately. federation issues here are a bit gnarlier than on masto, but i trust that also will be sorted.