OK, if anyone sees anything from this person: Ra (Freyja) (it/its)𒀭𒈹𒍠𒊩 (@[email protected]) regarding #ThriveMessenger he is just trying to find excuses to discredit me and my fellow devs work. He is just a guy that thinks that he knows it all and thinks that we should go overboard with our local dev environment, AKA our own computers that we are git pulling and doing the coding on, not just the server the application is hosted on. Like dude, no one goes out their way to do TLS shit on their home computers.
@alexchapman Uh... This is most definitely wrong. Lmfao. Yes, people do TLS on their dev computers. It's called having a dev certificate. It's self-signed, yo ushould perhaps learn about what your talking about before you criticise it.
@draeand But I don't open ports like a lot of others do, and this freya person was acting like not doing that is the worst thing, like literally, if I had ports open then yeah, but when editing code locally and then git pushing its not needed.
@alexchapman So what? TLS is always something you should be testing locally. Especially if your using a protocol which makes TLS a requirement. I know at least one protocol that requires TLS as a part of the protocol, it isn't an optional thing you can turn off
@draeand Yeah, when you're running shit on a server, but if you're just running tests before pushing changes to the VPS and stuff then yeah, this guy was basically trying to discredit me all because my windows machine, which doesn't have ports open, doesn't host any shit that is supposed to be on a VPS or other machine, doesn't have the SSL shit set up. I'm not the only one that doesn't go that far, a lot of people don't bother, because its not a requirement to write code and run tests.
@alexchapman @draeand I don't have SSL on my dev server. I have SSL because it's hooked under a cloud flare tunnel, but I don't have SSL itself on my local computer
@adisonverlice @alexchapman Maybe not but if your developign something over QUIC for example you have no choice as to whether TLS is used or not.
@draeand @alexchapman I don't even think Alex knows what quick is lololol
@adisonverlice @draeand Quick is how fast something is lmfao
@alexchapman @adisonverlice It's QUIC not quick lol
@draeand @alexchapman yeah, he doesn't now what quic is, why does he need to worry about it?
@adisonverlice @alexchapman I didn't say he had to worry about QUIC, I was pointing out that it is at least one protocol that has mandatory TLS, and it wouldn't surprise me if there were many others
@draeand @adisonverlice Right, well that's why for something like that instead of messing around with certs on the local machine I'd just have a test version on the VPS but not to where anyone can log in and do shit.
@alexchapman @adisonverlice And as I said, that introduces an entire new set of issues. A dev cert literally takes 5 minutes to set up and it's a one-time thing
@draeand I think it's based on http/https and activitypub, nevermind its based on python
@adisonverlice QUIC? If you mean that it's UDP based. Idk what the actual protocol for Thrive is
@draeand @adisonverlice Its not even a proper protocol, its literally whatever the fuck MSN/WLM used to do.
@alexchapman @adisonverlice And why are you mimicking what they do protocol wise? Why not just use your own and emulate their user-facing behavior?
@draeand @adisonverlice I wasn't the one who initially made the thing, Seedy did. And that's why once all the interface jank is sorted along with certain random disconnects and glitches that people have reported, then its gonna be a case of sort out a proper protocol.