Local timeline
SimpleX also has been having this default for a while now.
Signal made some headlines today by introducing a setting to prevent screenshots in the app. Conversations has had a setting for that since 2021.
(These days, you can find the setting under Settings / Interface / Operating System)
@Wintermute_BBS@oldbytes.space I see! So most went by "trust the SysOp, the SysOp can do no wrong"... Nobody was thinking about data breaches and leaks.
@sizeofvoid@bsd.network Cool! This is on X11 or Wayland?
Plasma Wayland was unstable for me on Alpine Linux, so I couldn't entertain the idea of going back to it on something even more distant from systemd Linux as OpenBSD.
@Wintermute_BBS@oldbytes.space Was it common for a BBS to ask for street address and other highly personal information when registering a new account? That happened to me with the first BBS from this site's directory that I tried.
Think I'll stick with the BBS on Gemini...
@mjack@bsd.cafe I don't even know for sure all that I've set in the wizard, all I know is that I can generate invite codes.
according to the configuration in the admin panel:
SMTP not configured
Open registration: disabled
Invite required: no
Approval required: no
OAuth scope enforcement: enabled
@evacide@hachyderm.io Galaxy brain logic: instead of funding boring ol' public education, they decided the best way to educate most everyone (see: turning Russian babushkas into masters of VPN obfuscation) about computers is forcing most everyone to learn all the means of dodging ID verification...
I am only half-joking, I bet some of these Big Tech masterminds regard this whole ID verification scheme as another way for them to filter humanity and narrow it down to the "fittest cyber minds" or some other Hunger Games scenario. If they really believe in this hyper competitive scenario, I think it's not too late for the outcome that people at a larger scale - and not just the most tech savvy - will actually cooperate to keep some networks alive and open and will do so whatever it takes.
Has anyone else running #littleFedi tried already to change an instance's setting from disabled registration to open for people with invite codes? The documentation suggestly the possibility to do this any time later, but there's no switch in the admin web console, nothing about it in the CLI tool, and forcefully adding "auth.registrations = true" to either the TOML config or an attached .env file doesn't produce any effect. What do you folks do? Tamper with the .db file? Re-start the wizard from scratch? I'd rather not put anyone through having to accept my friend request again just so I can have open registration, but I already rushed to give out a few invites.
Fun little bug: I decided to log into my #littleFedi from my 13-year-old tablet, where I'm running Privacy Browser. With JavaScript enabled (which I kept turned on because of Mastodon), the login page seems to hang. On the contrary, with JavaScript disabled, it just works! Now that's finally a bug that can be called a feature!
@justine@snac.smithies.me.uk This is funny. Might have something to do with me being on low-power preset. I'll restart the server later anyway.
Not on the first refresh, but on second refresh my instance managed to get this in the inbox.
Writing on here to test federation with my new #littleFedi instance, which already added this account and - wow! - fetched a bunch of posts from me, albeit without their quoted contexts, but still impressive.