• 5 Posts
  • 191 Comments
Joined 3 years ago
cake
Cake day: July 25th, 2023

help-circle



  • eksb@programming.devtoComic Strips@lemmy.worldThe same rights
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    11 days ago

    Do you even cycle?

    There are several reasons to do this:

    • Most of the sensors that make the lights change will not sense bicycles, so the light will never change.
    • In many places, getting a jump on the car traffic between the light and the next is much safer, because you are getting passed mid-block instead of at the intersection, where you are much more likely to be hit by a turning car.
    • Jumping the light usually means being noticed by drivers while you are moving and they are not, which is great because drivers are notoriously bad at noticing at noticing anything smaller than a 7-11 when they are moving. I have been hit 4 times while stopped at stop signs and red lights, three of which while IN MY CAR, because drivers simply cannot be trusted to pay attention.
    • Usually waiting at the light with the cars means the car in front of you is belching exhaust right into your face.

    I now live in a city with very good cycling infrastructure, and a vast majority of people wait for the light, because when the infrastructure is designed well, it is safer to do so.






  • IANAL. I originally interpreted the license.txt as: all of the source code is AGPL (see lines 234-235), some of the source is also Apache 2.0, and the binaries are MIT; plus a trademark notice and contact info for getting a commercial license. After rereading it, my only conclusion is that this is a dumpster fire of a license.txt, and can be reasonably read several different ways.


  • eksb@programming.devtoSelfhosted@lemmy.worldAlternatives to Mattermost
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    6
    ·
    18 days ago

    At the copyright owner, they are within their rights to release the source code under the AGPL, and also sell it under other licenses. Anyone is free to use the code under the AGPL. Nobody who releases code under an open-source license is obligated to provide binaries.

    As the copyright owner, they are free to use the code along with other non-open-source code (e.g.: SSO integrations) to build a non-free product.