FutileRecipe

@FutileRecipe@lemmy.world

This profile is from a federated server and may be incomplete. Browse more on the original instance.

FutileRecipe,

There are three big reasons why we’re removing SMS support for the Android app now: prioritizing security and privacy, ensuring people aren’t hit with unexpected messaging bills, and creating a clear and intelligible user experience for anyone sending messages on Signal.

To me, all of those reasons are BS and easily gotten around. “Unexpected messaging bills?” Have a popup that warns you that this user doesn’t have an account and is about to send a SMS, potentially incurring a cost, as an example.

They just didn’t want to maintain the code and chased some users away. www.signal.org/blog/sms-removal-android/

Why you shouldn't use a SIM card and use an hotspot as an alternative (piped.video)

The video discusses the privacy concerns associated with SIM cards in mobile phones, highlighting three main reasons to be cautious. First, it explains how SIM cards enable constant location tracking through communication with cell towers. Second, it delves into the autonomy of SIM cards, particularly proactive SIMs that can...

FutileRecipe,

You know landlines are still in use, right?

Mine didn’t work so well when I left the house.

FutileRecipe,

I’m not sure why people insist on F-Droid, considering the F-Droid Security Issues.

FutileRecipe,

Part of what I value in F-Droid is the additional layer in the build/release process, because it makes tampering more likely to be detected.

Barely and not really. “F-Droid can’t ensure the apps are safe. You still need to trust the upstream developers. We only do some basic check.” forum.f-droid.org/t/…/2

FutileRecipe,

N + X - Y ? N

Except now you’re adding an additional party to trust (the -Y). So it could still be considered less secure than N.

FutileRecipe,

that scare piece you linked would have the reader believe

So an indepth and critical analysis of something is now a “scare piece?” Ok.

FutileRecipe,

Depends on the particulars, and on the needs of the individual.

That’s not really how things like security works. It’s either more secure or it’s not. The security of a thing does not depend on needs. Now, does the application of it or does someone need it to be more secure? That’s where risk acceptance and the needs of the individual come into play.

I’m not going around presuming to tell other people what’s better for them, as one or two others in this thread are doing.

Same. I’m not saying “stop doing this.” I’m just trying to educate people and make sure they’re not operating with a misunderstanding. Needs of the individual and all that. I think some people just go crazy for something that’s not big tech, and then quit looking at the particulars.

FutileRecipe, (edited )

If that were true, threat modeling wouldn’t exist.

I feel like we’re talking about different things. I’m talking about static concepts, if X is more secure than Y, not individual setups where something is tweaked. Threat modeling is tailoring the security to your needs. It doesn’t bend security of a static object or make the application of something less than what it is. It requires one’s actions to do that by not utilizing it.

Take bullet proof glass, for example. Bullet proof glass is more secure than regular glass. Now, do you need (does your threat model require) bullet proof glass? No? Ok, that doesn’t mean bullet proof is now less secure than regular glass, it’s just unneeded.

FutileRecipe, (edited )

I guess people just started to realise that mini x86s exist too

People always knew x86s existed. I think the main culprit is the price gap between them and Pis is decreasing. Pis used to be around $35, which has skyrocketed to 3-5x MSRP, plus they were unavailable for a long time. Now the Pi’s performance to price ratio isn’t justifiable to most, so people pay a little more for the x86 but get so much more capability.

Privacy Concerns on Lemmy: A Call for More User Control (github.com)

I’ve been grappling with a concern that I believe many of us share: the lack of privacy controls on Lemmy. As it stands, our profiles are public, and all our posts and comments are visible to anyone who cares to look. I don’t even care about privacy all that much, but this level of transparency feels to me akin to sharing my...

FutileRecipe,

All your data will pass over other hardware owned by other people. The only real online privacy is not connecting to the internet to begin with.

And now we’re entering into the realm of encryption, especially end-to-end. Generally speaking, just because you’re sending information that touches other people’s hardware, doesn’t mean it’s public and readable.

what are your recommendations for a good privacy friendly sms app?

Hello, currently I use qksms but its very problematic and lacks basic fetures. One of those issues being you cant send videos, and sending and recieving media is pixalated or blurry because of a commpresion issue. I’ve already tried adjusting the compresion options in settings to find out it doesn’t work....

FutileRecipe,

Since SMS is already sent in the clear, I actually use Google Messages. For those who also have it, it upgrades the SMS to RCS with end-to-end encryption. Sure, it’s nowhere near as good as Signal (which OP says these people won’t use), but it’s better than plain-text SMS.

How RCS chats keep your conversations secure

FutileRecipe,

I was gonna say air filter.

FutileRecipe,

Specifically, the plug-ins are using our services in an unauthorized manner, which is causing significant economic harm to our Company.

How does this cause them “significant economic harm?” My immediate thought is they are losing out on data or ads, hence it being a privacy concern.

FutileRecipe,

Its a 5-year old product. With 5 year old specs.

It’s a Pi. Cutting edge (or even modern or high end) specs have never been it’s selling point or goal.

FutileRecipe, (edited )

Sensors permission toggle: disallow access to all other sensors not covered by existing Android permissions (Camera, Microphone, Body Sensors, Activity Recognition) including an accelerometer, gyroscope, compass, barometer, thermometer and any other sensors present on a given device.

FutileRecipe,

I just checked Lineage OS and it looks like Google Play Services doesn’t let you disable sensors permission. Can you do it on Graphene OS?

Yep, there’s a toggle to disable by default globally. I also individually checked Google Play Services, Google Play Store and Google Services Framework, and all three can be denied the Sensors permission.

This is due to Sandboxed Google Play: “GrapheneOS has a compatibility layer providing the option to install and use the official releases of Google Play in the standard app sandbox. Google Play receives absolutely no special access or privileges on GrapheneOS as opposed to bypassing the app sandbox and receiving a massive amount of highly privileged access. Instead, the compatibility layer teaches it how to work within the full app sandbox.”

FutileRecipe,

“There are no seeding rules…if you fall below a 0.5 ratio, your downloads will be disabled.”

That there sounds like a seeding rule.

FutileRecipe,

but one look at the face…

The old paper bag trick does wonders.

FutileRecipe,

the ground should absolutely be on the bottom because gravity.

Not necessarily. You typically want the ground longer so it’s the first in and last out. Type G has the ground on top. I vaguely remember hearing that’s because if it comes slightly out and something sharp or metal falls on the plug, you want it to hit the ground and not the live part…but I don’t know how reliable that story is.

FutileRecipe,

now that Google’s search engine has gone down in a bullshit flaming AI crapshoot

Tried Kagi yet?

FutileRecipe,

It’s just hardware. Almost any device can act as your router if you put the proper OS and/or software on it.

I have started using fedora silverblue

Today, I made switch to fedora silverblue and then rebased to ublue image because it has flatpak included in the image. I am also thinking about making my own image based on silverblue. there is a video made by bigpod a youtuber about how to make your own custom ublue image and I learned a lot from that video. I am using toolbox...

FutileRecipe,

Yeah, I’m not saying it’s hard, just illogical. To me, it came across similar as: “I’m moving to this other distro because they have Firefox.” Your current distro also has Firefox, so why are you moving again?

FutileRecipe,

then rebased to ublue image because it has flatpak included in the image.

From Silverblue’s Getting Started Guide:

Flatpak is the primary way that apps can be installed on Fedora Silverblue (for more information, see flatpak.org). Flatpak works out of the box in Fedora Silverblue…

Just seems very odd to distrohop for one main reason (flatpak in this scenario), without even checking if that reason is available in your current distro…which it is, out of the box.

FutileRecipe,

Lawnchair, according to the devs, is not abandoned. In late November (of 2023), they said:

Sorry for the long break in Lawnchair announcements.

We have made significant progress in regards to Lawnchair development, and we are now actually developing Lawnchair 13 (with A13 QuickSwitch support) and custom-made no-root global search. Stay tuned for more updates and sneak peeks.

Coming soon to a lawnmower near you™

(And no, we are not dead. Also No ETAs.)

Then in December:

Hello again!

This time around, we are now developing Lawnchair 14 (with A14 QuickSwitch support). Alongside that, we are also re-adding an option to Hide Dock and options for custom Feed Providers, alongside other new features (we wont give too many spoilers 👀)

We also plan to support QuickSwitch for Android 11 to Android 14, so you can use Lawnchair with QuickSwitch on all your recent devices. (We will prioritize A12.1 to A14 first though).

(As always, No ETAs)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • localhost
  • All magazines
    •
    Loading…
    Loading the web debug toolbar…
    Attempt #