flipboard.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to Flipboard on Mastodon. A place for our community of curators and enthusiasts to inform and inspire each other. If you'd like to join please request an invitation via the sign-up page.

Administered by:

Server stats:

1.2K
active users

#proprietary

2 posts2 participants0 posts today

This is a true story. I don't even know why I chose the proprietary drivers on this laptop, I don't game on this device or anything, nor does it even have a dGPU (which is generally the only reason to do so imho).

Luckily installing and setting up Linux is done quickly.

Just to be clear: If #Google decides it’s okay to no longer send non-Gmail users the ACTUAL #email, but only a LINK to some bullshit #proprietary service that you must click to “unlock” the TRUE contents, then Gmail ceases to be an email provider but is merely a spam service which bullies unsuspecting users into using their proprietary crap.

While this seems to be limited to (fake) E2E for now, I’m afraid it could get worse if people do not resist.

I know why I don’t use #Gmail.

Continued thread

Remember - the rest of the #OpenStreetMap #FreeSoftware ecosystem is still on #GitHub. The OSM website, the iD editor, @osmandapp, @vespucci_editor, @everydoor, @osmapp ...despite offers to help with the move.

I know the devs to be otherwise very friendly and supportive people, but on this issue we are at an impasse.

Why do they wait to be abused by #proprietary platforms when they could avoid the whole problem from the start?

On the train ride back from Patna (#BiharFOSS), @ravi and I sardonically thanked Trump for the state of things in the US, which may have been why #GitHub disabled the #OrganicMaps repo and forced them to move to #FreedomRespecting #Codeberg.

"This will hopefully teach people why it's important to boycott #proprietary platforms. But why do people always wait around for such things to pass? #FreeSoftware activists had been warning them for like 10 years!" (Also...Sourceforge???)

Replied in thread

@signalapp It's not #disinfo when one points out that you demand #PII aka. #PhoneNumbers from Users and that is literally a architectural vulnerability, alongside your #proprietary & #Centralized #Infrastructure.

Not to mention the lack of @torproject / #Tor support with an #OnionService or the willingness to fulfill #cyberfacist "Embargoes" or shilling a #Shitcoin #Scam named #MobileCoin!

  • #KYC is the illicit activity!!!

And don't get me started on the #cyberfacism that is #CloudAct.

  • If you were secure, criminals would've used your platform so hard, it would've been shutdown like #EncroChat and #SkyECC.

I may nit have allvthe.evidence yet, but #Signal stenches like #ANØM: #Honeypot-esque!

Replied in thread

@ueeu I think crucial parts is looking at it's components, dependencies, size and for apps permissions.

#ReproduceableBuilds for example are important, so the actually released source code is what people actually get served as basis.

Plus in terms of #security, choose *real #E2EE with #SelfCustody of all the #Keys!

Replied in thread

@fj I still think @signalapp has fundamental flaws like demanding #PII (#PhoneNumbers can't be obtained anonymously around the globe and are trivial to track down to devices and thus users), being subject to #CloudAct as an unnecessary & 100% avoidable risk as well as #Shitcoin-#Scam shilling (#MobileCoin) and it's #proprietary, #SingleVendor & #SingleProvider nature that makes it inferior to real #E2EE with #SelfCustody like #PGP/MIME & #XMPP+#OMEMO!

Replied in thread

Good luck @weblate ... While @nextcloud talks about FOSS and decentralization, people have been asking them for years about using #Peertube and #Weblate, but it's always crickets and continued exclusive use of #YouTube and #Transifex.

There's virtually never even a response why they exclusively use the closed, #centralized, #proprietary services.

I respect @Karlitschek and @jospoortvliet but the org seems only interested in #FOSS / #Privacy / #decentralization in their own code / marketing.

I believe Dan plans to never #federate , revoke federation, or at least retain the ability to do so. See term 2 on Loop's website: loops.video/legal/terms-of-ser
which says such things as "under this license you may not:...use the materials for any commercial purpose, or for any public display (commercial or non-commercial);.....transfer the materials to another person or "mirror" and the materials on any other server...This license shall automatically terminate if you violate any of these restrictions and may be terminated by Loops at any time." and "Loops may revise these terms of service for its website at any time without notice" Loops' terms are not open source and could be used to justify #defederation or changing policy on federation. And considering how dan behaves with peers who disagree with him, I could see him deciding federation isn't what he wants to do with Loops, which he treats not as an #opensource thing but as #proprietary
NO #FOSSWASHING

loops.videoLoops

Isn't it about time we start rallying against #proprietary #firmware already?

From every #EV and #car being a glorified #telemetry machine, to every chip out there basically harboring #SecretSauce with the "trust me bro" guarantee attached.

Neither #US interests, #Chinese interests or private interests should hold so much power. No one should.

All firmware; I repeat, ALL FIRMWARE should be #OpenFirmware. The firmware isn't open? #Ban the #product outright.

tarlogic.com/news/backdoor-esp

Tarlogic · Tarlogic detects a hidden feature in the mass-market ESP32 chip that could infect millions of IoT devicesBy Administrador
Replied in thread

@Lu with all due respect to #linuxmint #developers the #flagship variant should be based on #debian and for those who use #nvidia #gpus and need the #drivemanager ( #gui to install #proprietary #drivers ), could use the #ubuntu variant. LinuxMint as a #community #distro aligns with Debian and #flatpak #universal #linux #package #format compared with Ubuntu and its #snap package format. Also, Ubuntu as a commercial distro will eventually switch to an #ImmutableDisto with all snap packages.

Hmmm, advice please.

So; say you're a #opensource #vector image editor and a volunteer pops in to help write a new compatibility to some proprietary #fileformat.

Say the volunteer makes progress and one day a brand new account claiming to be the founder at the #proprietary company of said format offering the volunteer a job.

To me; this is clearly a way to foreclose work on compatibility. The #foss equiv of buying out a competitor.

But how should the project moderate this kind of message?