bytepursuits

@[email protected]

This profile is from a federated server and may be incomplete. View on remote instance

bytepursuits ,

Good point about critical mass. It doesn't need to take 50%.
You know, and the fact that windows is not as gateable as mobile platforms. There are 2-3 reasonable alternatives so it's much harder to stop the bleed. I wish we had alternatives on mobile

bytepursuits ,

On my websites I see 90-95 percents mobile traffic. There is just no desktop usage anymore.
Since Ms lost mobile game , - I can only imagine they are loosing badly now as Linux can absolute easily replace it. Can't wait for oems shipping it.

bytepursuits ,

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 ,

Nope. Never use telegram.
You can get banned out of the blue and just lose all the contacts.

Never touching that

bytepursuits ,

Whatever you do - don't use telegram.

bytepursuits ,

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 ,

I use signal. It's not bad

bytepursuits ,

Why? Show is great.

bytepursuits ,

I use xeoma.
It's not open source, but I honestly could not find any decent open source Linux NVR.

https://bytepursuits.com/xeoma-linux-nvr

bytepursuits ,

Share some pictures and stats of you could.
Do u see many probes?

bytepursuits ,

Opencloud

bytepursuits ,

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

bytepursuits OP ,

I think apps ATM are a bit raw. My android app - while it works, it sometimes takes time to sync it up. But eventually it syncs it up

bytepursuits OP ,

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

bytepursuits OP ,

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".

bytepursuits OP ,

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 OP ,

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

bytepursuits OP , (edited )

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:
https://programming.dev/pictrs/image/7eec9093-259e-4f92-8fcb-ae681b7e9402.png

bytepursuits OP ,

Let people use whatever they want.

you can do what you want

bytepursuits OP , (edited )

I think it really helps if you dont like !important:

@layer base, toggles;
@layer toggles {
    .wprm-print-hide-recipe-nutrition .wprm-recipe-nutrition-label-section {
        display: none;
    }
}

instead of

.wprm-print-hide-recipe-nutrition .wprm-recipe-nutrition-label-section {
    display: none !important;
}

I guess I answered my own question - I think its a neat feature and ill use it.