bytepursuits

@bytepursuits@programming.dev

• ⁨Comment⁩ on ⁨opencloud - I migrated from nextcloud. Screenshots and docker-compose-compose.yml included⁩ ⁨⁨20⁩ ⁨hours⁩ ago⁩:

  Let people use whatever they want.

  you can do what you want

• ⁨Comment⁩ on ⁨opencloud - I migrated from nextcloud. Screenshots and docker-compose-compose.yml included⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  Nextcloud stopped being a fast, reliable file sync tool a long time ago.
  It’s become a bloated “groupware suite” full of Talk, Office, AI, and half-finished apps…
  while the core sync still chokes on large folders and locks files like it’s 2015.

  The Core Problem PHP-FPM and mod_php are ancient architectures - every request spins up, runs, and dies. No persistent memory, no connection reuse, and no async I/O. Result: slow sync, race conditions, and constant “file locked” errors. Tons of open GitHub issues about sync bugs, upgrades, and no action from nextcloud

  What they shoud do: Hyperf + Swoole
  Swoole turns PHP into a high-performance async server - persistent memory, connection pooling, non-blocking I/O.
  Hyperf+swoole can rival GOlang. Hyperf builds on it: native WebSockets, coroutine HTTP, and microservice-ready architecture. You get live sync, push notifications, and massive concurrency with a fraction of the resource cost. Add TUS (resumable uploads) and you finally have reliable file transfer on bad connections.

  I don’t want “Teams clone” bloat. We want reliable sync that just works. I’d rather self-host a lean, fast file system than manage ten half-integrated apps. Hyperf + Swoole is how you bring Dropbox-level sync to self-hosting without the pain.

  Nextcloud could fix its image by: Refocusing on sync reliability and performance. Moving core services to a persistent, async engine (Swoole/hyperf, etc). Making “Nextcloud Core” modular - separate entirely from the groupware/ai/talk - I dont fucking need it. Until then, those who care about speed, concurrency, and modern PHP should look beyond the old PHP-FPM world.

• ⁨Comment⁩ on ⁨opencloud - I migrated from nextcloud. Screenshots and docker-compose-compose.yml included⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  ohoh. thank you. wth I didnt realize I needed to explicitely tick english

• ⁨Comment⁩ on ⁨opencloud - I migrated from nextcloud. Screenshots and docker-compose-compose.yml included⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  and I would have gotten away with it if it wasnt for you meddling kids.
  NO - but seriously completely gratuitous from my end. I’m fed up with nextcloud.

  as to licensing - yeah I didnt even look at it, opencloud was forked from owncloud I figured it is something consistent. I like they use matrix for their chat.

  as to enshittification - that is something nobody can predict but I have seen GPL3 went private many times: directus.io/…/changing-our-license-one-year-later or mongo I think was agpl3.

  tbh yes - licensing is not something I looked into strongly.

• ⁨Comment⁩ on ⁨opencloud - I migrated from nextcloud. Screenshots and docker-compose-compose.yml included⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  I can see comments in the inbox, but not when I click on the post… weird. my client - I just use the browser.firefox. I also use voyager mobile app and similarly dont see comments.
  languages are set to “undetermined”.

• ⁨Comment⁩ on ⁨opencloud - I migrated from nextcloud. Screenshots and docker-compose-compose.yml included⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  How come I can’t see any comments? It says 17 but I can’t see them.

• opencloud - I migrated from nextcloud. Screenshots and docker-compose-compose.yml includedbytepursuits.com ↗
  Submitted ⁨⁨2⁩ ⁨days⁩ ago⁩ to ⁨selfhosted@lemmy.world⁩ | ⁨47⁩ ⁨comments⁩
• opencloud - I migrated from nextcloud. Screenshots and docker-compose-compose.yml includedbytepursuits.com ↗
  Submitted ⁨⁨2⁩ ⁨days⁩ ago⁩ to ⁨selfhosted@lemmy.world⁩ | ⁨0⁩ ⁨comments⁩