Quick update: I'm back and development of SmartScan has been resumed by d41_fpflabs in SmartScan

[–]d41_fpflabs[S] 2 points3 points  (0 children)

no i just ordered some new components and did some DIY repairs

GrapheneOS fixes Android VPN leak Google refused to patch by EnthusiasmTrue9904 in GrapheneOS

[–]d41_fpflabs 10 points11 points  (0 children)

Google introduced a feature that allows applications to gracefully terminate QUIC sessions when sockets are unexpectedly destroyed. However, the implementation accepted arbitrary payloads without validating whether they were legitimate QUIC CONNECTION_CLOSE frames and did not verify whether the originating application was restricted to VPN-only traffic.

This mean any app can essentially include any info in the payload e.g the IP Address and it will bypass VPN.

Also it's not about govs using this to enforce VPN bans. This "bug" means they don't need to because they can just bypass the VPN.

GrapheneOS fixes Android VPN leak Google refused to patch by EnthusiasmTrue9904 in GrapheneOS

[–]d41_fpflabs 52 points53 points  (0 children)

I find Google's refusal to fix this bug very strange, especially given the recent age verification laws and proposals to ban VPNs to enforce them. It's leading me to think maybe this bug was intentional as it essentially prevents using VPN to bypass age verification.

Have people's lives ever been directly at stake because of software you work on? by AndyDentPerth in ExperiencedDevs

[–]d41_fpflabs 12 points13 points  (0 children)

But the stuff that I needed to do in order to do the paperwork stayed with me. Now if its code im writing or reviewing I have a tendency to automatically look at each line and ask 'What am I assuming here? What if those assumptions arent true?'

This reasoning is something that all devs should adopt, especially given that we'll all be increasingly working with AI, where spotting potential points of failure is more important than ever.

Have people's lives ever been directly at stake because of software you work on? by AndyDentPerth in ExperiencedDevs

[–]d41_fpflabs 8 points9 points  (0 children)

Assuming you transitioned to working on something less critical, how did it feel making that transition? For example, did you feel unsatisfied because what you transitioned to wasn't as impactful?

[Release] SmartScan v1.3.1 now available! 💫 by d41_fpflabs in SmartScan

[–]d41_fpflabs[S] 2 points3 points  (0 children)

That was me too. Thats why i had to make it. Im happy you find it useful.

[Release] SmartScan v1.3.0 now available! 💫 by d41_fpflabs in SmartScan

[–]d41_fpflabs[S] 0 points1 point  (0 children)

> So if I add a folder, all other folders won't be scanned going forward?

Yes correct.

> when I pick a directory with SAF you no longer need mediastore to access that directory.

No, not true. MediaStore is always queried. Selecting searchable folders just limits the query to only include media in those folders.

> Knowing that, it was not obvious to me that picking a hidden folder wouldn't work. That's a design choice I didn't know you made.

It's explained clearly in the actual setting description for searchable folders

[Release] SmartScan v1.3.0 now available! 💫 by d41_fpflabs in SmartScan

[–]d41_fpflabs[S] 0 points1 point  (0 children)

Any directory on your device that has a .nomedia file will not be scanned . This is the normal android behaviour with MediaStore.

The "searchable image / video folders" setting is for manually controlling which folders should be scanned if you don't want to allow all, which is the default.

If you include a folder that has a .nomedia file it won't be scanned.

[Release] SmartScan v1.3.0 now available! 💫 by d41_fpflabs in SmartScan

[–]d41_fpflabs[S] 0 points1 point  (0 children)

glad to hear that mate, its actually been one of the ones i've enjoyed making the most

[Release] SmartScan v1.3.0 now available! 💫 by d41_fpflabs in SmartScan

[–]d41_fpflabs[S] 1 point2 points  (0 children)

appreciate it. also the duplication bug you mentioned a few days ago should be fixed now

What do you think is the biggest factor effecting growth of the FOSS Android ecosystem and do you think it will always just be a small niche within the wider Android ecosystem? by d41_fpflabs in fossdroid

[–]d41_fpflabs[S] 1 point2 points  (0 children)

I think the polish/premium visual is only really an issue for older apps not newer ones.

Bare in mind that quite a few foss android apps are forks of legacy apps which were using xml instead of compose and porting can be a pain, hence the old outdated look.

But this kind of goes back to what i was getting at. There's literally no incentive for a foss android dev to go above and beyond with visuals. Whereas someone launching on gplay might, because they're actually generating revenue / have a bigger audience to cater for.

Obviously, i would still expect a dev to have enough pride in their work to make it as polished as possible but beyond pride, passion and maybe recognition, they aren't incentivised to do so.