• 46 Posts
  • 857 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle
  • 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.




  • Moonrise2473@feddit.ittoSelfhosted@lemmy.worldMozilla grants Ente $100k
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    13 hours ago

    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





  • 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!


  • go to watch who is the maintainer of nextcloud forms, then see if they could have known that NC 30 was about to go out or not

    It’s definitely not unreasonable that if I make product X and I make product Y, and they’re not compatible, then a bit of warning is suggested.

    Again, wordpress updates break plugins all the time, but automattic plugins (same people of wordpress) never break. Coincidence? They just launch a new wordpress without checking if woocommerce or jetpack don’t work?


  • I don’t know if maybe it’s my bad english in explaining it or it’s your comprehension skills that lack something.

    I write it again for the 10th time: I’m 100% ok having 1-2 weeks of downtime, and this is why i do it live. It simply doesn’t make sense to dedicate several hours every month on testing if all i need is getting 3 useless surveys filled per year. If it was essential for work and i needed 99.99999% uptime i would directly subscribe typeform or surveymonkey. If tomorrow my install completely bricks and disappears in thin air, i would have lost 30 minutes of time and no valuable data. I literally spent more time designing the logo for the instance than managing it. This is just to state how unimportant the data stored on it.

    This post wasn’t made about “oh no i lost millions and all my irreplaceable data thanks to nextcloud stupid updates” but how stupid is to release something that breaks features that they’re using as selling point.

    ok, now that we established that my IT skills are lacking and i should be fired because one single survey couldn’t be filled, this is the release notes: https://docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_30.html

    Please tell me where they say that this feature is automatically disabled and also tell me why you think that this is acceptable.

    I don’t understand why you think that is acceptable.

    I even can’t find other examples where a release is so rushed, that selling points are disabled without ETA. I never saw for Libreoffice 24 dropping support for opendocument files for a couple months just because they had to meet a self imposed deadline



  • You again commented on the docker upgrade comment that I said it’s irrelevant. It’s really like saying “if you wore pants that day, they wouldn’t have done that, it’s your fault”. It doesn’t make sense to spend $1000 in operating costs to host a useless survey that gets 3 responses a year. If it breaks for a week nobody dies.

    Focus on how they’re moving fast and breaking things, ok? It’s not normal that official plugins don’t support the latest stable release. It’s not an alpha, it’s not a beta, it’s stable. Stable means everything needs to work. Official plugins need to support the latest stable release. It’s acceptable only if this was a third party plugin made by a hobbyist in their free time

    WordPress updates also break many plugins but it never happened that a stable release blocked official ones like woocommerce.

    By the way, now I have learned that the latest version of nextcloud is a public beta and it’s better to always stay one version behind. So why don’t they call it public beta?


  • Us too, we only use it as a filelink provider for thunderbird and to host a useless survey that’s going to get filled once a quarter. That’s why nobody noticed the survey was disabled and that’s why we’re not doing multistage testing in multiple virtual machines. We are a super small company and ok with something that one day can be 3 days offline. Otherwise it would be cheaper to pay $100 to Surveymonkey and $100 to Dropbox


  • Manual docker upgrade issued my me after reading the official blog and newsletter. The upgrade notes described the new version as the best thing ever and didn’t mention that one of their selling points would be disabled without any notice.

    I’m starting to see a pattern in those comments like “why did you wear a skirt that night? It looks like you asked for it…”




  • Probably Google just wants to block them not because they care about the creators but because it’s costing them bandwidth money.

    From the new agreement that they had with warner bros for creating closed captions, it looks like Google is also stealing the subs for training, they had direct access

    It just sucks that someone pays hundreds of dollars to have a human create subs for a show, then that is used without credit or permission for training a model (actually whisper accidentally credits moments of silence with the name of the subbing groups used for training)


  • I’m not arguing that my procedure is right (it is not), I’m arguing that nextcloud rushed the release in an incredibly unprofessional way.

    When it’s the last time that Canonical, in the hurry to release Ubuntu xx.yy broke snapd without?

    When it’s the last time that Apple, in the hurry to release iOS xx, made it totally incompatible with iMovie and had no timeline on when it would be fixed?

    When it’s the last time that Microsoft pushed a Windows update that disabled Microsoft office and left it unfixed for months?

    Nextcloud decided to take care of the forms app. They decided to promote it as a selling point. They decided when to release the update. They decided to still push the update even if their own form app didn’t get any new release in 4 months and isn’t compatible.

    They aren’t contractually obligated to release a new, indistinguishable version (except some new bits that make it incompatible) every quarter.

    Not ready? Delay one week. Still not ready? Delay an additional week. It came out that it needs a complete rewrite and it will take months? Write a note in the blog saying that feature is no more a selling point but now it is deprecated/unmaintained/unsupported and it will be automatically disabled without confirmation.

    As someone said, a good app is only late until it ships, a bad app is bad until it’s patched. Why being perpetually bad with updates that nobody is asking?