this is from statcounter.
I mean - I like the numbers, but I doubt their validity:
https://gs.statcounter.com/os-market-share/desktop/worldwide/#monthly-200901-202608

257
8
1675
submitted 1 day ago* (last edited 6 hours ago) by bytepursuits@programming.dev to c/linux@lemmy.world
301
2
25

Omada platform was found to be vulnerable in several ways

26

Omada platform was found to be vulnerable in several ways

[-] bytepursuits@programming.dev 6 points 5 months ago

Opencloud instead of nextcloud

[-] bytepursuits@programming.dev 8 points 6 months ago

Would absolutely advise against telegram. They have your phone number and you have 0 privacy. There is 0 support. If you are banned - there is nowhere to file complaint and you just lose all your contacts.

[-] bytepursuits@programming.dev 6 points 6 months ago* (last edited 6 months ago)

Tied to your phone number. Cannot use without phone number - result is automatic 0 privacy.
Another issue - there is absolutely 0 recourse if they ban you, there is no support you can email, there Is absolutely nothing. So if you have a family group there and telegram banned you - you are out of options entirely other than switching phone number and device.
Don't touch that garbage platform with a 60ft pole.

[-] bytepursuits@programming.dev 20 points 6 months ago

Whatever you do - don't use telegram.

[-] bytepursuits@programming.dev 9 points 7 months ago

They said they still adding all of it. They are adding ai. Just not talking about it. Which is probably correct 😂

[-] bytepursuits@programming.dev 20 points 9 months ago* (last edited 9 months ago)

I'm sorry - I understand it's free, but this is how I feel:

Nextcloud stopped being a fast, reliable file sync tool a long time ago (I mean - was it ever? it's free thats why most people use it).
It’s become a bloated “groupware suite” full of useless Talk, Groupware, 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, no coroutines, slow as molasses non scalable backend held together only with redis.
Result: slow UI, slow sync, race conditions, and constant errors. Tons of open GitHub issues about sync bugs, upgrades, and no action from nextcloud. I'm sick of it. I'm done with it and I will be very direct about it.

Comments and issues and proposed classical PHP solutions are shocking:

https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html#configuring-your-web-server Nextcloud suggests you up its ram to 16Gb. 16Gb Carl!

php_value upload_max_filesize 16G
php_value post_max_size 16G

What about 17Gb files Nextcloud? nogo? don't use nextcloud then? Have you ever heard of TUS?

opencloud can run circles around nextcloud now - it is written in GO, much better architecturally, long running, uses connection pooling, does not need redis to survive.

What they (nextcloud) should 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 bloat. I want reliable sync that just works. I’d rather self-host a lean, fast sync app than manage ten half-integrated apps. They need to switch to Hyperf + Swoole - and 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 don't fucking need it. Until then, those who care about speed, concurrency, and modern PHP should look beyond the old PHP-FPM world.

Im not the only person - people are sick of this inaction:

[-] bytepursuits@programming.dev 5 points 9 months ago

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

[-] bytepursuits@programming.dev 12 points 9 months 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: https://directus.io/blog/changing-our-license-one-year-later or mongo I think was agpl3.

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

[-] bytepursuits@programming.dev 7 points 9 months ago

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

158
submitted 10 months ago* (last edited 9 months ago) by bytepursuits@programming.dev to c/selfhosted@lemmy.world

Hey friends. I finally fired nextcloud - and so should you.

edit: wow. reddit banned me for posting a link to my (completely unmonitezed, unproductized) blog in multiple r/selfhosted threads. I bet it's related to this lemmy link

5

Setting up xdebug with swoole could be a bit of a hustle especially if application is containerized and you are running swoole and xdebug in a docker container with IDE on the host.

Here’s what worked for me.

Here I’m using hyperf framework, but I think issues and instructions should be similar for other swoole based frameworks (mezzio, resonance etc). Swoole 5.0.1 + PHP 8.1 natively support xdebug.

22

Do you guys already use css @layer in your code? just curious.
Do you deem a level of adoption sufficient?

https://caniuse.com/mdn-css_at-rules_layer

view more: next ›

bytepursuits

0 post score
0 comment score
joined 11 months ago