WIRED

I currently use Debian. It is comfy and predictable and I am lazy.

I did recently try NixOS and Guix and I really enjoyed my experiences in different ways, but I always come back to Debian. I will probably move to Guix at some point, when a powerful passively cooled GPU is available that has less proprietary obstacles for me to grapple with.

I enjoyed NixOS because of the many precompiled things. I had an awesome experience with it. I loved how it just worked, and was so flexible and easy. I totally get why it is the Hotness.

That was until it wasn’t. Suddenly when I got to its edges, it felt like being in another walled garden. For sure the walled garden wasn’t really walled, I just couldn’t be bothered to learn how to climb that particular ladder. Too much to learn. Too much arcane stuff to learn. I mean, I did like Nix, but to learn its own language? Really? Did I mention that I am lazy? I really value my learning time and like it to be as useful (widely serving), long serving and fun as possible and the Nix language just was too arcane for me to get my emacs working without more WTF than I wanted.

That means that as and when I can more easily move to Guix, I will be able to, because it uses a version of LISP. In other words I wont just be learning a language for my OS, but I get to reuse the learning across a range of interests and tools.

I carried on dual booting NixOS its compile of OBS was recent and Just Worked. But recently I ditched the dual boot and have been using OBS on Debian again. But… the Debian OBS package doesn’t have the browser as a source feature. This was a bit too limiting for me, because there are some things that cannot be done without it. Mainly I wanted it in order to make my stream/recordings look a bit less basic by using an overlay. And potentially I also wanted to be able to use Big Tech platforms to stream to, you know, just incase I wanted to stream to something other than the awesome peertube. I like avoiding BigTech, but I also want to be in choice to be able to use it if I want to. Ya know?

So the best option, it seemed, was compile OBS! However, compiling software is something I tend to avoid, did I mention I am lazy? This is particularly true for me where there is something that I use that will likely be updated, i.e. most things. With Debian, it just looks after all that faff for you (most of the time). I like that. I like Debian. It just keeps on trucking.

So compiling a core tool seemed like more faff and effort than I was likely to be able to bother with. I really don’t enjoy running out of date software or having it hanging around on systems.

Since lock down I have experienced more brain fog and anxieties so having the clear headedness that I would need in order to track errors and use the CLI with sufficient velocity to be fun… has been a precious commodity.

I am writing this in part to thank Dario, who wrote a guide that held my hand through the process. This means I now have my own compiled OBS. It is more up to date than the Debian package (of course) and has the browser as a source feature that I wanted. Moments like these bring me all the joy – this is why I really love Free Software and its community.

On the journey, I delighted in the stretch of learning a little more about the CEF project – just Wow! (and why isn’t there a FF equivalent?). I also was delighted in how easy it was to make a package that would then allow me to stay within the Debian Way™, something I have learnt over the 20 years to avoid deviating from (Did I mention I am lazy?)!

<3

Hail Eris!

contributors; eab,

version 0.4 – reframe and relate to foldoc

Some ‘techies’ cultivate awareness about how values such as choice, freedom, empowerment are embodied, or not, by the things that mediate our digital lives. They may or may not identify as holding a hacker ethic.

The cultivation of such values brings pleasure, for instance the creation of ease and elegance for ourselves or others, or the gifting of time in projects (e.g. free software) or meaning in other ways.

Many techies holding such values choose to use software that seeks to embody these values through free software licencing, i.e. software which users can freely share and study and adapt.

I would really love for it to be more possible to enjoy community, most especially nonviolent community at the same time as holding a boundary towards using systems that feel horrible to use. Many familiar companies offer services that appeal to many because of familiarity and ‘no monetary cost’. Unfortunately such services appear to have very different values around things like choice, freedom and sharing and I fear that these systems, even though they are ‘normal’ are really enabling dominator culture and I worry that soon they will support more and more violence.

Therefore this invitation is to examine your digital life in service ensuring integrity in your digital life that is well aligned with a nonviolent practise. Perhaps we might hope to nurture the possibility of another digital landscape, one that is more life serving, one where we take more responsibility for the services we use, such as contributing to the financial cost and are therefore able to ensure the values that we enjoy are more possible in our digital lives too. I hold curiosity for whatever that that might mean, lets dance!

When practitioners in our community who hold leadership roles take action around this, it will be more possible. We are here to support you.

ref

[1]https://en.wikipedia.org/wiki/The_Age_of_Surveillance_Capitalism

notes to add

links to licenses

Author: [eab@nvcdojo.org]
Date: 2024-11-24
Version: 0.434a trollheim

---

Abstract

When I see that technology lacks a framework to express empathy effectively in written communication, I am curious. I value tools that support understanding and collaboration and offer this document in service of hope and contribution.

This RFC (Request for Comments—a type of publication from the principal technical development and standards-setting bodies for the Internet) proposes a standardised syntax for embedding Nonviolent Communication (NVC) into text-based chat protocols, such as IRC, Signal, or other messaging systems. There are a number of purposes in this RFC: – to develop shared meaning and clarity regarding emoji, – to support users in expressing observations, feelings, needs, – to support a culture of well-formed requests, – to support conditions where world peace can spontaneously emerge.

It is also anticipated that this RFC will support reduced miscommunication and enable error checking (a design feature lacking from normative human communication). The syntax consists of structured annotations that can be interpreted both by humans and automated systems.

The framework builds on the foundational work of Marshall Rosenberg (Nonviolent Communication) and Manfred Max-Neef (Human Scale Development), incorporating universal human needs and their connections to well-being.

---

Emoji Use in NVC Syntax

When I notice that emoji are often used inconsistently in online communication,[clarity,flow]🤔 I feel motivated and curious because I value alignment between words and visuals. Emoji in this framework serve as visual representations of feelings, enhancing clarity and emotional nuance in text-based communication. To ensure consistency: – Emoji may represent a feeling explicitly. to avoid redundancy or contradiction. For example, 😤 represents 'I feel frustration because I', so the sentence need not also state “I feel frustrated because I”. – Emoji be optional. While they enrich expression, the syntax remains functional without them.

---

Syntax Specification

Structure

observation(s)[need(s)]feeling(s); message

Formal Syntax (ABNF)

I observe that developers need precise guidelines for implementation,[precision]😌. The following ABNF (Augmented Backus-Naur Form) defines the NVC syntax:

#+BEGIN_SRC text
nvc-message = [observations] "[" needs "]" feelings ";" SP message
observations = 1*(CHAR) [ "." SP 1*(CHAR) ]
needs       = need *("," need)
feelings    = feeling *("," feeling)
need        = 1*(ALPHA / "-")
feeling     = 1*(ALPHA / "-")
message     = 1*(CHAR)
CHAR        = %x20-7E
SP          = %x20 ; Space
#+END_SRC

---

Summary: Removing Blame with “I Feel X Because I...”

When I notice that many conversations online include blame and escalate conflict[harmony]😞. NVC emphasises that feelings arise from our own needs, not others' actions. Using the structure, “I feel X because I...” helps us avoid blaming others and instead express our needs clearly. For example:

• Jackal Language (blame):

  "You make me so angry when you change the meeting time without telling me!" 
  

• NVC Language (ownership):

  "I feel frustrated because I value inclusion and clarity about meeting plans."
  

  or even,

  "When I saw the meeting time changed [inclusion]😤"
  

  ---

Example Messages

Jackal in the Room:

When I see that the jackal is sitting in the meeting and grinning at my frustration,[inclusion]😤 Would you be willing to share what’s going on for you, or am I better off assuming you’ve already judged me 10 different ways?

Singing Humor:

When I hear you singing loudly during a work call,[joy]😊 Would you be open to sharing your setlist? I’d love to join in, though I should warn you, my singing might scare off clients.

Seeking Understanding:

When I see that the deadline has passed and the report hasn’t been submitted,[understanding]🤔 Would you be willing to share what might have prevented it from being sent? If it’s procrastination, I promise I won’t judge—I’ve been there myself!

Making a Well-Formed Request:

When I see that our calls often run 20 minutes over time,[consideration]😤 Would you be willing to co-create a plan to honor the schedule? I wonder if reframing it as "creative brainstorming time" might even inspire us to bring snacks.

---

Well-Formed Requests

A well-formed request is: – Specific: Clearly states what is being requested. – Actionable: Refers to concrete actions the other person can take. – Optional: A request is not a demand, it must allow for choice. -Timebound: Specify when. -Curious: Inviting collaboration and open to mutuality.

Poor request:

You never listen to me!

Better-formed request:

When I see that you interrupted me,[respect]😞 Would you be willing to wait until I’ve finished speaking before responding? Unless it’s about chocolate, then feel free to interrupt.

Even-Better-formed, maybe even Well-Formed request:

When I hear you begin to speak whilst I am speaking,[respect]😞 might it be possible that next time you wish to speak, you raise your hand to let me know? Unless it’s about chocolate, then feel free to interrupt.

---

Implementation Guidelines

The syntax can be manually adopted by users or integrated into chat clients. This section outlines best practices for both manual and automated use.

Manual Use

Users are encouraged to: – Include 1–3 observations where context is relevant. – Preface observations with “When I see that” if it clarifies the message. – Keep observations neutral and minimize judgment. – Make well-formed requests to foster actionable outcomes.

Automation

Chat clients may implement the following features: 1. Syntax Highlighting: Display observations, needs, and feelings in distinct styles for improved readability. 2. Autocomplete: Provide suggestions for needs, feelings, and corresponding symbols as the user types. 3. Filters: Allow users to filter or prioritize messages based on specific needs or feelings.

---

Security Considerations

The proposed syntax does not introduce significant security risks. However, the following considerations should be addressed: 1. Privacy: Users expressing sensitive emotions may be vulnerable to exploitation. Ensure secure transmission and storage of messages. 2. Misuse: Automated processing of NVC messages could lead to misuse, such as sentiment profiling. Developers must implement safeguards against such practices.

---

IANA Considerations

This document does not require any IANA actions.

---

Proposed Feelings-Symbols List

Feeling	Symbol Code	Description	Needs Met/Unmet
Sad	😢	Feeling down or sorrowful	Unmet
Curious	🤔	Seeking clarity or information	Unmet
Happy	😊	Feeling content or joyful	Met
Frustrated	😤	Experiencing annoyance or anger	Unmet
Anxious	😰	Feeling nervous or uneasy	Unmet
Grateful	🙏	Appreciative and thankful	Met
Content	😌	Calm and satisfied	Met
Disappointed	😞	Experiencing letdown	Unmet

---

References

• Rosenberg, M. B. Nonviolent Communication: A Language of Life. PuddleDancer Press.
• Max-Neef, M. A. Fundamental Human Needs and Human Scale Development: An Outline.
• Crocker, D., et al. RFC 5322: Internet Message Format.
• Center for Nonviolent Communication: What is NVC?
• Center for Nonviolent Communication: About Marshall Rosenberg

I wanted to log what I have been playing with.

So, I finally got around to trying out Doom and it feels damm good to be back in Vim keybindings. And its taking a little while to get used to. Thank you https://github.com/hlissner

Alongside that, I am trying to get my literate config file working, start using tangle (again), update my org-ref skills (with version 3) , think about by bibliography. I am quite liking playing with Annotated Bibliography from this gorgeous site: (Noting the Django goodness and parallel AI interest).

Motivational Quote