yosamino

Look, I was trying to understand why the op believed the points that they made were not "pro surveillance-state", that doesn't align with what you are interested in reading here, but that's not really my job.

> You implied

I think you are implying that I implied.

Best to end this here, probably.

But I do believe them. It's just that they points that they sincerely ( I did not doubt that) made are part of the same set of points that are made in favor of a surveillance state - there is a contradiction here. Instead of assuming, I asked a question.

Quite literally this:

> attempt to understand how they could come to believe those things.

Is it possible that you are not reading my comment charitably ?

I did and then I asked a serious question.

These are arguments that are put forward in favor of mass-surveillance.

That is in direct contradiction to the claim "I’m not trying to be pro-surveillance state or whatever".

So I was wondering how that contradiction comes about and asked about it.

What would you suggest the charitable reading should be ?

> Look, I’m not trying to be pro-surveillance state or whatever, but

... but why do you then go on making all pro-surveillance state arguments ?

> spend your energy on something with a better chance of success.

but what ?

Bit of a Radio Yerevan Situation. Not even the various emergency broadcast app reliably get timely push notifications.

The thing about these notifications seem to be that apps that regularily get notifications from the the app get them reliably.

This is based on the observation that xmpp-contacts I'm in regular contact with seem to get notifications quickly and contacts I talk to less regularily not so much.

Sadly this dependent on apples whims

The current state of affairs is that cloudflare is that huge organization that arbitrarily censors websites without a mechanism for appeal or legal process.

Cloudflare actively removes your ability to decide for yourself which websites and systems you want to connect to by obscuring their sources.

Without Cloudflare I could decide for myself that I want to block certain networks to connect to my networks.

Cloudflare hiding the origin of these networks along with it's size in the market make Cloudflare exactly that huge organization.

This is a flawed analogy. The "keyboard manufacturer" in this scenario is the "router manufacturer" who Cloudflare buys off of, not Cloudflare.

In your scenario Cloudflare is more like a newspaper aggregator which carries all sort filth along with it's normal commentary.

If this was a normal situation one could just decide not to read some filthy newspapers, while letting those who want to read it make that decision for themselves.

But in the Cloudflare scenario all the major relevant normal newspapers decided to publish all their content through Cloudflare and if something objectionable is published along with it, instead of taking your beef to the original publisher, you have to to take it up with Cloudflare who might just forward your details to some very unsavory people without you having a chance to know beforehand.

Cloudflare enables this because their stance is that they are a neutral carrier who is not responsible for the data they carry. If I send an abuse report to github for content on their system, there is a chance that I will be annoyed by how they handle it.

Cloudflare's core thing OTOH is to hide who I could be sending an abuse report to,

Possibly they will forward it ( more likely not) , but they will include my personal information in a report to an entity that is unknown to me, who are likely criminals, exposing me to danger.

That's not a "weird belief". Cloudflare positions itself as "infrastructure". That means they think they are not responsible for the content that they carry.

In a normal scenario, if you want to protect your systems from other "bad" systems on the internet, you can block them on the IP layer.

But Cloudflare operates at the IP layer proxying data between you and good and bad (and everything in between) systems.

In a normal situation you could block and report a site that is run by the the mob, by either blocking them at the IP level or by contacting the abuse@ of the organization that is hosting the content.

Cloudflare is making it so that you can't do either. And if you send an abuse report to Cloudflare, you cannot be sure that they will not just forward your contact information directly to the entity that you are complaining about. They have changed their stance over the years to appear more responsible, but the fact remains:

If I want to send an abuse@ report to a system that is hidden behind Cloudflare I can not be sure that they won't just forward it without me knowing who they are forwarding it to.

The last time .de I remember .de had a major outage like this was 2010. I would cite some sources but... you know. That was a fun afternoon, though.

I am very happy that it doesn't happen more often.

> If so, why does it make sense that people can "generate" cash by proving some amount of work done?

Think of it this way: If you pay with physical cash, there are people somewhere who do the work of digging ore out of the ground, smelting it, shaping it into coins, cutting and printing paper and so on. All these people do that, because they get paid in the same currency that they themselves have minted.

It turns out that nobody has yet found a way to create a digital decentralized currency that that works without incorporating a similar concept of incentivizing the creation of currency.

Heh

> For privacy reasons we've made the planet shake a little bit

Thank you for the hint. We live in a very complex world...

That looks pretty cool - sorry to have a complaint immediately:

When opening the map on Firefox/Linux zooming to like a France-size view and then not doing anything, the view keeps scrolling up and down relatively slowly, but very annoyingly.

Zooming all the way out, it looks like the globe is jiggling back and forth ever so slightly, but continually.

I've recently seen this happen on another mapping application ( cannot remember which one) so it's probably in down the stack somewhere in a library you are using.

This isn't the issue that's at stake here though: The question is:

> Who is making the decision which code is allowed to run on my device?

The status quo is already that can make this decision yourself. There are other people who make different decisions from you.

The proposed change is trying to take this decision away from you and making google the arbiter of which code is allowed to run.

The core of this issue is the opposite of "publishing an app to a global scale ecosystem" - I want to publish an app that is useful for me and a very small circle of people, that is what's being taken away.