debanqued

I’m scared.

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 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).

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.

The cognitive dissonance in this

It seems you don’t know what that phrase means. It doesn’t follow from anything else you wrote why you think that.

You don’t think providing an email from a throw away service would strike the software as a malicious user/spam bot???

You don’t think that legitimate streetwise users secure themselves by supplying disposable email addresses???

You keep talking like you know everything

The post intends to solicit intelligent and civil discourse with logical reasoning, not the sort of ego-charged emotional hot-headed pissing contest you’re trying to bring here.

I’m not seeing how this is a good justification for login refusals to lack information and transparency. When you are denied a login, a well designed system tells you why you are denied and the rationale the server gives you should either include enough info to imply a remedial course of action (e.g. “re-apply and tell us more detail about why you like our node”), or at least make it clear that the refusal is final for reasons that are non-remedial. Users should not have to guess about why they are denied a login when countless things can go wrong with email at any moment. The denial rationale should be emailed and also copied into the server records to present upon login attempts.

The only exception to this would be if they really believe they are blocking a malicious user. Then there is some merit to being non-transparent to threat agents. But the status quo is to treat apps rejected for any arbitrary reason as they would an attacker.

There is no valid reason for the United Nations blocking Tor.

A mom & pop shop selling cupcakes would have a valid reason (lack of funding, lack of competence, no conflicting principles). Blocking Tor is a cheap and sloppy attempt at separating ham from spam which inherently entails blocking ham, ultimately against the principles the UN theoretically supports. The UN should have the funding and competence to support their own values.

The UN probably should not be drafting rules about digital inclusion when they themselves have an embarrassing display of digital exclusion.

I don’t want to be an enabler of the drivel, so without posting the full URL to that article that’s reachable in the open free world, I will just say that medium.com links should never be publicly shared outside of Cloudflare’s walled garden. I realise aussie.zone is also in Cloudflare’s walled garden, but please be aware that it’s federated and reaches audiences who are excluded by Cloudflare.

The medium.com portion of the URL should be replaced by scribe.rip to make a medium article reachable to everyone. Though I must say this particular article doesn’t need any more reach than it has.

Anyone who just wants the answer: see @souperk@reddthat.com’s comment in this thread.

A website isn’t a common carrier

We were talking about network neutrality, not just common carriers (which are only part of the netneutrality problem).

you cannot argue that a website isn’t allowed to control who they serve their content to.

Permission wasn’t the argument. When a website violates netneutrality principles, it’s not a problem of acting outside of authority. They are of course permitted to push access inequality assuming we are talking about the private sector where the contract permits it.

Cloudflare is a tool websites use to exercise that right,

One man’s freedom is another man’s oppression.

necessitated by the ever rising prevalence of bots and DDoS attacks.

It is /not/ necessary to use a tool as crude and reckless as Cloudflare to defend from attacks with disregard to collateral damage. There are many tools in the toolbox for that and CF is a poor choice favored by lazy admins.

Your proposed definition of net neutrality would destroy anyone’s ability to deal with these threats.

Only if you neglect to see admins who have found better ways to counter threats that do not make the security problem someone elses.

Can you at least provide examples of legitimate users who are hindered by the use of Cloudflare?

That was enumerated in a list in the linked article you replied to.

Interstate commerce is governed by the federal government.

Not exclusively. Interstate commerce implies that the feds can regulate it, not that they have exclusive power to do so. We see this with MJ laws. The fed believes it has the power to prohibit marijuana on the basis of interstate commerce, but in fact mj can be grown locally, sold locally, and consumed locally. Just like internet service can be.

Suppose you want to buy a stun gun in New York. You can find stun guns sold via mail order from another state (thus interstate commerce), but New York still managed to ban them despite the role of interstate commerce.

A close analog would be phone laws. The fed has the TCPA to protect you from telemarketers, but at the same time various states add additional legal protections for consumers w.r.t. telemarketing and those laws have force even if the caller is outside the country. (Collecting on the judgement is another matter).

Schools now require the internet for kids. ISPs being allowed to be anything more than a dumb pipe means they have the control of what information is sent across their network.

Education is specifically a duty of the state set out in the Constitution. If you can point to the statute requiring schools to provide internet for students, I believe it will be state law not federal law that you find.

The internet is now a basic human right in the United States for numerous reasons, one of which is #2.

I don’t quite follow. Are you saying that because education is a human right, that internet access is a human right? It doesn’t work that way. First of all, people who do not exercise their right to an education would not derive any rights implied by education. As for the students, if a state requires internet in education that does not mean that internet access becomes a human right. E.g. an Amish family might lawfully opt to homeschool their child, without internet. That would satisfy the right to education enshrined in the Unified Declaration of Human Rights (UDHR) just fine. A student attending public school in a state that mandates internet in schools would merely have the incidental privilege of internet access, not an expanded human right that students in other states and countries do not have under the same human rights convocation. If your claim were true, it would mean that California (for example) requiring internet provisions for students would then mean students in Haiti (a country that also signed the UDHR that entitles people to a right to education) or Texas would gain a right to internet access via the state of California’s internal law. A state cannot amend the UDHR willy nilly like that.

Also, if internet could be construed as a human right by some mechanism that’s escaping me, the fed is not exclusively bound by human rights law. The fed signed the treaty, but all governments therein (state and local) are also bound to uphold human rights. Even private companies are bound to human rights law in the wording of the text, though expectation of enforcement gets shaky.

ISPs cross state boundaries and should be governed by interstate law.

I subscribed to internet service from a WISP at one point. A dude in my neighborhood rolled out his own ISP service. His market did not even exceed the city.

The local ISPs have ISPs themselves and as you climb the supply chain eventually you get into the internet backbone which would be interstate, but that’s not where the netneutrality problem manifests. The netneutrality problem is at the bottom of the supply chain in the last mile of cable where the end user meets their local ISP.

Also with MJ laws, several states have liberated the use of marijuana despite the feds using the interstate commerce act to ban it.

An ISP being a business, especially a publicly-traded one, will sacrifice all manner of consumer/user-protection in order to maximize profit. And having the states govern against that will lead to a smattering of laws where it becomes muddy on what can actually be enforced, and where.

Sure, and if the fed is relaxed because the telecoms feed the warchests of the POTUS and Congress, you have a nationwide shit-show. A progressive state can fix that by imposing netneutrality requirements. Just like many states introduce extra anti-telemarketing laws that give consumers protection above and beyond the TCPA.

And having the states govern against that will lead to a smattering of laws where it becomes muddy on what can actually be enforced, and where.

That’s a problem for the ISPs that benefits consumers. If ISPs operating in different states then have to adjust their framework for one state that mandates netneutrality, the cost of maintaining different frameworks in different states becomes a diminishing return. US consumers often benefit from EU law in this way. The EU forced PC makers to make disassembly fast and trivial, so harmful components could quickly and cheaply be removed before trashing obsolete hardware. The US did not impose this. Dell was disturbed because they had to make pro-environment adjustments as a condition to access to the EU market. They calculated that it would be more costly to sell two different versions, so the PCs they made for both the EU market and the US market become more eco-friendly. Thanks to the EU muddying the waters.

The right to repair will have the same consequences.

On a serious note, plenty of people here surely know what net neutrality is. Net neutrality is the guarantee that your ISP doesn’t (de-)prioritize traffic or outright block traffic, all packets are treated equally.

That’s true but it’s also the common (but overly shallow) take. It’s applicable here and good enough for the thread, but it’s worth noting that netneutrality is conceptually deeper than throttling and pricing games and beyond ISP shenanigans. The meaning was coined by Tim Wu, who spoke about access equality.

People fixate on performance which I find annoying in face of Cloudflare, who is not an ISP but who has done by far the most substantial damage to netneutrality worldwide by controlling who gets access to ~50%+ of world’s websites. The general public will never come to grasp Cloudflare’s oppression or the scale of it, much less relate it to netneutrality, for various reasons:

• Cloudflare is invisible to those allowed inside the walled garden, so its existence is mostly unknown
• The masses can only understand simple concepts about their speed being throttled. Understanding the nuts and bolts of discrimination based on IP address reputation is lost on most.
• The US gov is obviously pleased that half the world’s padlocked web traffic is trivially within their unwarranted surveillance view via just one corporation in California. They don’t want people to realize the harm CF does to netneutrality and pressure lawmakers to draft netneutrality policy in a way that’s not narrowly ISP-focused.

Which means netneutrality policy is doomed to ignore Cloudflare and focus on ISPs.

Most people at least have some control over which ISP they select. Competition is paltry, but we all have zero control over whether a website they want to use is in Cloudflare’s exclusive walled garden.

Why would it necessarily have to be federal law, and not state law?

/cc @ulkesh@beehaw.org