• 1 Post
  • 20 Comments
Joined 3 years ago
cake
Cake day: May 26th, 2021

help-circle

  • doing this on Python or whatever language?

    If you’re on Linux, MacOS or some BSD doing this with a bash script would be the easiest imo, since there already exists ready-made software for all the steps.

    • Unpacking: unzip, unrar, 7z (the latter can handle many different formats)
    • Sorting the images: find
    • Converting them to pdf: img2pdf, imagemagick

    You can even automate the downloading with e.g. wget.

    Should be straight forward (just a series of commands and some command substitution for the find part) as long as you don’t have too many images.

    On windows you could (probably) do the same with a python script (or maybe powershell idk)

    Are email requirement the default for lemmy instances or it is something an operator has to choose?

    That can be configured.




  • In germany we have glass bottles that are reused, you pay a per bottle deposit (0,08€, non-reusable is 0,25€) and get it back when you bring the bottle back to the market. The market will send the bottle back to the company it came from and they will clean it and reuse it for bottling again if it’s still good.

    There is also reuse for plastic bottles, but it is less common, at least everywhere I lived. (reuse is done regionally) Also they can’t be reused as often as glass bottles. One could reuse metal containers, but that isn’t done. I’d guess because they aren’t transparent and so cannot be inspected by bottling systems as easily.

    Soft-drinks usually aren’t reusable, because they aren’t distributed locally.




  • If you use your distro’s up-to-date built and packaged from source applications it’s unlikely you’ll have a problem. Those start when you want to use old packages or packages from a different distro (with different or patched libs) with your system.

    Flatpak, AppImage etc. packaged apps will run on (almost) any system and you only need to build them for different processor architectures. So it’s the ovious choice for lazy or profit oriented developers.



  • Imo they’re right, but theres some weird (pro proprietary software) claims in there.

    If I ship an app for Windows I don’t have to include the entire Win32 or .NET runtimes with my app. I just use what’s already on the user’s system.

    Those cases are rare on windows, most apps package their own versions of dependencies just like with snap/flatpak/appimage (just not so neatly organized) and it sucks.

    Backwards compatibility is a major part of why Windows is still the dominant desktop OS.

    But thats also a major part in why it sucks and is insecure. Microsoft knows that and has started to break stuff with higher frequency too. You should only freeze interfaces when there is a consensus that there isn’t anything to be improved anymore. You can only build this consensus when you have a clear use case.

    I’d argue, that this is impossible for operating systems with desktop and all. So best you can do for backwards compatibility is to only put breaking changes in major versions and still maintain older ones. Of course that means you can’t have major versions to often and now people will complain that your software sucks because it can’t even do X.

    Microsoft does this too, but they often release a whole new product instead of version bumps. And by that they accumulate even more technical debt.

    Businesses actually care about this! They use ancient proprietary software that is critical to their business whose source code has long been lost to the sands of time.

    This isn’t a case that should be handled by FOSS developers, but by courts fining them for putting their employees, customers and business partners at risk! Running software that isn’t maintained by you or a third party is a liability.