• 0 Posts
  • 77 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle








  • So if I watch all Star Wars movies, and then get a crew together to make a couple of identical movies that were inspired by my earlier watching, and then sell the movies, then this is actually completely legal.

    It doesn’t matter if they stole the source material. They are selling a machine that can create copyright infringements at a click of a button, and that’s a problem.

    This is not the same as an artist looking at every single piece of art in the world and being able to replicate it to hang it in the living room. This is an army of artists that are enslaved by a single company to sell any copy of any artwork they want. That army works as long as you feed it electricity and free labor of actual artists.

    Theft actually seems like a great word for what these scammers are doing.

    If you run some open source model on your own machine, that’s a different story.


  • https://discord.com/terms#5 is pretty permissive

    Your content is yours, but you give us a license to it when you use Discord. Your content may be protected by certain intellectual property rights. We don’t own those. But by using our services, you grant us a license—which is a form of permission—to do the following with your content, in accordance with applicable legal requirements, in connection with operating, developing, and improving our services:

    Use, copy, store, distribute, and communicate your content in manners consistent with your use of the services. (For example, so we can store and display your content.)
    Publish, publicly perform, or publicly display your content if you’ve chosen to make it visible to others. (For example, so we can display your messages if you post them in certain servers or recommend that content to others.)
    Monitor, modify, translate, and reformat your content. (For example, so we can resize an image you post to fit on a mobile device.)
    Sublicense your content, to allow our services to work as intended. (For example, so we can store your content with our cloud service providers.)
    



  • I’d be more worried about media than the ability to pirate it.

    Music has adapted to generate plays. Platforms are already being polluted with genAI music.

    TV was replaced by streaming services. Series come and go and are very specifically tailored to get people to subscribe. Exclusives are the standard. Single season productions are not uncommon. People are also already investigating ways to pollute this pool with genAI as well.

    Movies are a stream of Marvel and Disney garbage that was already more CGI than acting. Now genAI and upscaled classics are on the menu.

    Piracy will not go away. People used to record movies with camcorders in the cinema, now they pull raw files from CDN nodes. There is always the scene. The platforms that try to profit from the scene come and go.


  • I wasn’t actively aware of this for most of my life until I recently visited a clients office. Buying someone a cup of coffee is an entire thing. There’s no free coffee. You have to purchase every single cup. And you first have to walk several minutes to the place where they sell the coffee. It blew my mind. I’m used to drinking one cup after the other without even giving it any thought. Coffee machine right next to me or around the corner. There, coffee incurs friction and cost.

    So when you invite someone for a cup of free coffee, this can open doors for you. I’m not kidding. People get all excited when you offer them a coffee break on your dime. And there’s levels to it too. There’s the regular coffee, and there’s the premium one. For the premium you have to walk longer and wait in line until the barista serves you.

    It’s a key component in office politics when coffee access is regulated.

    Why anyone would restrict access to legal stimulants in the office is unclear to me though. Put espresso machines on every desk!




  • I don’t necessarily disagree, but I have spent considerable time on this subject and can see merit in decoupling your own error signaling from the HTTP layer.

    No matter how you design your API, if you’re passing through additional layers, like load balancers and CDNs, you no longer have full control over all responses your clients receive. At this point it may be viable to always signal a successful backend connection with a 200, even if the process resulted in a failure.

    Going further, your API may include partial success scenarios, think batch processing, then the result could be a mix of success and failure that doesn’t translate to HTTP status.

    You could even argue that there is really no reason to couple your API so tightly with a concept of the transport layer it uses.


  • Respect the Accept header from the client. If they need JSON, send JSON, otherwise don’t.

    Repeating an HTTP status code in the body is redundant and error prone. Never do it.

    Error codes are great. Ensure to prefix yours and keep them unique.

    Error messages can be helpful, but often lead developers to just display them in the frontend, breaking i18n. Some people supply error messages in multiple languages, depending on the Accept-Language header.