• 239 Posts
  • 391 Comments
Joined 3 years ago
cake
Cake day: July 30th, 2023

help-circle





  • Whether it’s a good idea to present the DL to ICE depends on whether there is a legal obligation to do so – hence the question about jurisdiction.

    If you legally must present a state DL on-demand to feds, then it’s a question of consequences. Refusing to present your DL to a local cop who pulls you over could probably lead to legit confiscation (effectively, loss of driving privs). If the feds take your DL and it’s unlawful, then the confiscation has no legal effect because you are still licensed to drive. You would just have the inconvenience of reporting a stolen ID to the DMV and waiting for a replacement.

    One legal theory I would like answered is if you can refuse the DL to feds, then would they have to call a local cop to demand your DL by proxy in the scenario of following a legal procedure? This could be interesting because local cops may not be happy to respond to such calls.





  • PM’s apps perform the encryption on your own device because it’s your device that runs the apps. That is e2ee, but still only in the two scenarios I mention and even then it’s also vulnerable to targeted attack. PM could ship malcious j/s if it wanted (the likely case being to comply with a court order). It’s better if your own non-j/s FOSS MUA handles the crypto, which is actually easier if you don’t use PM.

    If mailbox.org works the way anonaddy works, then that’s not e2ee. The msg payload is seen by the server that does the encryption, in the very least. The sender’s ESP would have already seen the msg.



  • This page covers CF as a walled garden generally:

    https://thefreeworld.noblogs.org/post/2024/03/18/cloudflare-has-created-the-largest-most-rigidly-exclusive-walled-garden-in-the-world/

    W.r.t the fedi, Cloudflare blocks Tor and VPNs by default. So if you wanted to run your own Lemmy node, it would be unable to federate to Cloudflare nodes over Tor or VPNs. Lemmy end users are also oppressed by CF because images come from the source and are not cached. So if someone posts an image on a CF node and I use Tor to connect to slrpnk.net, I can only see the text and not the pics.

    Users of CF nodes tend to be ignorant about the exclusivity of many clearnet sites, so they often unwittingly post links to tor-hostile sites.

    Are you talking about a pure matter of size?

    That too. The fedi is designed to make decentralisation /possible/. But obvisouly if network effect causes a majority of people to pile onto a single host, that’s not decentralised. Lemmy was not designed to be smart about this.

    There are several node operators who do not give a shit about decentralisation or the balance that that requires. They just want to have a disproportionate amount of power over users so they can control the narrative through selective censorship. So they grow nodes that are obscenely large. Lemmy World goes to the extreme of using Cloudflare to circumvent the natural control of resource limitations, to grow out of control.

    Some non-CF nodes also don’t know when to quit new registrations. I track them by calculating the average node size. If a node has more than 2 standard deviations above the avg number of users, I consider them centralised and avoid posting in their communities, just as I avoid posting in Cloudflare’s walled garden.


  • Consider self-hosting HALF the service. Something like this:

    Outbound

    local Postfix on dynamic IP → relay (optional and configurable) → recipient

    You can configure Postfix to use a relay depending on the recipient. E.g. if you need to reach alice@outlook.com, MS will reject your dynamic IP. But if you have bob@outlook.com, you can tell Postfix to relay via MS servers using your bob@outlook.com account for all *@outlook.com recipients. And yes, you can still use a different vanity address in the FROM: field, like Gobbel2000@nerds.org, if that’s what you want to be known as. You can freetype whatever your want as the FROM: address if you use a good MUA like mutt.

    You can even hack postfix to send over Tor. And you can make it possible to support *.onion email addresses, which is something that no non-self-hosted service offers.

    When I email someone for the 1st time, say it’s alice@someunknownneverseensvc.xyz, I first configure my mail server to relay to @someunknownneverseensvc.xyz over Tor. If that fails (and it often does), I configure Postfix to directly send to that server from my dynamic IP (or VPN if I have that running). That’s the default, in fact. If that fails, then I can cave-in and compromise my privacy by relaying through a 3rd party, if I choose. Most importantly, I am in control. If I really want to send the msg but I really do not want an additional MitM, I may be able to create an acct on @someunknownneverseensvc.xyz and then use that as a relay to recipients on that host.

    Rise-up has an onion SMTP server. So if you have a riseup acct you could use their onion as a relay.

    Inbound

    (your acct @ rise-up or disroot.org or danwin1210.de or autistici) → POP3 onion using fetchmail → local Postfix → dovecote or procmail → local files read by your MUA of choice

    You avoid a lot of complexity and labor by not maintaining a WAN-listening server. Though you still have a fair amount of effort in configuring your junk, you need not do all the configuration up front. You can do it on a piecemeal per-outbound msg basis to spread your config effort out over time. Of course you need to use a forwarding service or do some DNS arrangements if you want an address that does not tie you to an ESP.

    This approach relieves you of the reliability problem… you need not maintain a server always online, up, and listening. But of course you lose some privacy because all your inbound traffic is seen by your ESP. At least you can potentially circumvent your ESP on outbound mail.

    BTW, you might want to crosspost to !email@lemmy.sdf.org

    (update) my complaint with Postfix: no Tor support out of the box

    Postfix needs some hacking to get it to work over Tor. As old as Postfix and Tor both are, they should work together out of the box.


  • side note: downside is, your data there is more snoopable, less so with something like proton.

    Can you elaborate? AFAIK, Protonmail only gives e2ee in 2 rare situations:

    • Both parties use PM
    • The non-PM user has a PGP key and the PM user is competent enough to add the key to their PM address book. (This is where Hushmail is superior to PM, but HM is not gratis)

    In all other scenarios (no e2ee), PM traffic and data-at-rest is just as exposed as conventional non-PM.


  • True, but sending from a static IP that is linked to you yields less privacy. I’ve decided: fuck these email recipients who demand I compromise privacy in order to give them the convenience of relying on IP reputation. Sure, google and MS servers refuse email from me, but I prefer that anyway. I use postal mail for such recipients (and yes, that’s most recipients).








  • As applied to banks it seems not so bad

    Certainly in the US it’s a catastrophic shit-show. The law only requires collection of 4 pieces of info, but the same law says “and banks may also collect whatever the hell they want with immunity to damages”. Then US banks lie to their customers and say “we need your annual income because KYC because US Patriot Act”… and people simply believe it. They don’t know the says the bank legally /can/ collect it, but that it’s not legally required.

    Then when the data breach happens, the cyber criminals get a huge treasure trove of sensitive data the bank did not need in the 1st place. When the breach is on an outsourced entity, no law in the US requires that outsourced entity to disclose to victims which bank supplied the info. So e.g. Citibank gives your data to corp X to do a some arbitrary service. Then corp X (who you never heard of) sends you a note: “we were breached… sorry… here, have some free credit monitoring through this Cloudflared website”.

    Victim: which bank gave you my data?
    corp X: (crickets)

    It’s astonishingly stupid how many Americans are naïvely okay with that arrangement.

    but they keep expanding it to new types of business.

    Indeed, VOIP may be next abuse of the KYC anti-privacy model. Why not… if the masses are stupid enough to lick bank’s boots, surely people can be conditioned to go along with tossing their privacy out wherever else KYC manifests from the Orwellian playbook.



  • All people with a right to live in the EU have a right to a free or reasonable priced bank account.

    Not exactly. That’s just a façade in attempt to create the optical illusion of equality. The EU requires member states to support a “basic” bank account, but then the EU looks the other way when they reduce the account capabilities and charge fees. You pay much more for a basic account than for a retail account, and depending on the member state you also loose features and capabilities. Some member states block cash services on basic accounts – thus making them useless in the context of this thread.

    So in the end, Americans are still marginalised on the basis of nationality.

    The assumption in the leaflet when they say they are protecting surcharges for using cash. They aren’t implying a right to charge more for using cash. Your inferring that.

    It’s reality, not inference. Cash payers pay fees that card payers are exempt from.

    The leaflet is accurate. Card payers are protected from fees (fees that cash payers are not).

    They can’t make that commitment because not all countries use euro in the EU, that’s why there’s no common EU wide solution for cash payment legislation.

    The EU absolutely has the power (exclusively, in fact) to prevent surcharging cash. Non-euro countries have more sovereignty in this regard, by choice.









  • First of all, you didn’t answer the questions.

    But I will answer yours:

    Why do people fear downvotes so much?

    This is irrelevant and already addressed in Lemmy. Lemmy already has a disable downvotes config option. Beehaw is an example of where that is used. Anyone who outright opposes¹ downvotes can use beehaw.

    Silent downvotes are a different matter entirely. There is good reason to oppose silent downvotes. They are a suppressive act that lacks justification, heavily manipulated, and adds negative value and toxicity.

    Re: toxicity – silent downvotes are also an assault on dignity as they regard the OP as unworthy of explanation. Then there is the further side-effect of the OP being denied the viewpoint of a (cowardly) opposition and ultimately being denied understanding of the community they are in, which is not conducive to future positive content.

    It’s ultimately shitty communication. Like when a bank’s way of communicating to you that your ID card expired on file is to freeze your account. Or when in Office Space they communicate to Marvin he is fired by fixing a payroll glitch. It’s that kind of communication that’s shitty. Bizarre how people actually think this is a sensible way to communicate in a civilised society.

    If you don’t like the downvotes, you can use a sorting algorithm that ignores them.

    There is no sorting algo that disregards silent downvotes while counting reasoned downvotes.

    Also, the power of defaults is a thing. The suppression has effect because of default algos used by the unmeticulous masses. One’s own custom sorting algo could not make a dent in that even if it were magically feasible from the user’s view to associate upvotes to downvotes.

    ¹ I don’t outright oppose downvotes, but when our blunt options are the default shit-show we have by default or no downvotes, no downvotes is better which is why I use beehaw.