New changes to Twitter make it even worse for free software users


There are many complicated debates happening right now around Twitter and its role in public discourse. These discussions are important, but we also shouldn't forget a very basic and clear principle -- whatever its policies are about who can and can't post or how, it's of fundamental importance that Twitter should not require users to run nonfree software in order to use the site.
Unfortunately, on December 15th, Twitter removed its "legacy" Web interface. As opposed to its much larger and more complex default Web client, the legacy interface did not use proprietary JavaScript (or any JavaScript).
Previously, the Free Software Foundation (FSF) could tolerate the use of Twitter because of this legacy interface. While it was active, we referred free software advocates to it, or to third-party free software applications. Twitter's removing access to this interface means that users are forced to use the site's nonfree JavaScript if they don't have a dedicated desktop or mobile client, preventing freedom-respecting browsers like GNU IceCat from posting to the service.
But why use Twitter in the first place, if we know that it has these issues? As any charity can attest, engaging users on social media is one of the chief ways of getting their message across. The same is true for software freedom. We need to be talking about free software in places where everyone is not already a committed free software supporter -- we won't be successful if we are only in our own echo chamber, or preaching to the choir. It's important for us as activists to be reaching the people on these platforms, even if we have some reservations about using them ourselves. Twitter has its share of issues, but until we're able to drive enough users to the software freedom movement to where we can rely solely on word of mouth, we need to include them in our messaging strategy. We are, however, careful to make sure that you don't have to follow the FSF on Twitter in order to receive news or updates. Everything we publish is also posted on platforms based on free software principles, including Mastodon and GNU social.
-
- Login or register to post comments
Printer-friendly version
- 1871 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
KDE Frameworks 5.81 Released with KHamburgerMenu, Various Improvements
The biggest new feature in the KDE Frameworks 5.81 release is the implementation of a new, custom hamburger menu called KHamburgerMenu, which will be shown on QWidgets-based apps whenever the main menubar is hidden.
The KDE Project plans to adopt the KHamburgerMenu for all KDE apps as it offers several advantages, including an alternative app menu in case you hide the default menubar by accident, more freedom when you want to take full advantage of the maximum vertical space, more compact design with only relevant menu items, as well as support for relocating, renaming, removing, or even changing its icon.
| today's leftovers
|
Devices/Embedded Hardware
| Programming Leftovers
|
the EvilNess of JavaScript (DON’T BE EVIL TWITTER) strikes …
the EvilNess of JavaScript (DON’T BE EVIL TWITTER) strikes … again!