Rather than disabling FTP, they should put it behind the same user made exception that HTTP needs now. This way, the legacy support can remain there with plenty scare for the average user.
But then this is the same Firefox run by a bunch of PR and HR hijackers that cut off the Servo team and other developers and silence users regularly on the bug tickets and on r/firefox (I got handed a 6 month ban for Cloudflare DNS criticism by nextbern).
The team is not just a “browser team”. These decisions are taken by CEO Baker and crew, who want to play virtue signalling politics and creating extensions like b!tch-to-boss (yes there is ! instead of I in the name) instead of focusing on development and valuable projects like Servo.
Rather than disabling FTP, they should put it behind the same user made exception that HTTP needs now. This way, the legacy support can remain there with plenty scare for the average user.
But then this is the same Firefox run by a bunch of PR and HR hijackers that cut off the Servo team and other developers and silence users regularly on the bug tickets and on r/firefox (I got handed a 6 month ban for Cloudflare DNS criticism by nextbern).
That seems a sensible choice, too bad they opted to deprecate it entirely…
If I may ask, how does the browser team “cut off” other teams?
Curious as I don’t know about any of this. 😅
The team is not just a “browser team”. These decisions are taken by CEO Baker and crew, who want to play virtue signalling politics and creating extensions like b!tch-to-boss (yes there is ! instead of I in the name) instead of focusing on development and valuable projects like Servo.