[–] 4 points 6 months ago

Why is this called 2.0? PWA without offline is assumed to be 1.0?

I don't like them randomly defining and attributing version numbers to standards. These versions don't exist. And they don't even define them.

PWA and offline capability has been around for a while. PWA typically raises the question of offline capability. That's not a new thing or a new standard.

  • source
  • [–] 0 points 6 months ago*

    Creating a sticky header is an easy task with position: sticky. But what about a sticky header that sticks for real?

    I don't get it. Sticky is sticky. What is "sticks for real"? The example looks no more sticky than normal sticky. Except is has a different shape.

  • source
  • [–] 6 points 7 months ago*

    Open core, closed extensions. Not really clear how that significantly improves the situation. I doubt they'll diverge the two code bases(?).

    The vault symbolism is pretty bad. A software product is much different to a vault, and a sister-vault-product you publish the blueprint for anyway.

    At the same time, we still care deeply about open source. That’s why we are releasing a version of our codebase to the community under the MIT license as Cal.diy.

    While our production codebase has significantly diverged, including major rewrites of core systems like authentication and data handling, we want to ensure there is still a truly open version available for developers, hobbyists, and anyone who wants to explore and experiment.

    Huh? I don't get it. So the open product is an older, worse/different version/codebase? And they can do that without impacting their product risk because it's different?

  • source
  • [–] 1 point 7 months ago

    I wonder what upsides those "web client" extensions bring for platforms you could just open "clients" as websites for (telegram, tiktok listed). Not need to install an extension.

  • source
  • [–] 1 point 7 months ago

    The (A)GPLv3 makes it clear that it permits all licensees to remove any additional terms that are "further restrictions" under the (A)GPLv3. It states, "[i]f the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term."

    Interesting, and quite clear.

    The whole response is very good, reasonable, and direct.

    I'm interested to see what OnlyOffice will do. Maybe they'll relicense their whole product, leading to a community fork under AGPL.

  • source
  • [–] 1 point 7 months ago* (last edited 7 months ago)

    Cooperation and sharing performs significantly better for collective gains. This applies to all kinds of concepts. Science, public infrastructure, common goods, common resources, governance, trade agreements, EU, medicine, software…

    Where it becomes problematic is when parties reap gains without participating. Using science to develop products and gain further knowledge without sharing them, using public infrastructure without paying taxes, using common infrastructure and frameworks without committing to them, nationalism, monopolies on medicine, proprietary software and platforms that are not cooperative…

    Much of our transformation and development speed and gains in the last century has been in a framework of cooperation. In the current global politics, we can see and imagine what rejecting cooperation could lead to and where it could lead us to.

    FOSS is great for the same reasons as other forms of cooperation: Collective gains.

    Unfortunately, we have not solved the issue of beneficiaries that don't actively participate and contribute yet.

    In patent law, you publish your findings and get a timespan of authoritative use and control but at the same time commit to it being publicly accessible and at some point usable. Some software licenses attempt to do the same.

    In music licensing, there's frameworks for collective licensing.

    Some frameworks use centralized/government regulation and prosecution to ensure play-fair systems. (To varying degrees and success, obviously.)

    I get where you're coming from, but I disagree [with disliking the software freedom]. The upsides and collective gains of software freedom are undeniable. Where we need to do and establish more, and some things are happening in some places, is to ensure a positive collaborative environment overall.

  • source
  • parent
  • context
  • view more: ‹ prev next ›