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

help-circle


  • Depending on your jurisdiction it is probably your responsibility to enforce your copyright. I can always just record your music off a streaming platform. You can attach a license to your song in funkwhale (see this). If you want DRM for your music then funkwhale is probably also not for your. You still have to enforce your self that nobody monetizes your works if you don’t allow it. You can delete things from the fediverse if you know the source but I don’t think funkwhale allows DRM protected music.

    If you attach a license to your works that doesn’t allow monetization and they monetize the app you can sue them. I doubt they will though. And they probably wouldn’t be very successful because the app and the server are open source. You could just build the app without monetization. And someone probably would.

    The upload and sharing copyrighted music probably falls into the hands of the instance admin. As with PeerTube it is probably not a good idea to have open signups. But everyone has to make sure that doesn’t happen.

    The fediverse is an open and very liberal space. If you want full control over your works it is probably not for you. No software with federation probably is. If you want and need to control over your works (which is legitimate) you need something with a tighter grip, maybe host the things yourself on your server with DRM. That doesn’t mean it is bad for everyone.






  • There is a whole field, that looks a bit like religion to me, about how to test right.

    I can tell you from experience that testing is a tool that can give confidence. There are a few new tools that can help. Mutation testing is one I know that can find bad tests.

    Integration tests can help find the most egregious errors that make your application crash.

    Not every getter needs a test but using unit tests while developing a feature can even save time because you don’t have to start the app and get to the point where the change happens and test by hand.

    A review can find some errors but human brains are not compilers it is hard to miss errors and the more you add to a review the easier it can get lost. The reviews can mostly help make sure that the code is more in line with the times style and that more than one person knows about the changes.

    You can’t find all mistakes all the time. That’s why it is very important to have a strategy to avert the worse and revert errors. If you develop a web app: backups, rolling deployments, revert procedures. And make sure everyone know how and try it at least once. These procedures can fail. Refine them trough failure.

    That is my experience from working in the field for a while. No tests is bad. Too many tests is a hassle. There will always be errors. Be prepared.





  • Yes and no. For apple you can use their phones for quite a long time securely. For Android that is a very different story. As far as I know only Google with their new pixel phones and Samsung have offered more than 2 years of updates. After that time your phone becomes a security risk. So make sure your devices receives updates or can be used with a custom ROM (though that can be insecure as well).


  • There is a common misconception that long term effects will manifest long after the injection. All vaccines with longterm effects manifested their effect shortly after the injection. It makes little sense that you will have adverse reactions months or years later because the compounds are long gone from your system.

    There was also the misconception that the vaccine was rushed and that steps were skipped or shortened during testing. That is not the case. The administrative processes were prioritized and there was a huge amount of test candidates so testing could be done much quicker. The normal process is not longer because they want to gather more long term data but because it just takes longer to gather it.