
Hier ein Bild aus dem Jugoslawien vor den Kriegen der 90er.
Yugoslavia built in the early 80's abandoned for decades. Nature takes over.
Die Natur erobert sich die alte Kaderschmiede zurück.
Foto: 2015
#urbex #lostplace #farn #urbanexploring #jugoslawien #socialism
#abandoned #naturestrikesback #fotografie #photography #pixelfed


🔴 The place to Beat ✅
https://a7productions.blogspot.com/p/7-radio-100-mix.html
#World #Travel #Voyages #France #Photography #Music #Media #Live #Podcast #A7Radio #Radio #Streaming #Webradio #Paris #Mix #Dj #Social #Motivation #pixelfed


The Pixelfed developer blocked me yesterday because he probably didn't like my replies to his posts. I'm considering doing the same as you with my instance, but I've made plenty of donations to the project and invested a lot of time in setting up an instance for myself and family/friends and deleting it will be sad for me.
Since the import feature is buggy and don't work, I finally decided to import my photos to my Pixelfed account manually, which took me weeks. Then I decided to have my own instance, so I had to do the same twice. If I delete everything now to migrate my gallery to another platform, I will need to start from scratch again, since no platform accepts photos from another platform. Even worse, we're completely locked in to Pixelfed if we want to move, since we can't even export our own photos! How is that any better than using a Big Tech platform? Even Meta allows us to export our data. Instances hosted in Europe are at risk of breaching the GDPR because, if admins receive requests for a full data export, the current export tool doesn't work. Good luck to admins who don't know how to do it directly from the server!
Have you ever tried moving your followers to a different Pixelfed instance? I tried and lost all my social connections, as others have reported in GitHub issues. The followers and following from my original account were deleted and didn't transfer to the new account. I'm not the only one - other people have had the same problem. This bug is absurd and ruins the reputation of the Fediverse. It's the basic feature we all expect from the decentralisation promised by the Fediverse, it does not work, and nobody addresses it.
I avoided talking about Pixelfed's problems because I believed in the project and didn't want to denigrate it. I had a lot of love and hope for it, lots of patience and disliked anyone that criticized it. But the problems have gone too far and I saw most of them only after I created my own instance. Perhaps if we stop pretending that everything is OK, skilled people will decide to create alternatives. I would do it if I had the skills, time and energy (I don't). Many devs tried to fork Pixelfed to release a better thing, but it seems that it's really hard to make it run on local machines, documentation is outdated, there isn't an official Docker for it... in the end, #Pixelfed has a good marketing but does not deliver the basics.

#FediHeresy: went back to Flickr from #Pixelfed because:
→ Migrating from one instance to another didn't move posts, nor followers, both versions being identical (v0.12.6) and supporting those features.
→ The pictures/profiles are shown differently depending on which client/instance people are using, some not showing any at all.
→ Quite discouraging for an instance to have a bus factor of 1 and so far being unresponsive for months.
→ Not being able to replace a picture.
Sorry, but also, ugh.


