Andres

@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.

@jerrimu @jagged_circle lol!

I read this as a very diplomatic way of saying, “Why… would you do that? Don’t do that.” 😏

@puppycat @JuryNow These days I *always* do the audio (accessibility for vision-impaired folks) captcha, because 1) fuck training self-driving cars, and 2) captchas have gotten harder and harder over time and it often takes me several attempts despite my vision being just fine.

@claralistensprechen5th @rejinl @ECEC She said ‘street trees’, which are have shown clear benefits to dense cities all over the world. They’re incompatible with on-street parking, though.

@claralistensprechen5th @ECEC *sigh*

City streets are _not_ specifically for cars. Freeways aren’t even specifically for cars (buses, trucks), but city streets in particular are definitely not just for cars.

Tree roots are a solved problem. Lots of city master plans and similar documents have a list of trees allowed in the public right-of-way that have root systems compatible with sidewalks and roads. Some trees have roots that buckle concrete, others have roots that don’t. Choose wisely.

@ECEC Good lord the number of replies here from people whose brains have been destroyed by “planners”…

1. Trees lower the urban heat island effect.
2. There’s plenty of room for trees in dense places, so long as “density” means efficient housing and efficient transportation rather than parking lots and stroads and single-family homes.
3. Someone said “trees require maintenance”, as if asphalt & pretty much everything doesn’t require maintenance?
4. Trees harm cars. But cars harm cars too!

@claralistensprechen5th @ECEC Sounds like the problem is cars, not trees.

#FuckCars

@sugar_in_your_tea @phoenixz Hi there! If you wouldn’t mind indulging grampa for a minute - I’m a former php4 maintainer for Debian with a story.

One time we found a bug that caused the php interpreter to crash, based on the input passed to a function. We decided it was a security issue, but even that was kind of besides the point. We reported it upstream to the php folks. They (Rasmus!) told us it was not a high priority issue, because apache would simply restart when it crashes - no big deal

@leodavinci @poVoq @sxan I can’t speak to iOS, but at least on android that’s not a problem as long as you grant it the proper permissions.

@poVoq @sxan Also, I used to maintain a matrix client in Debian, as well as self-hosting synapse. I went back to XMPP.

@poVoq @sxan I have a 200MB/mo data connection, and my XMPP client (Cheogram) is barely a blip. The main driver of data usage with it is when my family is sending around 0.5MB images to each other.

@mac @poVoq Just curious what you dislike about Cheogram’s UX?

@ItJustDonn @486 Hang on, this runs chromium as root? That seems like a _really_ bad idea. And unnecessary, since there’s a hoarder user installed later in the script…

https://github.com/karakeep-app/karakeep/blob/main/hoarder-linux.sh

@Coldmoon @Steamymoomilk I mean, a few months ago I bought a 10TB used HGST drive from 2018 (from goharddrive). The bigger issue imo is buying a drive that old and having only a 90 day warranty. The 10TB drive I purchased came with a 5yr warranty.

@Smash @Limonene Right, it *was* proprietary. Which is why adoption of it by free software devs is so slow. Ubuntu only got dotnet packages in the past few years! (RIP @vorlon )

@sxan @shortrounddev jmp.chat uses XMPP, and it’s a very viable replacement for Google Voice (and generic SIP options like voip.ms), so that’s what got me back on the XMPP train. No one else other than my family is using it with me, though, but it’s still nice to have SMS, (encrypted & decentralized) family chat, and IRC (via biboumi bridge) in one desktop client.

@WhyJiffie @kratoz29

> is there such a problem? honest question. But I think that might be a different issue

Yes, that is a problem. We’re still in a world where you need to manually enable port forwarding in order to get better seeding for bittorrent clients, and if you have CGNAT you’re SOL (short of using a VPN or something to bounce through an external host).

It’s likely because torrent software is older (& in crappier languages), and came about before CGNAT was a thing.