it’s nice and faster than woocommerce, main issue is that almost every extra feature is provided by a plugin that needs a subscription and i hate subscriptions, i prefer to get a permanent license and pay extra for a new version only if and when it’s actually updated

Thirty bees is a fork based on an ancient version of prestashop (1.6, released TEN years ago). While it’s much better than what prestashop was at the time of the fork, IMHO it’s better to go with prestashop 1.9 (now called 9) if you need any extra plug-in, as third party developers abandoned support for 1.6 a long time ago.

gdkchan? Who’s that person? My username is gdkchan2 but it’s purely a coincidence

Main hassle is to set up the disposable bank accounts in tax havens

as of now, nobody took the place of yuzu devs, for example

suyu (the most famous yuzu fork) got just 50 commits in the last 6 months and are almost all of them are tiny changes to the readme where they only change the discord link or just memes

Meanwhile, ai companies that are doing exactly the same are allowed to rack up billions in revenue.

“It’s American for profit corporation, not a Russian cybercriminal!”

Until now the stance was “rofl in Brazil C&Ds are a waste of money”, so the bribe option makes sense.

Suppose that they calculate $1 million in legal costs in order to take the case to a court, then offering something like $200k to delete the repo is a big saving.

The dev of simple mobile apps sold millions of users to an ad company for just $30k which was almost pennies if we think how popular those apps were in the Foss community

Now, backups of the code are widely available, will the development continue without the main dev? Suyu (fork of yuzu) made almost no progress since the fork

The dev got bribed (or threatened) by Nintendo to manually delete the repo. GitHub this time didn’t do anything

Fuck

It can be an easy target if they just take the betas and call them stable

I had a similar problem when using nginx proxy manager. In the end I just gave up and directly used cloudflare tunnels+cloudflare ssl

It was really weird to see the Pixel 9 launch with android 14. They have full control on os and the soc…

The QA testing for the OTA update for a new major version requires a lot of hours = it’s expensive

The new requirements make sense only if there’s the possibility to contact human support. Google unfortunately is run by bots

What about Publii?

WYSIWYG static site generator but personally I like to keep the content in markdown pages in a git repository so i can keep unlimited edit history; this saves everything in a local sqlite database.

Unfortunately the most powerful one that checks all the boxes, including automatic upload to s3 is hugo, but as you said the learning curve is high. Maybe try to see if you can run the example site of this theme, install hugo in your system, then go in the examplesite directory and run hugo serve. Slowly edit the files until you understand how it works.

I tried nextcloud photos for ten minutes and it looked like you can add photos to an album only at the moment of their creation. And you need to choose them one by one, don’t have “select all”. And you can’t select photos already uploaded in the past. What? Couldn’t think of a worse gallery than this.

Me too, just saying that encryption isn’t always a pro

Encryption in self hosted when you’re hosting only your personal data isn’t really a positive feature

For the case of ente, having all the photos in encrypted blobs in a minio container, means you have to export the content every night using their cli tool, verify it, repeat for every family member, then backup the result

Technical question, if it’s e2ee, it means videos can’t be transcoded? Modern smartphones encode video at a bitrate that doesn’t allow real time streaming on 4g

This is a photo gallery that can replace Google photos, while using nextcloud as a photo gallery is a proof of concept that can’t be even considered alpha quality

When on my personal install the music app was broken after an update for months, I didn’t complain at all. Because I went to see who was the maintainer: owncloud. Not their fault. In this case was my fault. Definitely my fault and without sarcasm. A third party plugin is expected to have problems after updates. Completely understandable. They’re even competitors.

First party plugins instead, MUST work at all times versus the latest stable release. It’s the reason I didn’t check compatibility.

This is the concept I want to say. It’s not hard. I’m not saying “the update process must be idiot proof”. When shit like this happens, it completely erodes trust in users. It’s not stable, it’s beta. It’s a tiny detail. It’s just a number on the manifest. What does it cost to update that number to 30 for the forms app? (The “incompatible” version runs perfectly fine when the check is overridden)

But no, let’s defend this behavior of moving fast and breaking things for no reason, like that issue thread on GitHub where users are rightfully pissed that the Windows nextcloud desktop client reboots without confirmation and fanboys are dismissing it “eh the cloud indicators in explorer.exe are so important, must reboot at all times, what’s the problem”

Do you agree that first party stuff must work? (unless it’s discontinued)

Would you expect Microsoft Office 365 being disabled after upgrading to Microsoft Windows 11?

And finally, how I persuaded the it department. Here I make a list of all the members:

We were just searching a way to host a worthless survey that nobody is watching instead of paying $350 to Surveymonkey. We drank the marketing cool aid and assumed that something heavily promoted just 6 months ago would be supported. But this is unreasonable.

Solution 1: waste a week doing your suggested way of multiple installs and custom unit tests and every quarter check carefully everything because nextcloud “stable” is as stable as a house of cards.

Solution 2: delete nextcloud and write a form in PHP+HTML in an afternoon, don’t have the same problem with nextcloud 31 next quarter.

Ok i get it, it’s best practice to do rushed releases without QA because users are the free testers.

They definitely had no way to know that their own app was incompatible, this is definitely a problem of the stupid user. Idiot user who believed their newsletter “update now, hub 9 is the best thing ever”. The user should have known that stable = untested beta

Also, this issue happened exclusively to me in the whole world, because everyone else isn’t an idiot like me and checks 30+ release notes scattered in 30 different repositories to guess any incompatibility. I was lazy and only checked the main notes! Such an idiot! Why I didn’t check every single installed app? It’s just 30! Nextcloud devs couldn’t have known that nextcloud devs didn’t update the manifest of the forms app! I should have checked before! Completely my fault!

Now if you excuse me I got an update to the Windows nextcloud desktop app and it must reboot after update because reasons even if there’s a GitHub issue with 200 angry comments about that. No wait! Stupid me! First I have to fire a VM and use a whole week to write automated tests that account for every possible combination of settings, language, power management, installed apps and so on. Otherwise I could lose a worthless survey that nobody reads and that will definitely get me fired!