debanqued

joined 3 years ago
 

Front-desk receptionists installed in the buildings of gov agencies, news offices, and large companies sometimes have (or act like they have) a strict protocol of tasks that they can or cannot do. If I ask them to page/call relevant staff for something, or to sign for a delivery, they answer to the effect of:

“That is not in my job description…”

or

“Nope, not on my list… I have no scripted process or procedure for that…”

Some receptionists will say “do you have an appointment?”, to which I answer “if an appointment is needed, please make one for me”. They can never handle that. They say call or email, which of course excludes¹ people.

It’s increasingly more common for the outsourced security receptionist to be dumbed down to know nothing about the org they are keeping a gate for, to have no visibility on schedules and no ability to page people. These “people” typically have no capability beyond writing a call center phone number or URL on a post-it note.

I have to wonder, if these unskilled people are going to be so stripped of basic capability, unable to cater for the needs presented in a situation, why even have them? They are good candidates to be replaced by robots, or even just a sign-posting with a QR code on it².

It’s in everyone’s interest for that threat to be looming, and for such receptionists to come to realise that their own job security relies on being customer oriented (not their boss as a customer, but the ultimate customer, who won’t give a shit if a robot replaces a human that acts just like a robot anyway).

Consider the insideous #forcedBanking dimension to this. Making the front desk helpless enables the org/agency to essentially maintain a non-physical presence, which they use as an rationale for refusing cash payments. The outsourced recepionist can be passed off as someone who does not represent the org/agency and thus cannot handle cash payments.

¹ Calling excludes people because call centers have a limit number of languages they can handle, and even if you’re lucky enough to get someone with a compatible language, you lose the possibility of body language, a bad quality signal makes rough language rougher, and if one side gets tired of speaking a non-native language it’s easy enough to just hang up. Calling also is not free. And email is also exclusive

² (in fact I’ve seen it happen.. a gov office receptionist got replaced with a QR code pointing to a dysfunctional website)

Call to action

Maybe print this rant on a flyer that starts with “Dear receptionist…” and keep a copy when you approach a front desk. If they turn out to be a human acting like a bot, give them the flyer. Suggest they read it and share it with their boss.

[–] debanqued@beehaw.org 1 points 1 month ago

Every method has a barrier:

  • snail mail: requires postage, which is particularly costly if you need proof of delivery. Also generally entails revealing your physical address to the controller.
  • email: requires revealing your email address to them. And if the recipient is MS or Google, or a user on those platforms, their mail server is fussy. I cannot email any MS or Google users because their server blocks my mail server.

A webform could potentially have the fewest barriers, but they blew it.

 

Indeed, MS only makes GDPR rights available to people who are willing and able to solve their graphical CAPTCHA. You must execute their JavaScript and have image rendering enabled in your browser.

For sighted people it’s not the more shitty varieties of CAPTCHA. Looks easy. But still fucked up that there is a barrier to exercising GDPR rights.

 

Suppose you have the following parties to an email conversation:

Douche Bank¹ manages to collect Alice’s email address either legitimately from her or illegitimately without her consent. DB sends her an email like this:

From: "Douche Bank" 
To: "Alice Marie Smith" 
Subject: Your unpaid debt of €20,000 on account № 354-987-156

Pay up.

Alice did not choose to do business with Microsoft Corporation and does not trust MS in the slightest. Yet Douche Bank has exposed sensitive financial information about Alice to MS, potentially without her consent. She may or may not have supplied an email address to D/B but certainly she opposes MS receiving her sensitive data, which it will then exploit to the fullest for surveillance marketing or otherwise.

Alice has no control over her bank’s choice of email provider. But in principle the GDPR is expected to give her control over her data exposure. If she makes an art.17 request to erase the privacy-abusing email, it’s too late b/c MS already saw it. The bank would not erase it because they have a legit need to track the fact that they sent a payment reminder. The bank /can/ mirror Alice’s art.17 request to MS if they are motivated, but most likely they will not, particularly if the bank is not treating the art.17 request themselves. And most likely MS would ignore it anyway.

If Alice sends a GDPR request direct to MS to erase MS’s copy of the email, MS would naturally respond with something like ”who are you? You are not our customer. Therefore we cannot properly identify you in accordance with GDPR rules. Also, we are just a “data processor” not a “data controller”. Sorry.. you can fuck off now.” (in so many words)

If Alice were to complain to the Data Protection Authority of Germany (where MS is headquartered), they would be helpless in this situation. I mean, there is Art.32 which requires processing to be secure, but most data controllers seem to be ignoring Art.32 w.r.t Art.77 requests. EDPB said in their “Contribution of the EDPB to the report on the application of the GDPR under Article 97” report:

“fines were imposed … for failure to comply with the obligations with regard to the rights of the data subjects (Article 12 to 22 GDPR),”

IOW, infringements on Articles outside the Art.12-22 range are not considered by the EDPB as “rights of the data subjects”. I’ve seen a similar sentiment expressed in other places.

¹fictitious name inspired by Deutche Bank/Bank of America

[–] debanqued@beehaw.org 1 points 6 months ago* (last edited 6 months ago)

I wish I kept track of where I read that. Could have been case law, or EDPB guidelines. Maybe I was speed-reading Art.21¶4 (which is really a requirement on the data controller).

It might be a good idea to send a registered letter with reply advice (Einschreiben mit Rückschein).

If I did that it would cost me over €10 for every single request. Even if it leads to lawsuit and the court favors my claim, registered letters are still a loss. They cannot be claimed back in court.

 

I read somewhere that GDPR requests for restricted processing (Art.18) cannot be combined with any other topic or request. E.g. If you request that they not use your e-mail for marketing purposes.

WTF. Yes, I understand the idea is that if the request stands on its own, it cannot be overlooked. But #GDPR requests are ignored so often that I deliberately combine a GDPR request with another request that is more difficult to ignore. That way when they ignore the GDPR request but treat the non-GDPR request from the same letter, it proves that the data controller received my letter. When a GDPR request is made on its own, they can more easily claim the letter never came and shift the proof-of-delivery burden onto me.

[–] debanqued@beehaw.org 1 points 7 months ago (1 children)

You say for suspicious users, but for the 4-month stretch of beehaw being unreachable there was no opportunity to login. So there was apparently a user agnostic systemwide change.

[–] debanqued@beehaw.org 4 points 7 months ago* (last edited 7 months ago) (1 children)

It’s worse than being reversible. The problem is that it’s unprovable. A switch from “zero logging” to “log everything” is wholly undetectible to users. You have to rely on blind faith that a profit-driven entity will act in your interest and resist their opportunity to profit from data collection. All you have is trust. Tor avoids that whole dicey mess and reliance on trust.

[–] debanqued@beehaw.org 3 points 7 months ago (3 children)

Indeed the ISP can only see where you go when using TLS, and that data can be aggregated to who you are along with everywhere else you go. It’s sensitive enough that in the US lawmakers decided on whether ISPs need consent to collect that info. Obama signed into force a requirement of ISPs to get consent. Then Trump reversed that. Biden did not reverse it back AFAIK.

W.r.t VPNs, you merely shift the surveillance point; you do not avoid the surveillance. The VPN provider can grab all that info just as well.

[–] debanqued@beehaw.org 9 points 7 months ago* (last edited 7 months ago) (6 children)

I am anonymous. Only doxxing experts know who is behind my account. Using clearnet makes it trivially simple for doxxers. Activitypub msgs include the IP address of the sending source which anyone with their own instance can see, IIRC.

But note as well Tor offers more than anonymity. It mitigates tracking by your ISP.

 

For the past four months beehaw has been unreachable to those of us on the Tor network. Glad to see access was finally restored. Was there an attack?

I could really use a way to periodically backup my posts to my local disk so if Tor is spontaneously blocked again I at least have my history. I’ve not found a Lemmy equivalent for Mastodon Archive.

(edit) For security, it would be a good idea to setup an onion instance. The Tor network has built-in DDoS protection for onion hosts.

[–] debanqued@beehaw.org 3 points 7 months ago (2 children)

lemm.ee is centralized in Cloudflare’s exclusive walled garden. I can’t speek for the admins but it’s antithetical to the purpose of the fedi to advocate for federation with centralized hosts.

And there are consequences. If an image is posted to Lemmy.world, sh.itjust.works, or discuss.online, those of us who are excluded from Cloudflare cannot see it. A non-CF node federating to a CF node creates a broken network.

[–] debanqued@beehaw.org 2 points 7 months ago* (last edited 7 months ago)

If I recall correctly, the main reason we defederated from those instances at the time was the sheer volume of spam we were getting from users of those instances.

Good point (if that’s true). I can’t help but expose the irony of instances centralized under Cloudflare having a spam problem. It seems to show that those instances sold their sole to the devil only to not get the benefits of the devil’s offer.

[–] debanqued@beehaw.org 1 points 11 months ago* (last edited 11 months ago)

The irony, hypocrisy, and injustice here is that the UN’s own website itself discriminates against some demographics of people and denies access to the UDHR of 1948:

And this same UN will be creating the Digital Global Compact.

 

I installed the Aria2 app from f-droid. I just want to take a list of URLs of files to download and feed it to something that does the work. That’s what Aria2c does on the PC. The phone app is a strange beast and it’s poorly described & documented. When I launch it, it requires creating a profile. This profile wants an address. It’s alienating as fuck. I have a long list of URLs to fetch, not just one. In digging around, I see sparse vague mention of an “Aria server”. I don’t have an aria server and don’t want one. Is the address it demands under the “connection” tab supposed to lead to a server?

The readme.md is useless:

https://github.com/devgianlu/Aria2App

The app points to this link which has no navigation chain:

https://github.com/devgianlu/Aria2App/wiki/Create-a-profile

Following the link at the bottom of the page superfically seems like it could have useful info:

“To understand how DirectDownload work and how to set it up go here.”

but clicking /here/ leads to a dead page. I believe the correct link is this one. But on that page, this so-called “direct download” is not direct in the slightest. It talks about setting up a server and running python scripts. WTF.. why do I need a server? I don’t want a server. I want a direct download in the true sense of the word direct.

[–] debanqued@beehaw.org 1 points 1 year ago* (last edited 1 year ago)

I would love to put my code where my mouth is. It’s on my long list of projects. The defects I describe in this thread probably do not justify a forking effort and I’m not enthusiastic about learning JavaScript, which is not just a shitty language but also it’s the wrong tool for the job. Although Rust is probbly a decent choice for the backend (but Ada would probably be better).

The biggest deficiency is that there is no decent threadiverse desktop client. I am just baffled that a majority of threadiverse users are using phones. There are like a dozen different mobile clients to choose from and not a single decent client for the desktop. So if I build anything it will be a proper client for a sensibly sized screen (non-portable).

As for fixing the defects exposed in this thread, the upstream Lemmy devs are rather stubborn but I think devs of an existing fork (Lenny?) might be more open to improvements.

Who would use a well-designed variant? You can see from the thread that millennials & gen Zers actually expect designs that prioritise the anti-bot agenda above the needs of both the direct user (the admin) and the end user. A majority of the population does not see how Google, Spamhaus, and Microsoft have broken email. This threadiverse crowd entered after email was already ruined. The emotional attachment to gmail (calling it what it is.. there is no generic netneutral email infra anymore) trumps software that avoids the dog food problem. I might be the sole user of such software, especially if I also code it to enforce decentralisation (which would necessarily include anti-centralisation features that would be unpopular).

[–] debanqued@beehaw.org -1 points 1 year ago* (last edited 1 year ago)

to have not actually had an account yet makes it pretty obvious when you try to login and fail that the application has not been accepted.

That would be a blunt non-transparent/non-specific message to send. It’s not obvious /why/ the reg was denied.

If the instance admins wanted to talk about it, they’d have emailed you; or published some means of contacting them outside lemmy.

Lemmy software is designed as comms software itself with email address disclosure optional. An admin can make it mandatory, but Lemmy’s design should cater for the email-free option regardless of how an admin toggles that setting.

I wouldn’t expect to receive the reason for refusing the application via any other means than the email I’d provided in that application.

I get that. People are accustomed to relying on email. But this is not an excuse for software deficiencies.

That’s the entire purpose of providing an email; so you could be contacted when/if there are updates to your applications status.

That can be accomplished without email. Email is a convenience at best. Some users have decided email is an inconvenience and do not use it. And Lemmy supports that -- partially.

Let’s be clear about who the software is expected to serve. The comms feature of giving feedback to users without an email account is not to directly serve the end user. Software should serve its user (the Lemmy admin in this case). A Lemmy admin does not want to take the time to express themselves on their decision only to have their msg blackholed. They don’t necessarily know that an email address is disposable. The end user benefits by extension, but it’s about creating software that serves the direct user of the s/w. If you’re an admin who makes email optional, you might still want to be able to get a msg to a user.

The core purpose of the Lemmy platform is communication. So relying on out-of-band tech is kind of embarrassing. Think of it from the dog food angle. An in-band msg has the advantage that the admin has more control (e.g. they can edit a msg later and they can know whether the msg has been fetched). Lemmy relying on email as a primary means of comms is a dog food problem.

The only sensible concession I would see to make is that there are a hell of a lot more important things for Lemmy devs to work on because the software has a lot of relatively serious defects. I’m talking about how great software would be coded, but extra diligent handling of denials should have a low triage in the big scheme of the state of where Lemmy is right now.

 

These are Lemmy instances with a “Sign Up” link which present you with a form to fill out to register. Then after you fill out the form and supply information like email address to the server, they respond with “registration closed”:

  • lemmy.escapebigtech.info (dead node now, but got instant reg. closed msg when they were alive)
  • expats.zone
  • hackertalks.com
  • lemmie.be
  • lemmy.killtime.online
  • lemmy.kmoneyserver.com
  • lemmy.sarcasticdeveloper.com
  • level-up.zone
  • zoo.splitlinux.org

I suppose it’s unlikely to be malice considering how many there are. It’s likely a case of shitty software design. There should be a toggle for open/closed registration and when it’s closed there should be no “Sign Up” button in the first place. And if someone visits the registration URL despite a lack of Sign Up link, it should show a reg. closed announcement.

Guess it’s worth mentioning there are some instances that accept your application for review (often with interview field) but then either let your application rot (“pending application” forever) or they silently reject it (you only discover non-acceptance when you make a login attempt and either get “login failed” or even more rudely it just re-renders the login form with no msg). These nodes fall into the selective non-acceptance category:

  • lemmy.cringecollective.io
  • lemmy.techtriage.guru
  • lemmy.hacktheplanet.be (pretends to send confirmation email then silently neglects to)
  • links.esq.social
  • dubvee.org

To be fair, I use a disposable email address which could be a reason the 5 above to reject my application. And if they did give a reason via email, I would not see it. Not sure if that’s happening but that’s also a case of bad software. That is, when a login attempt is made, the server could present the rationale for refusal. Another software defect would be failing to instantly reject an unacceptible email address.

 

Utility companies, telecoms, and banks all want consumers to register on their website so they do not have to send paper invoices via snail mail. When I started the registration process, the first demand was for an e-mail address.

Is that really necessary? They would probably argue that they need to send notifications that a new invoice has been prepared. I would argue that e-mail should be optional because:

  • They could send SMS notifications instead, if a data subject would prefer that.
  • They need not send any notification at all, in fact. Reminders is why calendars and alarm clocks exist. A consumer can login and fetch their invoice on a schedule. If a consumer neglects to login during a certain window of time, the data controller could send a paper invoice (which is what they must do for offline customers anyway).

They might argue that they need an email for password resets. But we could argue that SMS or paper mail can serve that purpose as well.

Does anyone see any holes in my legal theory? Any justification for obligatory email address disclosure that I am missing?

 

Yikes. As some Tor users may know, the UN drafted the Unified Declaration of Human Rights, which in principle calls for privacy respect and inclusion. That same UN blocks the Tor community from their website. Indeed, being denied access to the text that embodies our human rights is rich in irony.

Well that same UN plans to create a “Global Digital Compact” to protect digital human rights. It’s a good idea, but wow, they just don’t have their shit together. I have so little confidence that they can grasp the problems they are hoping to solve. Cloudflare probably isn’t the least bit worried. Competence prevailing, Cloudflare should be worried, theoretically, but the UN doesn’t have the competence to even know who Cloudflare is.

 

BBC World Service was covering the US elections and gave a brief blurb to inform non-US listeners on the basic differences between republicans and democrats. They essentially said something like:

Democrats prefer a big government with a tax-and-spend culture while republicans favor minimal governance with running on a lean budget, less spending¹

That’s technically accurate enough but it seemed to reflect a right-wing bias that seems inconsistent with BBC World Service. I wouldn’t be listening to BBC if they were anything like Fox News (read: faux news). The BBC could have just as well phrased it this way:

“Democrats prefer a government that is financed well enough to ensure protection of human rights…”

It’s the same narrative but expressed with dignity. When they are speaking on behalf of a political party it’s an attack on their dignity and character to fixate on a side-effect rather than the goal and intent. A big tax-and-spend gov is not a goal of dems, it’s a means to achieve protection of human rights. It’s a means that has no effective alternative.

① Paraphrasing from what I heard over the air -- it’s not an exact quote

#BBC #BBCWorldService

view more: next ›