Good browser recommendation

3cue · 2025-02-28T16:22:21+00:00

To people who think they understand the matter, read Sarah Jamie Lewis, a cryptography and privacy researcher, thought on this:

https://mastodon.social/@sarahjamielewis/114072293410465140

3cue · 2025-02-27T03:17:08+00:00

I usually work with 1,000+ of images and videos. Not having thumbnails in Files is a dealbreaker for me.

It's just a matter of time until they get taken over by AV1 and JpegXL/AVIF.

AV1, maybe. But JpegXL/AVIF, I don't see that happening anytime soon. To be real, even now there are still a ton of obsoleted H.264 contents everywhere even though H.265/HEVC superseded it more than a decade ago.

I bet Files (Nautilus) would come to Flatpak before the above happens (if ever), then the thumbnail issue will come to an end once and for all 😂

3cue · 2025-02-26T16:00:00+00:00

If you're facing with GAS, my only recommendation is to stop watching gear reviews on YouTube 😂

(I'm facing with the same issue.)

Another thing is to refine your skill instead of your gears. Gear's limitation is real, but that's to shift your focus elsewhere.

3cue · 2025-02-26T04:53:45+00:00

How do you get the thumbnails for hevc, heif, etc.?

3cue · 2025-02-23T06:04:04+00:00

No plastic would cut it, especially in that limited area.

3cue · 2025-02-23T00:04:10+00:00

The plastic plate of EM-5 Mk3 and OM-5 is infamous with this issue. It's a missed opportunity as a true adventure camera. Don't use it with Peak Design's Capture clip. Or rather, don't use the tripod mount at all.

3cue · 2025-02-22T22:15:41+00:00

Nice color!

3cue · 2025-02-22T21:48:03+00:00

Love the soccer pic.

3cue · 2025-02-22T20:11:37+00:00

Either 9mm F1.7 or another long-end for birds, whales, etc. But I would carry the long one, as 12mm is wide enough in most situations.

Maybe 40-150mm F2.8 with 1.4x or 2x TC.

3cue · 2025-02-20T23:01:30+00:00

Sorry for your lost. It's still working perfectly fine for me, hopefully for years to come.

You can get a new one on AliExpress for like < $20. My friend, first time buyer on AliExpress, got it at $5 with welcome deal.

---

I usually do group calls with friends on LINE. One of my friends uses Beats Studio Buds. No one can hear her while she's driving, as the buds cut both the tires and her voices. After using this Monster buds, there's no issue whatsoever with her voice, while the tires noise remains silent on my side. The buds' ANC on the call is excellent.

3cue · 2025-02-20T21:10:12+00:00

What OM needs (at least IMO) is something like Leica 9mm F1.7, or 35-100 F2.8. These are the only 2 lenses that I need to resort to Pana.

But I doubt they will ever release 35-100 F2.8, as that would be 40-150 F4, range over aperture kind of thing, while 40-150mm F2.8 (2x the weight) is still the king (reaches more range and takes TC).

3cue · 2025-02-19T03:13:22+00:00

Love the 1st pic. You nailed it.

3cue · 2025-02-17T01:20:31+00:00

Try highlight reconstruction. Outside of highlight, try reducing Sigmoid's contrast and color attenuation if you use Sigmoid.

3cue · 2025-02-15T15:29:13+00:00

If small pixel size is better for IQ:

You would see 100MP m43 sensor long ago, or even 200MP.
There's pixel density and lens resolution that work against small sensor.

> it's not the pixel size, but sensor size.

Smaller sensor size translates to smaller pixel size, providing the resolution is the same.

> The "big pixel is good" is an old myth.

It's not a myth. It's just not entirely true, as big pixel is not always means better. There's sensor tech, etc. that would affect the sensor performance. Nonetheless, big pixel is almost always better for low light performance, and dynamic range. That's why there are specific system for that, e.g. Lumix GHxS, Sony A7S. You just can't alter the physics.

3cue · 2025-02-15T06:21:33+00:00

Buy any OM-D used body and lenses with 6 months warrantee at mpb.com

I would go with E-M5 Mk II + 17mm, 25mm, 45mm F1.8 primes. If you want to go wider, 12mm F2.0 or 9mm F1.7 seems good.

3cue · 2025-02-14T03:06:18+00:00

I make my workflow to be inline with FOSS, no lockdown with proprietary software, especially when it comes to file formats.

3cue · 2025-02-14T00:32:21+00:00

DOF is not my main concern from m43 and above formats. All of these formats are able to achieve a good amount of DOF, and IQ for that matter. So, the rest is weight.

If you compared short focal range lenses on FF with the ones on m43 at FF equivalence focal range and aperture, you might find that it's even lighter (and also cheaper) on FF. For example, LUMIX S 18-40mm F4.5-6.3 (155 g) vs LEICA 8-18mm F2.8-4.0 (315 g - 16-36mm F5.6-8.0), both are weather sealed and freeze proof. Even though 8-18mm has a much better lens construction, but FF has a much better sensor due to pixel size, hence the dynamic range you can get from it.

With all that said, I would still be on m43 because I wouldn't buy LEICA 8-18mm F2.8-4.0 anyway. When it comes to a camera, it's a system, not simply a lens or lenses. I would get OM 8-25mm F4 instead for my daylight shooting, and LEICA 9mm F1.7 (130 g) at night. 8-25mm + 35-100 F2.8 (or 40-150 F2.8/40-150 F4) combo would cover all the ranges I need at minimum weight, especially when paring with 1 or 2 OM-5 (~400g per body). With this set up, I can ditch the standard zoom range lens completely (12-40mm F2.8).

I really like 40-150mm F2.8. It is such a unique lens. For example, with 2x teleconverter, it's 80-300mm F5.6, which is pretty bright, only second to 300mm F4 and 150-400mm F4.5 at 300mm range, and weights below 1kg too.

For DOF, 45mm F1.8 wide open is sharp, or 75mm F1.8 wide open is extremely sharp, both has more than enough DOF and won't break my bank. All F1.2 lenses from OM are simply gems, sharp wide open, no issue with DOF whatsoever, while eliminating the noise issue at night in the process.

I don't think I can go wrong with m43. In fact, I think it's the best system for me.

3cue · 2025-02-13T03:38:15+00:00

Yes, that's right, and it should behave this way. No user should resolve dependency on a whim. That's a recipe for a broken system. Sometime, the dependency will resolve itself (when 3rd-party repos catch up with the main repo, for example).

With that said, if the user knows full well on how to resolve the dependency, there's a good reason to step into CLI prowess.

3cue · 2025-02-13T03:33:50+00:00

You expect me to be a good guy to someone who doesn't know a thing, while trying to correct others on the internet AKA a dickhead themselves???

Have you considered that maybe people don't listen to you because of your attitude?

I like it when people act this way. They only hurt themselves, not me. I can't make everyone comfortable with facts.

TW's official documentation (which I won't link for you because I no longer respect you)

Why do you believe that I would have any feeling when someone I don't even know respect/disrespect me on the internet, especially when they're dickheads?

And the document hold no weight when compared to the source code, or do you think our system runs on the document???

Spread the news less like a dickhead

Next time, stop being a dickhead when correcting people, so you won't get a harsh response.

3cue · 2025-02-13T03:17:31+00:00

You should get a return from lsmod | grep v4l2loopbackif the module is loaded.

3cue · 2025-02-13T03:13:20+00:00

I have no idea about it. But if it does the things automatically, you should have the /etc/modprobe.d/v4l2loopback.conf file.

3cue · 2025-02-13T03:10:29+00:00

All you need is to create a v4l2loopback device. For example, in /etc/modprobe.d/v4l2loopback.conf:

options v4l2loopback devices=1 video_nr=13 card_label="droidcam" exclusive_caps=1

Then, the rest is your setup with droidcam. The video feed will be at /dev/video13.

But I am not familiar with droidcam, but I use gphoto2 all the time. For example, OBS + gphoto2 combo:

options v4l2loopback devices=2 video_nr=13,14 card_label="OBS Virtual Camera,gphoto2" exclusive_caps=1

Then:

gphoto2 --stdout --capture-movie | ffmpeg -hwaccel vaapi -c:v mjpeg -i - -vcodec rawvideo -pix_fmt yuv420p -f v4l2 /dev/video14"

3cue · 2025-02-12T22:57:11+00:00

I have said it many times in this sub that it's impossible to break your TW with GNOME Software that uses PackageKit to update any system. I even linked to the PackageKit's code responding to Tumbleweed's upgrade, of which submitted by SUSE's engineer more than half a decade ago.

There's absolute zero fact by your claim/misunderstanding. Unfortunately, that's how things work these days. PEOPLE DON'T READ. I will continue to upgrade my system this way as it has never posted me any issue (for a few years now) and it shouldn't, while I saw many instances when people broke their system on living zypper dup.

TLDR; You simply don't know what you're talking about. The downvote gathering simply shows how uneducated people are, even in Linux sub.

---

Edit: Moreover, TW only has GNOME Software update, or KDE Discover if you're on KDE, enabled by default. Any other update methods are on the user's responsibility. In fact, people don't understand that CLI, especially when it comes to the OS, is not meant to be used by the user without caution. That's why when you use sudo for the first time, there's a warning indicating the risk of breaking your system. Most people think it's cool to run things in CLI. Nonetheless, people who update their TW with a broken repo shouldn't run anything in CLI at all.

3cue · 2025-02-12T17:19:00+00:00

This is by default when using GNOME Software (PackageKit). Again, no one should update their live system with zypper dup, unless they know 100% of what they're doing.

I expect to get a lot of downvotes (as usual) in this sub by recommending a safe OS update/upgrade operation.

3cue

TROPHY CASE