At first, absolutely. Very frustrating, kept feeling the pull back you-know-where. But then after a while, it became kind of a zen thing, if i’m using that word properly? It gives me time to breath a bit, rather than just doom scrolling at an increasing rate.
Maybe kind of part of the Lemmy Ritual? Maybe I’m strange.
I had this same problem. I kept changing it in my instance setting on the website and pulling my hair out that it didn’t take.
I eventually found there was a separate setting in my app. Not intuitive but I got there.
Look for the alternate settings. Mine wasn’t even in the main client settings, it was the per instance setting, but in the client.
Thanks Bot!! that was awesome.
I might violate your top “ideal solution” checkmark, but I have a raspberry pi running Motion Project (https://motion-project.github.io) on site and it makes an easily viewable webpage-stream. My Rpi4 can handle 2-3 video streams, with motion detect-video-save, periodic snapshot, etc. etc.
Not for the feint of heart, but it is the way I solved a very similar problem. I’m using random mixed brand of IP Cams, whatever was cheap at the time.
For what it’s worth, NFS in my experience is also faster. I had a very similar use case (but QNAP instead of Sinology) and switched everything over to NFS and saw performance gain. Little things like previewing IP Camera security footage would feel slow on SMB, but snappier on NFS. I’d gotten over the user thing, but the speed is why I switched.
I did eventually wipe QNAP’s software in favor of stock Debian – but the prevailing wisdom seems to say Sinology’s OS is pretty good.
I was wondering about this. What is the right etiquette? It’s not the same as multiple channels on the same server. But at the same time - supply side? Or consumption side?
Should clients filter them out? Do we need a way to “merge” on a per post basis?(or link or relate or…)
It is an interesting concept to ask. I don’t have a good answer.
lol. I love it.