• 2 Posts
  • 49 Comments
Joined 3 years ago
cake
Cake day: June 28th, 2021

help-circle
  • ᗪᗩᗰᑎ@lemmy.mltoLinux@lemmy.mlFlathub has passed 2 billion downloads
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    2
    ·
    edit-2
    11 days ago

    Offline/internal network installs can be handled with flatpak create-usb - https://docs.flatpak.org/en/latest/usb-drives.html

    One can distribute flatpaks along with their dependencies on USB drives (or network shares, etc.) which is especially helpful in situations where Internet access is limited or non-existent.

    Cache/mirroring would be great for those who need it.

    Edit:

    Thinking about it, I wonder if there’s enough “core features” with ‘create-usb’ that its just matter of scripting something together to intercept requests, auto-create-usb what’s being requested and then serve the package locally? If a whole mirror is required, it may be possible to iterate over all flathub packages and ‘create-usb’ the entire repo to have a local cache/mirror? Just thinking “out loud”.







  • First off, how can you claim RCS "requires you to buy an Android and then state iMessage is "cross platform through Apple’s ecosystem? RCS works on Android and is available in various devices from many manufacturers. iMessage is only available on devices sold by Apple.

    Secondly, why would you rate iMessage higher than RCS for “ease of use”? That makes zero sense, they behave basically the exact same way.

    Lastly, RCS is coming to iOS - Apple’s just been lagging because implementing a cross-platform solution is detrimental to their profits.

    So RCS will eventually work across iOS and Android AND work by default. There’s no reason RCS wouldn’t be easier or rated higher than iMessage in terms of “ease of use”



  • There’s a few clients for Signal, nobody is preventing developers from creating apps; there’s Molly, gurk-rs, Axolotl, Flare, signal-cli, Pidgin (with the Signal plugin.

    The problem is 3rd party clients don’t implement all features because it takes a lot of work and they’re created/developed by volunteers - just take a look at Matrix and how many clients support all features or even just group end-to-end encryption (E2EE). Last I checked many third party Matrix clients didn’t support encrypted group messages, primarily just Element, the reference client built by the matrix developers. So you have the same problem on Signal that you have on Matrix.








  • It’s disingenuous to act like this is some huge burden.

    Having to double your software engineers, UI/UX designers, QA engineers, DevOps, and localization/accessibility specialists to handle a second browser is a HUGE burden for a non-profit.

    If you don’t care about quality, security, or user experience, sure you can just pass a “does it compile” test and push to prod. You’ll quickly find that nobody wants to use this under resourced browser.

    Or if it’s such a pain, you don’t bother and just ship the WebKit version everywhere.

    This is exactly what Apple wants. They don’t want to give people a real choice because they’re scared of real competition.