trash
fedilink
11
trash
fedilink
@TheGreatestLemmyUser@lemmy.world
creator
link
fedilink
2•6M
  1. Using Crates.io:

cargo install mollysocket

ends up with

error[E0658]: c"…" literals are experimental … error: could not compile rusqlite (lib) due to previous error.

Now rustc --explain E0658 states that this is due to unstable feature “repr128”. I’m using a nightly version.

  1. Using precompiled release:

After systemctl enable --now mollysocket

performing systemctl status mollysocket gives

… Active: failed (Result: exit-code) … Process: … (code=exited, status=203/EXEC) …

  1. Docker:

sudo -u mollysocket mollysocket vapid gen | systemd-creds encrypt --name=ms_vapid -p - -

or basically any command starting mollysocket ends up with

mollysocket:command not found error.

Autonomous User
link
fedilink
1•
edit-2
6M
  1. Check their issue tracker for build issues.

github.com/mollyim/mollysocket/issues

@TheGreatestLemmyUser@lemmy.world
creator
link
fedilink
2•
edit-2
6M

I guess I managed to break too many things while testing several settings…so I did a fresh Linux Mint installation and decided to try Crates option again almost succeeding…

Now I managed to perform cargo install mollysocket as well as create vapid key (though only as a plaintext…) and add that to corresponding file. I set up Mollysocket to be used in air-gapped mode (webserver = false), then performing systemctl restart mollysocket, and now based on systemctl status mollysocket the process is now active. I also got the QR code via journalctl -u mollysocket, but now the status on the Molly app says it’s “Unable to create the linked device”.

That’s where I’m stuck now. Seems to be so close to work…

@TheGreatestLemmyUser@lemmy.world
creator
link
fedilink
2•6M

Yeah, someone just made a post about that recently. This solved the issue, and now I’ve my Mollysocket server running! Many thanks to you for assisting.

Autonomous User
link
fedilink
1•
edit-2
6M
  1. sudo journalctl -xe -u mollysocket # to see full log
Autonomous User
link
fedilink
2•
edit-2
6M
  1. mollysocket command is inside the docker container(s), so outside you get not found.

github.com/mollyim/mollysocket/blob/main/README.md

VAPID key

VAPID key is used to authorize mollysocket server to send requests to your push server, if it supports it.

To generate a new key, you can run this command mollysocket vapid gen. Or using docker, docker compose run mollysocket vapid gen.

This value can be passed to mollysocket via a file, location given with vapid_key_file parameter, or directly in the vapid_privkey parameter. The key file takes the precedence.

docker compose run mollysocket vapid gen

Create a post

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

  • Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
  • Don’t promote proprietary software
  • Try to keep things on topic
  • If you have a question, please try searching for previous discussions, maybe it has already been answered
  • Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
  • Be nice :)

Related communities

much thanks to @gary_host_laptop for the logo design :)

  • 6 users online
  • 124 users / day
  • 1.05K users / week
  • 1.3K users / month
  • 4.58K users / 6 months
  • 1 subscriber
  • 3.89K Posts
  • 98.1K Comments
  • Modlog