katzenberger / is on Nostr

Rolf | RFK ⁂ 🇪🇺🇺🇦🟣
Please be advised that I make only limited use of Content Warnings.
Private account | English and German

#NoBot #NoBridge | My posts are licensed under Creative Commons Attribution-NonCommercial-ShareAlike (https://creativecommons.org/licenses/by-nc-sa/4.0/)

Web: https://katzenberger.tel
Business: https://pragmatic-teams.com/
Pronouns: he/him
My posts w/o boosts: katzenberger (npub1y3h…kyxr)">https://justmytoots.com/katzenberger (npub1y3h…kyxr)
Formerly: @social.tchncs.de, 2021-09-01 to 2024-06-15
Post deletion: after 3 months, unless boosted or favorited

Last Notes

2024-09-17 12:32:49

- reply

There are practical consequences for all similar "ideas" in this field.
E.g., we don't even have the most basic stuff like a free, non-commercial Time Stamping Authority (TSA) service - while the protocol is public, the requirements for running a TSA are so comprehensive that the "free" implementations aren't trusted by anybody because they do not meet those requirements.
Which, in turn, leads to applications like @npub19fl…pxyp resorting to the bitcoin, earth-burning blockchain as a de-facto "reliable" timestamping backend.
To the best of my knowledge, the only institution that ever managed to escape a similar hell was the Let's encrypt CA, and it ultimately depended on the help and agreement of big corporations and an existing CA for that.

2024-09-17 11:38:36

- reply

This architecture gives the "issuers" unprecedented gatekeeping and extortion powers. The section on "Equitable access" lists but a few, and belittles the risks as a mere "challenge". It completely fails to mention that this expensive, highly regulated machinery will unload its costs to users - i.e., exclude people who can't afford obtaining and "renewing" credentials.
On the side of the services, PHC is a dream come true for the delegation of discrimination: eliminate everybody from your service who can't afford or obtain a PHC, without even having to resort to profiling or buying background information, and with being able to deny all of this: "it's the issuer, not us, you see?"
Since you (seem to have) mentioned #eIDAS and #ESSIF: its concept of "trust services" / "issuers" suffers from similar deficiencies: tremendous requirements, resulting e.g. in no free trust services available (because providing them for free would be prohibitively expensive), resulting in discrimination and exclusion.
Concepts like eIDAS, ESSIF and PHC are typically lobbied for by businesses that intend to profit from becoming "issuers" or "trust services", and therefore urge legislators to "just specify the requirements", and "leave the rest to the market".

2024-09-13 15:12:02

United Nations Office for the Coordination of Humanitarian Affairs #UN #OCHA periodical update on #Gaza:
At least 41,118 Palestinians #killed by now, including¹ at least 14,685 #children and 9,670 #women
About 62% of all #housing units either destroyed/rendered uninhabitable (73,000) or damaged (290,000)²
About 1.9 million (90% of population) internally displaced people (IDPs) in shelters
No update since: ¹Apr 23, ²Jan 22
https://www.ochaopt.org/content/humanitarian-situation-update-217-gaza-strip

2024-09-12 15:31:47

- reply

Despite this being promoted as supporting multiple "discovery providers", the text says »This will specify how an instance will “feed” content to a discovery provider to index. And how a discovery provider can be queried to actually search and discover content.«
Nothing is being said about why there would ever be a need for a more than a few big providers, once it is established that the big ones "work". As usual, centralization is looming here, by a few corps "generously" offering high-speed "discovery" for "free".
Also, nothing is said about providers sharing results of the indexing, to enable fediverse-wide search - instead, the proposal almost inevitably points to few providers that everybody needs to feed if they want posts to be found.
"Hope" will not change that hence just saying »We want to specify how a discovery provider works and interfaces with a Fediverse server instance. We hope to inspire several competing implementations of the specification.« does not make much sense.
Nothing is said about who outside of the Fediverse gets to query a provider, or to process the data that has been extracted from a fediverse server feed - and for which purposes. It's even expressly mentioned that »These “providers” might serve other purposes than just search and discovery«
»The protocols and implementations will respect user privacy«, but the text only offers "shoulds": <li>»Our reference implementation will respect this setting and only ingest content from creators who opted in to discovery in the first place.« (note the telling words "respect" and "ingest" here, it does not even seem consensus that providers are "fed" by Fediverse servers). </li><li>»All other information a discovery provider gathers should be anonymous.« Should?</li><li>»Fediverse Discovery Providers should only ever index content clearly marked as “public”.« Should?</li><li>»Fediverse Discovery Providers should honor these settings and only index user data and content from users who have opted-into that.« Should?</li>
Another red flag: »This means we might not always be able to incorporate all the feedback we get into the very first draft of everything we publish. But rest assured that we are committed to continue working on this even after this first project has ended, so we will be able to make adjustments later on.«
More privacy after the first implementation is out? And no: With Mastodon gGmbH being the driver of this, and with the current wording, we can not "rest assured".
[@EC_NGI](https://ec.social-network.europa.eu/@EC_NGI )

2024-08-22 05:08:16

- reply

I believe you are familiar with #blockchains that are based on #ProofOfWork, so it should be sufficient to say that the energy required by #bitcoin is already an estimated 120 Twh annually, surpassing several countries.
While single users may try to calm their conscience by only using a fraction of this (and #ProofMode by pointing to its aggregation mechanism), it's the sheer scaling effect that matters. Merely by using the bitcoin blockchain with others, you'd also be contributing to stabilizing bitcoin, fostering an even wider usage of it, and faster burning of our planet. As an idiom in my language goes: no raindrop wants to be guilty of the flood. But they are.
https://ccaf.io/cbnsi/cbeci
With respect to the myth that mining takes place in remote regions, fueled by "clean" electricity from Iceland, you might wish to read this, to see what these compounds are doing to their environment:
https://time.com/6982015/bitcoin-mining-texas-health/
In short: proof of work is a crime against humanity.
@npub14v5…uldt @npub19fl…pxyp

2024-08-03 15:20:39

- reply

You mean you're restricting your movements at home to the areas where your headphones connect? 😉

2024-07-31 19:06:49

- reply

Interesting. When you can pin down what it is in your context, I'd be happy to read another post about it!

2024-07-31 18:15:28

- reply

It emphasizes there is a well-established relationship (real or imagined) upon which the current conversation is built.
You can use it e.g. to signal that you want your message to be taken absolutely serious, especially a negative one.
Compare how easy it is to answer with a "But …" to a
"No."
vs. to a
"No, Ciara".

2024-07-19 09:26:46

- reply

Are there any plans to verifiably #timestamp and #sign the #metadata collected in verification mode, similar to what ProofMode does?
Unfortunately, they're using opentimestamps.org for the timestamping part, which in turn uses bitcoin's blockchain, so that's a no-go for me.
@npub14v5…uldt

2024-07-08 21:45:20

- reply

Hate to say it, but neither the UK nor France are in North America anymore.
[@The_Whore_of_Blahbylon](https://mastodon.social/@The_Whore_of_Blahbylon )

2024-07-08 15:32:30

#Mastodon seems to be more popular in #China than I expected - at least, I'm seeing my brave little #WebServer being hammered by a #DDoS attack that by far exceeds both its importance in the world, and the reach of my posts on the #Fediverse.
Anyway: thank you for validating me, #WinnieThePooh, and for letting me learn a few more useful things about web servers.

2024-07-07 19:25:27

- reply

I'm confused.
You're not requesting they should guillotine themselves, are you?

2024-06-20 20:15:55

- reply

I really admire your text cutting skills, your deliberate effort to make this look like a blanket statement.
You are very well aware whom exactly @npub1p09…m5vl criticized in this post, and for what specific reaction.

2024-06-20 07:40:21

- reply

@npub1p09…m5vl is pointing out the simple fact that companies with a quite decent overall budget are pushing out essential software that excludes people who had been better supported before. As everybody trying out accessibility features under Wayland vs. x11 can easily experience.
Nowhere is he posting blanket statements like your "people are not supporting accessibility". These are your misrepresentations of what he is saying.
Quote him correctly.
@npub1m0f…k3na @npub1nnl…udhf

2024-06-20 06:44:32

- reply

As I see it, @npub1p09…m5vl has been calling out ableist behaviors, not arbitrarily labeling people, and most certainly not @npub19nh…v7fc (prove me wrong).
The worst part of ableism in software development is to treat accessibility as yet another "requirement" in the list that consistently gets ranked down, kind of a bonus of grace. Like with pushing out Wayland fully knowing that this will exclude people.
It seems to be hard to imagine for some what this means for people depending on features like e.g. a screen reader that is fully functional, and works during installation already. And sometimes this ignorance shows in very disappointing statements and replies.
@npub1m0f…k3na @npub1nnl…udhf

2024-06-15 19:29:43

Not really an #introduction but here we go:
#Freelancing #Facilitator, #TeamCoach & #Trainer
Ex #SoftwareDeveloper, #Consultant, #TeamLead, #HeadOfProductDevelopment #HeadOfIT
I care for #privacy #HumanRights #DEI #TransRightsAreHumanRights #Linux #FLOSS #DigitalSelfDefense
See bio for links & websites.