Andres

@MimicJar @moseschrute *touches finger to earpiece*

…hang on, I’m getting word that the most recent edition of this book will crash your nvram’s firmware

@Dust0741 Check out jmp.chat (i can provide a referral code if you’d like a free trial). Your number would be ported there, and then SMS would go over XMPP/jabber to any device with a client running. Your phone can stay home, and you’d get SMS messages on your laptop or whatever device you’ve taken with you.

@iii @KarnaSubarna Looks like syncthing-fork already updated to 2.0: https://github.com/Catfriend1/syncthing-android/releases

It’s not in f-droid yet, though.

@Passerby6497 np! Any usb-powered PC fan will do, btw. I also have some Arctic fans that I like even better, but for the minipc I’m using an AC Infinity because that’s what I had handy.

@Passerby6497 @curbstickle I have a Minisforum hm90 that tried to cook the nvme (it triggered a smart error before actually frying, thankfully). Since the m2 slot is on the bottom near some vents, I just put the minipc on top of an AC Infinity usb fan (I forget if P12 or P14 - use whatever fits your minipc best) that blows up into the case and over the nvme.

@a @selfhosted @selfhostedchat Unfortunately no, as we don’t have any apple devices in the house.

@a @selfhosted @selfhostedchat Prosody (xmpp). The kids use Dino on their linux laptops, and Conversations on their android phones. The biggest problem we have is that the kids want to invite non-family members into the family chat, and I’m just not set up for that.

@tripflag @disobey2623 Your statement is correct; the way seafile stores files is in blocks (for de-duplication, apparently).

They offer a fuse extension that allows you to view stuff like a normal filesystem, though I’ve never tried it: https://manual.seafile.com/latest/extension/fuse/

@ssdfsdf3488sd My understanding it that they’re both pretty much the same, so I wouldn’t unless snikket has stopped being maintained or something?

@2xsaiko XMPP is nice and lightweight, so I think either would work fine. I just find prosody has more community momentum.

It was matrix that was a massive memory hog, required running bleeding-edge homeserver software, didn’t do proper security support, etc, so that’s where I have stronger feelings.

@2xsaiko A big caveat is that I used them in very different time frames - prosody starting from 2021 to now, while ejabberd I used from 2006 to 2012 or so. At the time I used it, ejabberd’s config was done in erlang(!); they apparently they’ve since switched to yaml configs. It was generally fine, but when I switched back to XMPP in 2021, I figured I’d go with a server in a less niche language and better support (the jmp.chat folks mostly use & recommend snikket/prosody).

@poVoq @fmstrat I ran ejabberd for years before switching to matrix (synapse). Matrix was a disaster, plus jmp.chat is a fantastic google voice / VOIP replacement, so I switched back to xmpp (with prosody). Out of those options, prosody is clearly the best for self-hosting.

@BackYardIncendiary @ProdigalFrog If you have an old latitude, newer kernels also allow you to set min/max charging thresholds. My syncthing server (and NAS and a few other things) is an old 2013/2014 dell latitude e7240. It’s not the original battery, but I do keep it in decent shape via charging thresholds.

@irmadlad @lambalicious I just manually do the audio captcha. Every time. Because the picture captchas often don’t work correctly for me.

It does bug me a little that I don’t know what the audio captcha is being used for - am I helping an amazon echo transcribe whatever it is surreptitiously listening to?

@possiblylinux127 @Tattorack I still stand by this other major difference, though: https://social.ridetrans.it/@Andres4NY/114671239145822442

@possiblylinux127 @Tattorack See also this table: https://discuss.techlore.tech/t/comparison-chart-of-grapheneos-divestos-and-calyxos/5618

A bit outdated since Divest is gone (😢), but a core difference is that Graphene prefers proprietary google stuff that is sandboxed and not given any privileges, while Calyx prefers free software versions that might have other issues (eg incomplete, or unsigned coming from third-party sources).

@martinb @jerrimu I wrote the initial comment with the idea of saving just the username, but then figured “why not?” for the password. If the password is saved in browser memory (and based how I *think* the app functions, it would have to be), then it wouldn’t be much different than saving a password in firefox’s password manager (for example). Assuming reasonable crypto usage by the app, of course.

@jerrimu A usability suggestion, having just tried it out - save the username and room password in the export file to make it more like a traditional chat experience. So when you import the chat file, the username and password are pre-populated along with the room name.

@moonpiedumplings @jagged_circle
* I can’t speak on behalf of the author, but I could imagine handling it by simply not decrypting _everything_ on startup, and only decrypting an older chat if you click on it or attempt to run a search on everything. Although for a search, I would expect some kind of hashed (and of course encrypted) database that allows a quick search of all prior messages.

@moonpiedumplings @jagged_circle I read your initial question as 1,000 active chat *rooms* (with some large number of users for each), which… seems excessive. That’s what I was referring to.

1,000 individual private 1-on-1 chats (or group chats with 2-3 users), if that’s what you meant (and especially over a long period of time, with lots of inactive chats), seems like a more common scenario*. If that was your question, I apologize.