a client made by an enterprise who will willingly backdoor your messages
a client made by 3 people that get random breaking changes that completely obliterate flow
a client that is one giant html5 canvas that uses 100% of your browser gpu power
a client that requires systemd
way too many abandoned android and ios clients
please use fedi we have:
an instance software which is so popular but so feature deprived it makes no sense why it exists, also it's trademarked in a bad way
an instance software that has so much code rot it spawned 500 forks to try and fix it only to become rotten themselves
an instance software that doesn't really know what it's doing and instead implemented 3 different api standards, and this is the fork i'm talking about. no one should talk about the upstream project.
@kkarhan@ada It's funny how every time I see any toot about chat software or encryption of messages I can be sure you already posted your almost missionary XMPP+OMEMO reply to it. :breadpeek:
@kkarhan@Natanox@ada Some caveats at the fuel part that some policies are very much being used to tilt things their way (isn't regulatory capture & mass infrastructure destruction followed by motivated car-dependent development great⸮).
The rest about healthy ecosystem & open standards is right though.
@lispi314@Natanox@ada OFC, creating car-dependency by being allowed to destroy public transport is an utter failure of regulation.
This should not have been allwed in the first place!!!
But we've to all agree that switching from combustion to battery isn't going to save the planet, but reducing traffic and using economies of scale aka. public transport is.
@lispi314@Natanox@ada For example: A bus may require 40l/100km of Diesel duing stop and go service and while that seems inefficient, one can sit 30+ passengers in one without much effort...
Compared to the most efficient "serial production" car (VW XL1) which has a nominal consumption of 1l/100km, it barely fits 1 passenger besides the driver and only gets that mileage in optimal tests (i.e. Hypermiling it on a german highway with basically no deceleration/acceleration)...
@lispi314@Natanox@ada OFC running like a big beny-bus that can sit 50+ doesn't make sense beyond high-density areas and rush hours, but even if we go with like a BEV minibus that has maybe a dozen seats that's still more resource efficient that the 4+ Super Useless Vehicles they replace...
But that means #EcoHipsters can't "#ConsumeHappy" themselves beyond buying a ticket like everyone else.
This line really frustrates me. No, switching from petrol-powered cars won't "save us." However, it will help. Fewer petrol-powered cars means less need for petrol at the pump, which means fewer petroleum-powered cargo ships moving that petrol around. The greater the proportion of EVs on the road, the greater the impact of shifting electricity production from fossil fuels to renewables.
We also need to shift towards mass public transport.
These things work together. They're not mutually exclusive.
Tho I'm.shure "custom emojis" are a thing directly supported, tho I'm shure it could be suggested to them as option.
Granted, I unlike archival and export options and being able to sent files, that's more of a "nice to have" and not a non-negotiable requirement because missing :blobcat: and :blobfox: is hard it's not gonna get one into hot water due to mandatory requirements for legal reasons.
@kkarhan@ada Blaze: Yeah, it's only really non-negotiable for our use case because we want to make the transition as seemless as possible when Discord kicks the bucket
@kkarhan@ada Blaze: Guess we can play around with the API and making a Discord-bridged workspace though. We'd like to be able to port the Discord bots we use over as well, fortunately we've mostly picked open source bots.
And since their #API is open, you can self- and managed-host and even write your own #client that should allow you to have more options and controls than you could ever have on #Discord...
Add comment