I have the Multiling keyboard. I don’t recommend it to others as it’s rather long in the tooth and still has quirks I haven’t fully sorted. I keep it precisely because it does multi-language support with separate dictionaries; I switch it between U.S. English and French Canadian and autocorrect follows. It’s massively customizable but I don’t understand it and am more likely to render it unusable than to make it better.

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 get this warning on startup: “Forced shutdown is disabled. Runtime settings may be suboptimal.”
• I also can’t stop my server with any sane signal; only SIGKILL brings it down.
• Some discussion here: https://github.com/SergioBenitez/Rocket/discussions/1880

deleted by creator

you probably already found this, but for others who might be curious:

https://molly.im/

https://github.com/mollyim/mollyim-android

in the settings if you change notification method from websocket to unified push, the UP settings come up, including a server address (which is what they intend to be used) or some air gap mode that i can’t find documented

well i feel stupid now for not doing the obvious. but…

Blocked Page

Your organization has blocked access to this page or website.

on the PPA box, this is what it showed me (meanwhile it was attempting to connect to incoming.telemetry.mozilla.org). another symptom of displaying respect for enterprise policies but in fact ignoring them. (as i had mentioned, on this box all of the settings look locked down as they should be, but it’s still attempting to send telemetry.)

thanks, i’ll look again. it’s not that i love the idea of being fingerprinted; i just think that five mylar bags, four tin hats and a partridge in a pear tree won’t save me from that. i need my password manager, and once that’s in, enforcing a generic screen is silly - cow’s out of the barn. but not having the arms race against pocket and telemetry would be a big bonus.

i did try that but the never-dark mode blinded me. i understand the reasoning, but absolute anonymity isn’t my own threat model; i’d like to be able to use themes and resize the window

an interesting oddity: on my non-rooted xperia, signal thinks that i don’t have play services and so it falls back to… polling. every five minutes. killing my battery and my logs.

i had to put signal into the restricted battery group, which means no notifications. i anxiously await the new molly, as i already have a unified push environment. it looks like the migration will be a bit delicate.

to a techie, i’d say, it’s open source and if they ever overpushed politics, they’d find they’d become the fork as the community would fork away.

to a non-techie, i’d say, everyone’s an asshole a different way, but they don’t own the whole place like spez and musk do.

and i wouldn’t argue. let them walk away haters. this platform isn’t ready for everyone to come right now anyway.

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’m new here. i never used reddit except if it was a search result for a specific, usually technical, question.

every thread i’ve looked at here has been like this one, intelligent, reasoned, no dunking except to look like a donut for effect.

the reddit experience described here… wow. that’s many years of boiling frog.

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.