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/

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.

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,

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,

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,

but one look at the face…

The old paper bag trick does wonders.

FutileRecipe,

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

Tried Kagi yet?

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,

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,

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,

I have like 5 years using Niagara and paying for it…

If you would’ve paid for the lifetime, you only pay once and it’s cheaper than annual once you hit 3+ years.

Yearly subscription: $9.99/9.99€/₹120 a year Lifetime purchase: $29.99/29.99€/₹360 (once)

Marketing Company Claims That It Actually Is Listening to Your Phone and Smart Speakers to Target Ads (www.404media.co)

A marketing team within media giant Cox Media Group (CMG) claims it has the capability to listen to ambient conversations of consumers through embedded microphones in smartphones, smart TVs, and other devices to gather data and use it to target ads, according to a review of CMG marketing materials by 404 Media and details from a...

FutileRecipe,

Except the device is already in your home, and most people leave their account logged in. That’s basically like you inviting someone into your house, they hang out in your spare bedroom…and they’re still there. So no need to re-grant consent to a situation that hasn’t changed. Unless you mean it auto-logs out (or you log out) and have to re-grant consent then? Most do require consent on logging in, and the average consumer would hate having to log in every time and would probably use weak passwords because of this.

But, you can at least kick them out (revoke consent).

I just don’t see how a proper law/regulation would fix/restrict this, except to make certain personalization attempts (targeted ads) illegal.

FutileRecipe,

They (manufacturer) would just put it in the ToS that the user grants them that access, because very few actually reads those and just hit Accept.

FutileRecipe, (edited )

Amazon’s logic is you paid a subsidized/cheaper price that is offset by included ads. You can buy it without ads (more expensive, obviously) from the start.

FutileRecipe,
  1. Blocking older known malware still blocks them, so that’s good (and saves bandwidth because the connection never happens, so this is really good).
  2. If the site is hijacked, it needs blocked till it’s unhijacked. So this is good as well.
  3. This is not really a point?

Number one above, stopping the connection before it happens, is really the best benefit, in my opinion. And if they boast a high false positive, you need better lists. You keep saying “they don’t block this or block that.” They are (nothing is) a one stop shop. Simply because they don’t block what you’re cherry picking does not make them bad. Use multiple layers. You say “don’t use a blocklist, use MS Defender instead.” Why not use both the blocklist, MS Defender, and even more stuff? Multiple layers. Defense in depth.

FutileRecipe,

tl;dr: Cut out Cloudfare’s recursive resolver (or anyone else’s) and run your own via PiHole and Unbound.

You don’t cut the middle man, you create the middle man with Unbound.

Umm, Unbound is on your machine. So you’re saying you are your own middle man lol…which is the same as cutting out the middle man as you (rather, your server) are you.

And Unbound needs to ask other DNS servers on the internet to resolve DNS queries.

It asks the authoritative nameservers, which is who external DNS servers ask. By using Unbound, you are cutting out those external DNS servers, because you/Unbound is the DNS server. You are asking the authoritative name server directly instead of inserting someone else to ask on your behalf.

Here’s an explanation by Cloudflare: A recursive resolver (also known as a DNS recursor) is the first stop in a DNS query. The recursive resolver acts as a middleman between a client and a DNS nameserver…Most Internet users use a recursive resolver provided by their ISP, but there are other options available; for example Cloudflare’s 1.1.1.1.

I copy/pasted the above quote from the article you linked. Again, Unbound (your machine) is asking the DNS nameserver. You’re saying you are your own middleman lol. I’m saying cut out Cloudfare’s recursive resolver and run your own via PiHole and Unbound. Did you read the article I linked?

FutileRecipe,

Which OpenTracks? Google PlayStore has two.

FutileRecipe,

So does mine (Voyager), and the misswipes is why I disabled it, which thankfully Voyagers allows to be configurable.

FutileRecipe,

The only time I can think of when it actually made sense for the story…

Never watched I Now Pronounce You Chuck and Larry?

FutileRecipe,

Assuming they’re talking about what most businesses, especially large ones with huge legal resources, do: exploit loopholes to not pay, or pay reduced, taxes.

FutileRecipe,

It’s been my experience that for most people, Google services are not a requirement, but a luxury… especially for daily life. Now, most Google-esque services are a requirement for daily life, but as they said, there are alternatives that you can use that work.

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