• @sugar_in_your_tea@sh.itjust.works
        link
        fedilink
        English
        011 months ago

        Update: Bitwarden posted to X this evening to reaffirm that it’s a “packaging bug” and that “Bitwarden remains committed to the open source licensing model.”

        I’m not going to jump ship just yet, though I may get around to updating my backup.

        There are plenty of alternatives, so feel free to shop around. But don’t jump the gun just because of a random Phoronix article with an update that says basically the opposite of what the article claims. Wait some time to see if there are actual changes coming.

          • @sugar_in_your_tea@sh.itjust.works
            link
            fedilink
            English
            011 months ago

            Maybe. Here’s what they say in the readme of the project people are complaining about:

            The password manager SDK is not intended for public use and is not supported by Bitwarden at this stage. It is solely intended to centralize the business logic and to provide a single source of truth for the internal applications. As the SDK evolves into a more stable and feature complete state we will re-evaluate the possibility of publishing stable bindings for the public. The password manager interface is unstable and will change without warning.

            There are two ways to take this:

            • this is temporary as they’re refactoring code to reduce duplication across clients
            • refactoring is an excuse to create fully proprietary clients going forward

            Until I see evidence of the latter, I’ll stick with the project, but I’ll be more consistent about creating backups so I can switch easily if I need to.

      • GHiLA
        link
        fedilink
        English
        011 months ago

        KeePassxc with syncthing

        Nextcloud with their password solutions

        A notebook

  • kingthrillgore
    link
    fedilink
    English
    011 months ago

    I’m going to keep using Bitwarden because KeepassXC sucks, but not as a paying user. Once this package inclusion is removed, if it is removed, i’ll pay again.

  • Magnus Åhall
    link
    fedilink
    English
    011 months ago

    Daniel García, owner of the Vaultwarden repo, has recently taken employment for Bitwarden.

    The plot thickens.

    • @sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      011 months ago

      Honestly, if he can replace the current Bitwarden BE w/ Vaultwarden, that would be awesome! The last time I looked at the Bitwarden self-hostable BE, it was super heavy, which is the entire reason I was interested in Vaultwarden.

      • Magnus Åhall
        link
        fedilink
        English
        011 months ago

        I’m running a couple of Vaultwarden instances, and it would be really nice if Bitwarden employed Garcia to improve the Rust backend. But as the bitter cynic I am, I guess it is an effort to shut down and control as much of the open source use of Bitwarden as possible.

        The worst case, someone will most likely fork Vaultwarden and we can still access it with Keyguard on mobile and the excellent Vaultwarden web interface :)

        • Magnus Åhall
          link
          fedilink
          English
          011 months ago

          Phew, looks good on the news with the packaging bug (if they didn’t just got cold feet for worse PR/backlash than they expected and this is a backtracking).

          In this case, hopefully Garcia is employed for his expertise and can be deployed to further open source relations :)

    • @fuckingkangaroos@lemm.ee
      link
      fedilink
      English
      011 months ago

      I don’t understand.

      Are you saying it’s a bait and switch like Google, where they suck people in with a good product then enshittify it once they’re hooked?

      • @ArkyonVeil@lemmy.dbzer0.com
        link
        fedilink
        English
        011 months ago

        I’m not thoroughly aware of their dealings, but these amounts of private investment aren’t going to pay for themselves. If you raise 100 million, investors typically want a billion back, or more.

        From the looks of it, Bitwarden might’ve tried to go with the Open Source model to get free development resources, trust (because it’s an open source PASSWORD manager), and general goodwill. But now that they’ve deemed that got enough of a market share (or investors are starting to breathe down their necks), it’s time to start raising the walled garden.

        Even if they claim after the fact that it was a “Bug” that the client couldn’t be built without their proprietary sdk. The very fact one exists is a bad enough sign, specially when its influence is spreading.

        VC is a devil’s bargain. Raising VC money is NEVER a good sign.

  • @Shape4985@lemmy.ml
    link
    fedilink
    English
    011 months ago

    I use to always recommend bitwarden to people. Now i feel like an idiot for doing so with them switching up. Ill be making the effort to move to keepassxc soon and host it myself.

    • GHiLA
      link
      fedilink
      English
      011 months ago

      …host it?

      …is there something I’ve been missing out on? Can one host a KeePass vault online? We have web apps? I only know about the Nextcloud ones. I’ve just been using syncthing and merging the conflicts when they happen.

    • @AbidanYre@lemmy.world
      link
      fedilink
      English
      011 months ago

      I like pass and used it for a while, but sharing passwords with it wasn’t nearly as straightforward as it is with bitwarden.

    • Virkkunen
      link
      fedilink
      011 months ago

      By trying to make things simple, this ends up making it more complicated and convoluted than anything

    • DarkThoughts
      link
      fedilink
      011 months ago

      Unix elitist think the average user is willing to just memorize a gazillion different commands. No, nope. Not ever going to use a command line password manager.

      • @AbidanYre@lemmy.world
        link
        fedilink
        English
        0
        edit-2
        11 months ago

        Is typing “pass” into a terminal really that much harder than typing <passwordmanager>.com into a browser?

        • DarkThoughts
          link
          fedilink
          011 months ago

          I really don’t know why you think I’m doing that in the first place.

          • @AbidanYre@lemmy.world
            link
            fedilink
            English
            011 months ago

            Because unless you paid someone else to set up an account for you, you had to get there somehow. And if you’re using the built in password manager from your browser, none of this article is relevant to you anyway.

            • Cris
              link
              fedilink
              English
              0
              edit-2
              11 months ago

              Most people use an extension on web and an app that uses the system autofil functionality on mobile (at least on android, I’ve not used iOS for a long time)

              You don’t have to open anything, or type anything other than a password. On mobile you just use your fingerprint, don’t have to type anything at all.

              If you’re taking about initial setup that’s also gonna be a lot more complicated for an average user than bitwarden.

              A command line tool is not even remotely a comparable user experience. It may work wonderfully for you, and I’m glad it does, but it’s pretty out of touch to suggest that it’d be a good fit for most people

            • @WhyJiffie@sh.itjust.works
              link
              fedilink
              English
              011 months ago

              have you heard about bookmarks? browser addons? smartphones? URL-checked autofill?

              keepass is superior to pass. it even has a CLI.

  • @unskilled5117@feddit.org
    link
    fedilink
    English
    0
    edit-2
    11 months ago

    This is an importang issue IMO that needs to be addressed and the official response by Bitwardens CTO fails to do so.

    There is not even a reason provided why such a proprietary license is deemed necessary for the SDK. Furthermore this wasn’t proactively communicated but noticed by users. The locking of the Github Issue indicates that discussion isn’t desired and further communication is not to be expected.

    It is a step in the wrong direction after having accepted Venture Capital funding, which already put Bitwardens opensource future in doubt for many users.

    This is another step in the wrong direction for a company that proudly uses the opensource slogan.

    • sunzu2
      link
      fedilink
      011 months ago

      Welp, I guess another time to move here soon.

      And I just fucking vouched for them to a friend recently 🤡

      Didn’t know about VC funding these parasites using their funding to turn everything into shite.

      What’s the current “best” alternative? Keepass?

      • @foggenbooty@lemmy.world
        link
        fedilink
        English
        011 months ago

        I haven’t jumped yet, but the Proton suite is looking more and more appealing. I’ve been eyeing them as a Gmail replacement, but I’ve been happy with my VPN and password management providers. As this reduces the bundle makes more sense.

        • sunzu2
          link
          fedilink
          011 months ago

          They have a solid value proposition but don’t like putting all my eggs all in one basket both for security and monopoly reasons.

          They seem to be gunning for one stop shop and I think they are doing decent shop but I just don’t like the idea after what Google did to us.

          Situation is a bit different but gonna need to tka the lessons and not let these corpos do this again.

          • @foggenbooty@lemmy.world
            link
            fedilink
            English
            011 months ago

            That’s a good practice, and I think you’re right that is what they’re going for. I don’t think that means you shouldn’t consider them, but it does lower their value proposition as the bundle is the better deal.

      • @Artaca@lemdro.id
        link
        fedilink
        English
        0
        edit-2
        11 months ago

        It’s not open source, but I got a lifetime license for Enpass over a decade ago and it’s done everything I’ve ever needed it for. I think stacksocial occasionally has new lifetime codes for sale. I like the idea of Proton Pass as others have said, but it feels a bit like putting all my eggs in one basket, which is a mistake I already made with Google before (context: I use Proton for email). I think Keepass is the next best option if dedicated to staying FOSS.

    • irotsoma
      link
      fedilink
      English
      011 months ago

      They’re basically trying to get rid of vaultwarden and other open source forks. I expect they’ll get a cease and desist and be removed from github at some point in the not too distant future if they don’t make some changes. I have a vaultwarden instance and use the bit warden clients. Guess I’ll need to look for alternatives in case Bitwarden decides to get aggressive.

    • @oaklandnative@lemmy.world
      link
      fedilink
      English
      011 months ago

      Proton Pass is open source and the company that runs it recently reincorporated as a Swiss non-profit to ensure their privacy mission can’t be bought out by venture capitalists etc.

      https://www.reddit.com/r/ProtonPass/comments/153t85q/proton_pass_is_open_source_and_has_now_passed_an/?utm_source=share&utm_medium=mweb3x&utm_name=mweb3xcss&utm_term=1&utm_content=share_button

      https://proton.me/blog/proton-non-profit-foundation

      • @ilmagico@lemmy.world
        link
        fedilink
        English
        011 months ago

        +1 For KeePassXC and the KeePass ecosystem. Yes, you need to sync the database yourself, but you can use any file sharing service you like, e.g. google drive, dropbox… or selfhost something like nextcloud (like I do), which for me is actually a point in its favor.

        Based on this news, I think I made the right choice back then when I decided to go with KeePass.

        • @kill_dash_nine@lemm.ee
          link
          fedilink
          English
          011 months ago

          As someone who used to use KeePass, went to LastPass, and then Bitwarden (Vaultwarden), I finally got my non-tech literate wife to use Bitwarden. I’m concerned that KeePass might end up being more difficult if it comes down to it. I believe that KeePass had some sort of browser integration but it really has been a long time since I used it so who knows the current state. Curious how browser integration is today.

          • @ilmagico@lemmy.world
            link
            fedilink
            English
            011 months ago

            I use KeePassXC’s browser integration daily and it works pretty well with Firefox (linux), well enough that I’m not complaining, but I cannot compare it with Bitwarden cause I never used it. On Android I use Keepass2Android and works well with autofill, but again, I can’t really compare it.

            Something tells me Bitwarden works better, just by virtue of being a commercially supported product, but I have no complaints with KeePassXC & Keepass2Android (KeePassDX works well on android too). Original KeePass desktop client was never great though.

          • GHiLA
            link
            fedilink
            English
            0
            edit-2
            11 months ago

            The big issue isn’t using it, it’s syncing it.

            User A used KeePass to order pizza and changed the Papa John’s(heaven forbid) password while they were at it, on their desktop.

            syncing: “oh! This file changed! Neat!”

            User B picks up their phone and wants to order Papa John’s at work. They try, but the password isn’t right. Huh. They check KeePass. No issues. They go to change the password because they think something is wrong.

            (All the while, they never thought to see if syncthing had been woken up in the background lately)

            They change the password, update KeePass,

            syncthing opens later, goes: "Oh, hi, User B’s phone! I have a ne- Oh! You have a new password file too!!? Small world! I’ll take both!

            Now there’s two files, two users who think they both made corrections to a password, syncthing thinking nothing is wrong, and someone has to now merge the newer KeePass file over the old ones by hand and realize what happened, but the bigger problem is, no one knows anything is wrong yet and it doesn’t even take two users. This can just be you ordering on your phone after modifying on your desktop.

            well, it’s just pizza.

            As an example. Imagine an insurance app, or a banking app, or the DMV… And you won’t know for months down the line. It gets old.

            • @kill_dash_nine@lemm.ee
              link
              fedilink
              English
              011 months ago

              Ah yeah, the fun of how that works. I recall that I had previously set up WebDAV to try to simplify my source of truth but I think that was just with the original KeePass app, not KeePassXC. I also wasn’t trying to share passwords among multiple people but I do recall having issues when I was using Dropbox to sync to my phone since I would have to actually make sure Dropbox had updated the copy of the file which required me opening the app at the time.

    • @ChillPill@lemmy.world
      link
      fedilink
      English
      011 months ago

      Keepass? No cross device support, you need to manage that yourself through something like Google Drive…

      • @ilmagico@lemmy.world
        link
        fedilink
        English
        011 months ago

        What do you mean “no cross device support”? KeePassXC supports Win, Mac, Linux and there are iOS and Android apps available…

        As for the lack of cloud and requirement to provide your own synchronization, for some (like me) that’s a feature, not a limitation :)

        • @hedgehog@ttrpg.network
          link
          fedilink
          English
          011 months ago

          Do any of the iOS or Android apps support passkeys? I looked into this a couple days ago and didn’t find any that did. (KeePassXC does.)

          • @ilmagico@lemmy.world
            link
            fedilink
            English
            0
            edit-2
            11 months ago

            I don’t use passkeys so I don’t know. Maybe I should research into passkeys, what’s the benefit over plain old (long, randomly generated) passwords?

            • @ilmagico@lemmy.world
              link
              fedilink
              English
              0
              edit-2
              11 months ago

              Ok, from a quick search, it seems passkeys rely on some trusted entity (your browser, OS, …) to authenticate you, so, yeah, I’m not sure if I like that. The FIDO alliance website is all about how easy, convenient and secure passkeys are, and nothing about how they actually work under the hood, which is another red flag for me.

              I’ll stick to old-fashioned, long, secure, randomly generated passwords, thanks.

              • deejay4am
                link
                fedilink
                English
                011 months ago

                Passkeys rely on you holding a private key. The initial design was that a device (like a browser or computer/phone) stored the private key in a TPM-protected manner, but you can also store it in a password manager.

                This is more secure than a password because of the way private/public key encryption works. Your device receives a challenge encrypted with the public key, decrypts with the private key and then responds. The private key is never revealed, so if attackers get the public key they can’t do shit with it.

                Just be sure that your private key is safe (use a strong master password for your PM vault) and your passkey can’t be stolen by hacking of a website.

                • @ilmagico@lemmy.world
                  link
                  fedilink
                  English
                  011 months ago

                  I see, that makes sense and should be more secure, in theory. Thanks for the explanation.

                  The issue I have is, whether I need to trust a third party with my private key, e.g. Google with Android, Microsoft with Windows, etc. (yes on linux it’s different, but that’s not my only OS).

                  Also if the private key does get compromised (e.g. local malware steals it), hopefully there’s an easy way to revoke it.

            • @jqubed@lemmy.world
              link
              fedilink
              English
              011 months ago

              I’m no expert in this but the passkeys really on some sort of public key, cryptographic pair. Your device will only send your encrypted cryptographic secret when it gets the correct encrypted cryptographic secret from the destination. This makes it much harder to steal credentials with a fake website or other service.

        • Shirasho
          link
          fedilink
          English
          011 months ago

          It means we have less insight on what they are doing with our passwords.

        • @winterayars@sh.itjust.works
          link
          fedilink
          English
          011 months ago

          No, technically they already are SaaS company. That’s mostly how they make their money.

          Also it should be noted “no longer open source” doesn’t mean they’ve done a “our code is now closed and all your passwords are ours” rug pull like some other corporations. This is a technical concern with the license and it no longer meets proper FOSS standards (in other words, it has a restriction on it now that you wouldn’t see in, for example, the GPL).

          So by and large the change is very minimal, the code is still available, it’s still the best option. However, this does matter. It may be a sign of the company changing directions. It’s something they should get pushback about.

          • @sugar_in_your_tea@sh.itjust.works
            link
            fedilink
            English
            011 months ago

            From the update, it looks like they consider it a bug, which they’re working to resolve. Let’s see how they resolve it before jumping to conclusions.

          • @dustyData@lemmy.world
            link
            fedilink
            English
            0
            edit-2
            11 months ago

            The SDK was never FOSS, and was never under the GPL. Hence why they can add the text mentioned in the article. You don’t get to change the text of a FOSS license to begin with. It isn’t unheard of for text like this to be part of proprietary software that integrates with and uses FOSS that are under different licenses.

            That said, this is concerning, but whether it changes BW’s FOSS state is a matter of legal bickering that has been going on for decades.

            • @KairuByte@lemmy.dbzer0.com
              link
              fedilink
              English
              011 months ago

              You can’t retroactively change FOSS licensing, but oft times you can alter the licensing moving forward. Not always the case, of course. But in no way are all FOSS licenses set in stone.

  • @mli@lemm.ee
    link
    fedilink
    English
    011 months ago

    Update: Bitwarden posted to X this evening to reaffirm that it’s a “packaging bug” and that “Bitwarden remains committed to the open source licensing model.”

    According to Bitwardens post here, this is a “packaging bug” and will be resolved.

      • Liz
        link
        fedilink
        English
        011 months ago

        I switched from keepass to Bitwarden because individual entries started randomly disappearing. I’m still discovering missing accounts after switching a couple of weeks ago. Sometime to do with how keepass was opening the files, because when an entry went missing it was gone even from backup files I hadn’t touched since before the entry disappeared.

        • @Serinus@lemmy.world
          link
          fedilink
          English
          011 months ago

          Sound like something you did with replacing files. Bitwarden is dead simple, and that’s why it’s great.

    • @sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      011 months ago

      In this case, zero, because it’s a packaging bug, not an actual change in direction. Read the update on the article:

      Update: Bitwarden posted to X this evening to reaffirm that it’s a “packaging bug” and that “Bitwarden remains committed to the open source licensing model.”

      Next time, before jumping to conclusions, wait a day or two and see if the project says something.

      • @486@lemmy.world
        link
        fedilink
        English
        011 months ago

        I really hope that this is actually the case, but I am not very optimistic. This doesn’t seem to be a mistake. They intentionally move functionality of their clients to their proprietary SDK library. The Bitwarden person stated this in the Github issue and you can also check the commit history. Making that library a build-time dependency might actually have been a mistake. That does not change the fact, that the clients are no longer useful without that proprietary library going forward. Core functionality has been move to that lib. I really don’t care if they talk to that library via some protocol or have it linked at build time. I wouldn’t consider this open source, even if that client wrapper that talks to that library technically is still licensed under GPLv3.

        • @sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          011 months ago

          They intentionally move functionality of their clients to their proprietary SDK library.

          Proprietary is a strong word IMO. Here’s the repo, it’s not FOSS, but it is source available. It’s entirely possible they make it more open once it stabilizes, but it’s also possible they make it less open as well. It’s still early, so we don’t know what the longer term plans look like.

          I don’t think we should be panicking just yet, but I’ll certainly be checking back to see what happens once this internal refactor is finished, and I’ll be making some more regular backups just in case they are, in fact, trying to take it proprietary. I don’t think that’s the case (why would they? I don’t see the benefit here…), but I guess we’ll see.

          • @486@lemmy.world
            link
            fedilink
            English
            011 months ago

            Proprietary is a strong word IMO. Here’s the repo, it’s not FOSS, but it is source available.

            Yeah, that’s what I meant by “proprietary”. I guess having the source to look at is better than nothing, but it still leaves me uneasy. Their license lets them do anything they want (ignoring that - as it stands - their license is void due to the linkage with GPLv3 code, but they said they want to fix that). I have no idea what their plan is. I don’t think it is in their best interest to go the route they appear to be going. Having truly open source clients seems to be a selling point for quite a few customers. But what do I know…

      • ArxCyberwolf
        link
        fedilink
        English
        011 months ago

        Not sure who downvoted you, you literally quoted the article.

    • @JustARaccoon@lemmy.world
      link
      fedilink
      English
      011 months ago

      Sadly as many times as needed, complacency is how these companies get “loyal customers” who are willing to put up with bs

      • @doktormerlin@feddit.org
        link
        fedilink
        English
        011 months ago

        That’s far from the best option. It’s working, but it’s super complicated compared to Bitwarden and other cloud password managers. Imagine telling your grandma “just use keepass”, she would never be able to make it work. But Bitwarden? Lastpass? That’s possible

        • @cy_narrator@discuss.tchncs.de
          link
          fedilink
          English
          0
          edit-2
          11 months ago

          Is it so?

          I feel like anyone who can open up and edit ms word can do it, just double click on the keepass.kdbx file and it opens up prompting for a password.

          Syncing is a bit of a problem and I wrote an article on how I do it here in the easiest way I found. Though MEGA cloud does not have a good reputation among general public, their share link is something you can write in a piece of paper and keep in a safe.

          • @doktormerlin@feddit.org
            link
            fedilink
            English
            011 months ago

            “Just double click the keepass.kdbx” is not what it is. You need to go to your explorer, find the file in the folder structure and double click it. You then need to search for the website you are on and copy the password, then you need to go back to the website within 12 seconds and paste the password. That’s inconvenient for everyone, but for a tech-illiterate grandma it’s impossible.

            Compare that to Bitwarden: You go to the website, click on the bitwarden icon and then click on the login details. Or even better, you can enable auto-complete with a single click and it automatically fills the login details when on the website, without clicking anything. That’s far more convenient and easier.

            Just as a FYI: My grandma has a sticky note on her laptop that shows exactly which buttons to press to get to her emails, with things like “Click this twice within 2 second, be fast!!” for a double click. It doesn’t say “lef mouse button”, she draw her touchpad and an arrow. She is not able to find her mails when the website changes the layout.

    • Ghostface
      link
      fedilink
      English
      011 months ago

      This is by no means to a slight towards bitwarden. Solid product and community

    • r00ty
      link
      fedilink
      011 months ago

      If they’re moving away from open source/more monetisation then they’re going to do one of two things.

      1: Make the client incompatible (e.g you’ll need to get hold of and prevent updating of a current client).
      2: DMCA the vaultwarden repo

      If they’re going all-in on a cash grab, they’re not going to make it easy for you to get a free version.

      • @potustheplant@feddit.nl
        link
        fedilink
        English
        011 months ago

        You can’t “dmca” the fork that was created while it was still open source. They could only prevent it from getting future updates (directly from them).

        • irotsoma
          link
          fedilink
          English
          011 months ago

          DMCA is a tool for suppression of free information. It doesn’t require evidence that you’ve made a good faith effort to consider fair use or other legal complexity as it’s meant to take down the information before that is settled in court, but most commonly used to suppress information from a person or group who can’t afford to fight it in court. Microsoft’s Github has a history of delete first without risking their own necks to stand up for obviously fraudulent takedowns much less ones with unsettled law like APIs/SDKs.

        • r00ty
          link
          fedilink
          011 months ago

          If you mean they shouldn’t. I’d agree. But, as has been seen a lot on youtube. “They” can DMCA anything they want, and the only route out is usually to take them to court.

          I mean I’d hope if they’re going in this direction they will be decent about it. But, it’s not the way things seem to be lately.

      • @schizo@forum.uncomfortable.business
        link
        fedilink
        English
        011 months ago

        Don’t forget option 3: someone writes a vaultwarden client independent of the closed-source crap.

        If you can write a server that fully supports the client via the documented API, then you know everything you’d need to do to make a client as well.

        • @humorlessrepost@lemmy.world
          link
          fedilink
          English
          011 months ago

          That’s not a third option in the same list (things they are going to do), it’s an item in an entirely different list (foss responses to their actions).

  • @Routhinator@startrek.website
    link
    fedilink
    English
    011 months ago

    Alright does anyone have opinions on Nextcloud Passwords? There’s apps for it and it would sync to my Nextcloud.

    I hate this. Bitwarden has been a good app.

    • @sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      011 months ago

      Bitwarden has been a good app.

      And it still is. There’s no reason to stop using Bitwarden, and I will continue my plans to switch to Vaultwarden.

      As @Krzd@lemmy.world said, it’s a packaging bug, not an actual change in license. If you read the article, it says as much in the update.

    • GHiLA
      link
      fedilink
      English
      011 months ago

      Nextcloud passwords is just a client for a KeePass vault.

      I guess it’s as good or bad as that can be, but I’m sure it’s limited in functionality to KeePassxc with plugins.

      • @Wispy2891@lemmy.world
        link
        fedilink
        English
        011 months ago

        Are you sure?

        Because last time I tried that it was THE worst password manager that i ever tried in my life. I’d feel safer with the ie6 password manager

    • Krzd
      link
      fedilink
      English
      011 months ago

      It’s a packaging bug, the headline is false.

    • @octopus_ink@lemmy.ml
      link
      fedilink
      English
      011 months ago

      No one is listening I’m sorry to say. I corrected a couple people but then realized it was pointless. The discussions in the crossposted communities (which - holy shit I don’t think I’ve seen something so thoroughly spammed across multiple tech communities before) are just as bad or worse.

    • qaz
      link
      fedilink
      English
      011 months ago

      Why would it be fake news? Because they called it a “packaging bug”?

    • @locuester@lemmy.zip
      link
      fedilink
      English
      0
      edit-2
      11 months ago

      Community is fine, your comment is at the top, along with others pointing this out.

      It’s the “non-community” if you will boosting this. The passerby’s not reading comments.

    • @ammonium@lemmy.world
      link
      fedilink
      English
      011 months ago

      How is it fake news? They are moving functionality into a proprietary SDK and have a whole framework ready to get around the GPL.