Biology, gaming handhelds, meditation and copious amounts of caffeine.

  • 0 Posts
  • 5 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle

  • I recommend using this: https://github.com/TheLastGimbus/GooglePhotosTakeoutHelper

    A couple years ago, Google decided that instead of exporting the photos with EXIF data exactly as you’ve uploaded them, which was the original behavior and how platforms such as OneDrive do it, they are going to completely delete all EXIF from the image and instead also create a .json containing the original data, in a non-standard format. This script is an open and free version of a paid tool that goes through each image, finds the corresponding .json, and puts the EXIF data back on.

    If you don’t do that, when you reupload these photos into a new service, the date will be reverted to the day you’ve downloaded them and location data will be missing entirely.




  • I think users are still having trouble with the mental model for browsing Lemmy.

    The first interaction with the service is already fragmented - you need to choose where to create an account and start browsing. Even though you can browse communities from other servers, people are now seeing them through the lens of “fragmented” “my server vs other server” and that creates the illusion that these duplicates are somehow a huge issue.

    But duplicates can actually be quite useful - a community called “memes” on Lemmy.world could attend to a different audience than a community also called “Memes” but made in an instance entirely in French.

    Also, if two instances have two communities you enjoy, with the same name… Subscribe to both? Nothing stops you from doing that. It’s okay. Reddit had “me_irl” and “meirl” which were the exact same, but with different mods, a relatively similar number of subscribers and quite honestly the same content. I didn’t know the actual difference between the two, and I still do not know - I just subscribed to both and kept getting depressing memes to cry before going to sleep. No issues.


  • As much as I disagree with some of them, I recall the folks at the Accidental Tech Podcast spent a good while on this very discussion back when people were migrating from Twitter to Mastodon, and they had some interesting concerns and conclusions.

    The answer is yes, in many places the admin hosting the content could be responsible for the content. Where I live I believe they would have to provide user data about who made the post, and if they refuse, they become the responsible party.