dice.camp is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon server for RPG folks to hang out and talk. Not owned by a billionaire.

Administered by:

Server stats:

1.7K
active users

#proprietary

2 posts2 participants0 posts today
Replied in thread

@dgar Love the variety of synonyms for "died" 😆

Lessons to be learned -
• Boycott #proprietary software - use #FreedomRespecting software (a.k.a. #Libre / #OpenSource / #FreeSoftware) which is free of corporate control, and
• Boycott #centralized services - use #federated services so you aren't locked into one service.

#XMPP is still around, and thriving.
contrapunctus.codeberg.page/th

contrapunctus.codeberg.pageThe Quick and Easy Guide to Jabber/XMPP
Replied in thread

@signalapp As a supporter of #Signal, it is important to point out a key detail: Signal's own code is #OpenSource, but Signal uses multiple #proprietary libraries from #Google. Those cannot be scrutinized since the source code is not open. We believe Signal should offer an actual open source version, and are ready to help. This exists already in the fork fosstodon.org/@MollyIM Also, apps like #Element #Threema #Wire are #FOSS, and have #ReproducibleBuilds on @fdroidorg #FDroid

FosstodonMolly (@mollyim@fosstodon.org)52 Posts, 30 Following, 1.57K Followers · Born from Signal, built for freedom. Molly is an independent Signal fork for Android, with a strong focus on security and hardening. #mollyim #signal #signalapp

This is a true story. I don't even know why I chose the proprietary drivers 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.

Replied in thread

@thelinuxexperiment 19:00 about that developers or publishers could just #opensource ancient games for the community, they dont usually tend to do that because of other #proprietary libraries, and stuff that they used to make the #game

Sure, they could just run through the source code - if it even still exists - and remove not theirs stuff, but that would require knowledge of all not theirs proprietary elements, or ability to start their old developement environments or other game engines, that are the only sensible way of accessing scripts/logic stored in obscure binary formats.

But yes, they should at least try to check if the source code is still on theirs discs, ask their lawyers if they can do that, and what has to be stripped, and maybe hire one intern to do all that work, to get hang of using computer, and tools they have used.

Replied in thread

@simendsjo @jackdaniel #XMPP has all those features, and there's a fairly big #Lisp / #Scheme / #CommonLisp channel there - xmpp.link/#lisp@conference.a3.

It might not have everything that #Discord does, but it's vastly better than #IRC. And there's a cost to using #proprietary and #centralized services, which people constantly forget about in chasing convenience and shiny features.

Here's a guide to help you get started.
contrapunctus.codeberg.page/th

xmpp.linkXMPP Invitation

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 #Forgejo.

"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.

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?