Nostr notes by Braydon Fuller

RISC-V Mainboard III for Framework 13 laptops launched! ...

2026-05-12T03:08:37Z

RISC-V Mainboard III for Framework 13 laptops launched!

https://deepcomputing.io/deepcomputing-launches-dc-roma-risc-v-mainboard-iii-advancing-open-risc-v-laptop-computing-on-framework-laptop-13/

Awesome!

2026-05-04T17:02:38Z

In reply to nevent1q…fk7s
_________________________

Awesome!

2.4GHz LoRa!? https://partyon.xyz/@nullagent/116499715071759135

2026-05-04T04:16:19Z

2.4GHz LoRa!?

https://partyon.xyz/@nullagent/116499715071759135

Do you remember of it someone with an early dev kit or one of the ...

2026-05-04T03:46:10Z

In reply to nevent1q…md6t
_________________________

Do you remember of it someone with an early dev kit or one of the founders?

Hmmm.. interesting, haven't heard of Modos. Looks like they ...

2026-05-03T20:28:16Z

In reply to nevent1q…3zcs
_________________________

Hmmm.. interesting, haven't heard of Modos. Looks like they are launching soon.

Any software updates in this regard? Also, have you all ...

2026-05-01T20:30:40Z

In reply to nevent1q…enyw
_________________________

Any software updates in this regard?

Also, have you all considered producing monitors (e.g. Dasung Paperlike or BOOX Mira) or collaborating with companies like Framework to work with a broader category of available software?

Any update on full Linux distro support? Or an ability to use ...

2026-05-01T20:21:26Z

In reply to nevent1q…qhuu
_________________________

Any update on full Linux distro support?

Or an ability to use optionally just as an external display?

This upgrade looks great. The modularity of this laptop really ...

2026-04-30T14:54:26Z

In reply to nevent1q…whkp
_________________________

This upgrade looks great. The modularity of this laptop really shines with options for RISC-V mainboards. Looking forward to the next one this summer!

Who knows, perhaps daylightco (nprofile…9ykf) is also partnering with Framework for alternative screen options!?

Shaping up well! ...

2026-04-22T20:40:06Z

Shaping up well!

https://deepcomputing.io/deepcomputing-showcases-dc-roma-risc-v-mainboard-iii-at-framework-nextgen-event

Official Canonical Ubuntu support now also!

quoting
nevent1q…z8xn
👀 RISC-V Mainboard III?

https://frame.work/nextgen

Cool, what tools?

2026-04-17T23:21:34Z

In reply to nevent1q…qkf2
_________________________

Cool, what tools?

What was the hardware necessary and process to create such a ...

2026-04-17T23:20:14Z

In reply to nevent1q…q347
_________________________

What was the hardware necessary and process to create such a model?

👀 RISC-V Mainboard III? https://frame.work/nextgen

2026-04-10T04:06:14Z

👀 RISC-V Mainboard III?

https://frame.work/nextgen

Probably different lists.

2026-03-24T03:00:16Z

In reply to nevent1q…hkrq
_________________________

Probably different lists.

Can you host APKs from many different servers?

2026-03-23T17:24:47Z

In reply to nevent1q…8kjd
_________________________

Can you host APKs from many different servers?

Interesting techniques for declarative web pages without ...

2026-03-18T21:56:40Z

Interesting techniques for declarative web pages without imperative scripting:

https://developer.mozilla.org/en-US/docs/Web/API/View_Transition_API

https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API

https://www.jonoalderson.com/conjecture/its-time-for-modern-css-to-kill-the-spa/

Daniela Brozoni gave a presentation last year at BTC Prague on ...

2026-03-16T22:38:56Z

In reply to nevent1q…9ymd
_________________________

Daniela Brozoni gave a presentation last year at BTC Prague on this topic:

https://www.youtube.com/watch?v=KQu8MLG2zl0

Nostr event nevent1qqsdvm7pnghadlm8hkcfk4pma9lcyr7tuy4avxk7espawfp393lzwgczyqdlnu3emjskxc2fhshnlse5qaawjk02jcru4nu5tmu03wez0hz7zc7ndte

2026-03-16T20:51:01Z

Running RISC-V! 🖖

Congrats to all!

2026-03-11T00:57:38Z

In reply to nevent1q…clpt
_________________________

Congrats to all!

Awesome!

2026-03-11T00:55:37Z

In reply to nevent1q…u5ag
_________________________

Awesome!

The Cosmic Desktop Environment sounds pretty interesting: ...

2026-03-06T18:08:22Z

The Cosmic Desktop Environment sounds pretty interesting: Modular. Customizable. Responsive. Tileable. Wayland. Rust.

https://www.youtube.com/watch?v=fBcfjlFX-xM

New book announced by The Property and Freedom Society: Rothbard ...

2026-03-04T00:40:23Z

New book announced by The Property and Freedom Society: Rothbard at 100

https://propertyandfreedom.org/books/rothbard-100/

Great news!

2026-03-02T05:55:14Z

In reply to nevent1q…l3mq
_________________________

Great news!

Interesting.

2026-02-24T19:18:48Z

In reply to nevent1q…74gy
_________________________

Interesting.

Pretty good interview with Lina Seiche (with Little Hodler): ...

2026-02-13T21:05:19Z

Pretty good interview with Lina Seiche (with Little Hodler):

https://www.youtube.com/watch?v=U-vKgmdYqXg

Will sometimes have this problem, usually on desktop, rotating ...

2026-02-10T15:16:13Z

In reply to nevent1q…gcm7
_________________________

Will sometimes have this problem, usually on desktop, rotating VPN usually works.

Tip: It's possible to configure NewPipe to open YouTube links ...

2026-02-10T02:22:15Z

Tip: It's possible to configure NewPipe to open YouTube links via “App Info (long press app icon) -> Open by default -> Add link”.

50 Years of Computer Architecture (2018) w/ David Patterson at ...

2026-02-09T23:20:42Z

50 Years of Computer Architecture (2018) w/ David Patterson at ISSCC:

https://www.youtube.com/watch?v=NZS2TtWcutc

Portraits of Krste Asanović, Yunsup Lee and Andrew Waterman, and ...

2026-02-09T23:11:21Z

Portraits of Krste Asanović, Yunsup Lee and Andrew Waterman, and origin of RISC-V at CHM:

https://www.youtube.com/watch?v=lbMIuX28d18

Portrait of David A. Patterson (2017) at HLF: ...

2026-02-09T23:07:26Z

Portrait of David A. Patterson (2017) at HLF:

https://www.youtube.com/watch?v=VI9FZNuMC7E

Instruction Sets Should Be Free: The Case for RISC-V (2014) w/ ...

2026-02-08T03:47:49Z

Instruction Sets Should Be Free: The Case for RISC-V (2014) w/ Krste Asanović

https://www.youtube.com/watch?v=vB0FC1DZqUM

Ubuntu 26.04 will support RISC-V (RVA23) and the upcoming ...

2026-02-07T01:05:47Z

Ubuntu 26.04 will support RISC-V (RVA23) and the upcoming SpacemiT K3 processor.

https://canonical.com/blog/spacemit-announces-availability-of-ubuntu-on-k3-k1-series

There is a pretty good interview with David Patterson on ...

2026-02-06T04:05:18Z

There is a pretty good interview with David Patterson on Fridman's podcast. He worked on early versions of RISC and lead Par Lab at Berkeley where RISC-V was initially developed.

“It's more difficult—surprisingly—to come up with a simple and elegant solution.”

https://www.youtube.com/watch?v=naed4C4hfAg

This one: https://github.com/spacecowboy/Feeder

2026-02-05T01:55:13Z

In reply to nevent1q…2vvz
_________________________

This one:

https://github.com/spacecowboy/Feeder

One thing that the Feeder mobile app has done well is to have ...

2026-02-05T01:47:29Z

One thing that the Feeder mobile app has done well is to have compatibility with various formats from RSS feeds to Mastodon. It's a decent means to create follow lists for information still yet beyond Nostr.

For one, the latest announcement at FOSDEM from DeepComputing for ...

2026-02-04T04:41:29Z

In reply to nevent1q…4plg
_________________________

For one, the latest announcement at FOSDEM from DeepComputing for their next release of a mainboard for the Framework 13, looks pretty great.

https://deepcomputing.io/dc-roma-risc-v-mainboard-iii-unveiled-at-fosdem-powered-by-spacemit-k3-for-framework-laptop-13/

Sounds like they're going to be able to move quickly and have a new release every six months with better hardware.

Development has been growing steady with several different development boards (from SiFive and others) and the ratification of the RVA23 profile for general purpose use should be important for software development and support.

Nostr event nevent1qqs89tlqmf3sgsv7k4uz7t8xzg8hnrrnnkn07zs70kz82q6v66r5h8gzyqdlnu3emjskxc2fhshnlse5qaawjk02jcru4nu5tmu03wez0hz7za5zkgf

2026-02-04T01:35:15Z

Recent developments with RISC-V are getting pretty exciting.

Photogrammetry (1997) -> NeRFs -> Gaussian Splats (2023) ...

2026-01-21T16:41:40Z

Photogrammetry (1997) -> NeRFs -> Gaussian Splats (2023)

https://youtube.com/watch?v=T_kXY43VZnk

https://hackaday.com/2023/09/02/high-quality-3d-scene-generation-from-2d-source-in-realtime/

Nostr event nevent1qqsy83ed7mus2lq6sjspqwc848q0hfepyhydck7fcw5wejfh0cwsysgzyqdlnu3emjskxc2fhshnlse5qaawjk02jcru4nu5tmu03wez0hz7zskuack

2026-01-19T02:20:13Z

https://hrf.org/latest/hrfs-bitcoin-development-fund-announces-support-for-22-projects-worldwide/

Reminds me of: https://m.youtube.com/watch?v=5URefVYaJrA

2026-01-19T02:02:57Z

In reply to nevent1q…mcju
_________________________

Reminds me of:

https://m.youtube.com/watch?v=5URefVYaJrA

https://www.youtube.com/watch?v=g1-46Nu3HxQ

2026-01-19T01:46:24Z

In reply to nevent1q…mcju
_________________________

https://www.youtube.com/watch?v=g1-46Nu3HxQ

"You have free rein to explore, reposition cameras after the ...

2026-01-19T01:45:42Z

"You have free rein to explore, reposition cameras after the fact, break spatial continuity, and recombine performances in ways that 2D simply can’t."

https://radiancefields.com/a-ap-rocky-releases-helicopter-music-video-featuring-gaussian-splatting

“The computer can be used as a tool to liberate and protect ...

2026-01-10T16:08:43Z

“The computer can be used as a tool to liberate and protect people, rather than to control them.”

—Hal Finney

https://cypherpunks.venona.com/date/1992/11/msg00108.html

https://youtube.com/watch?v=EiW4lKrMXQ4

2026-01-10T15:56:08Z

https://youtube.com/watch?v=EiW4lKrMXQ4

Great video of a tour of a nuclear power plant: ...

2026-01-01T01:22:21Z

Great video of a tour of a nuclear power plant:

https://youtube.com/watch?v=v0afQ6w3Bjw

Great video on progress on processor manufacturing by ASML: ...

2026-01-01T01:19:48Z

Great video on progress on processor manufacturing by ASML:

https://youtube.com/watch?v=MiUHjLxm3V0

Great video on Phi https://www.youtube.com/watch?v=sj8Sg8qnjOg

2025-12-18T04:56:28Z

Great video on Phi

https://www.youtube.com/watch?v=sj8Sg8qnjOg

Congrats!

2025-12-14T06:14:05Z

In reply to nevent1q…6dm3
_________________________

Congrats!

Not a problem 🤘

2025-12-09T16:51:52Z

In reply to nevent1q…s8md
_________________________

Not a problem 🤘

Sounds good to me.

2025-12-09T16:43:51Z

In reply to nevent1q…pqhe
_________________________

Sounds good to me.

Good to see this topic getting more attention: #naddr1qq…s0dt ...

2025-12-09T16:40:07Z

Good to see this topic getting more attention:

quoting
naddr1qq…s0dt

In Nostr, you are your key. This is beautiful in its simplicity: your identity belongs to you, held by no intermediary, subject to no platform policy. But this radical ownership comes with radical responsibility: lose your private key, and you lose everything. Get it compromised, and an attacker becomes you.

The protocol desperately needs key rotation, but previous proposals have struggled with complexity. They require pre-generated key chains, cryptographic commitments, or trusted hardware, things most users skip until after a crisis.

What if we could solve this through the social layer?

The problem space

There are two distinct scenarios we need to handle:

Key Compromise with Access: You discover your key is compromised, but you still have it

Lost Keys: Your key is gone, device destroyed, forgotten, or otherwise inaccessible

Traditional cryptographic solutions fail the second case entirely. Pre-commitment to a recovery key is the only path, and most users skip that step. But Nostr already has a powerful social graph. What if we used it?

Solution 1: The Compromise Declaration

When you discover your key is compromised but still have access, you can publish a special "compromise declaration" event. This is a loud, permanent, irreversible signal that your key is untrustworthy from this point forward.

The brilliance is in what happens next: you update your profile name to [COMPROMISED] YourName. If an attacker tries to remove it, you add it back. This creates a spam war that helps, because the chaos of competing updates signals to everyone that something is wrong with this account.

Even if the attacker "wins" and controls the account, they're controlling an account that's been permanently marked as compromised. They've vandalized their own prize.

Solution 2: Social Key Rotation

The second solution is more radical: anyone can propose that a key should rotate to a new key, and the community decides if it's legitimate through attestations.

Here's how it works:

Proposal: Anyone (including you with a different key) publishes a rotation proposal

Attestation: Your friends verify out-of-band (Signal, in-person, video call) and publish attestations

Confidence: Clients calculate confidence based on who's attesting and how many

Manual Action: Users see the attestations and manually decide whether to follow the new key

The key insight: if both the old AND new keys sign the proposal, that's strong evidence. With the old key unavailable (lost scenario), sufficient attestations from your social graph can establish legitimacy.

Why this works

These solutions embrace what Nostr does well: social signaling and community verification. They're:

Simple: No pre-planning or complex setup required

Social: Leverages existing trust relationships

Permanent: Creates undeletable audit trails

Backward Compatible: The profile name trick works on every client today

Antifragile: Attacks make the compromise more visible, not less

The non-deletable event range

These proposals introduce events in kinds 65533-65535, which we're proposing as permanently non-deletable. Once you declare a key compromised or propose a rotation, that record stays forever. This prevents attackers from hiding their tracks and gives the community a permanent audit trail.

Moving forward

Perfect security doesn't exist, but perfect can be the enemy of good. These proposals offer practical, implementable solutions that work with human behavior. They turn Nostr's social layer into a security feature.

Key rotation doesn't need to be complex. Sometimes the best solution is to admit that humans are social creatures and build systems that embrace that reality.

NIP-101: Key compromise declaration

draft optional

This NIP defines a method for users to permanently declare that their private key has been compromised.

Abstract

When a Nostr user's private key (nsec) is compromised but they still have access to it, they can publish a special event to warn others that the key should no longer be trusted.

Specification

Compromise declaration event

A compromise declaration uses event kind 65535:
{
  "id": "<32-bytes lowercase hex of the id>",
  "pubkey": "<32-bytes lowercase hex of the compromised public key>",
  "created_at": <unix timestamp>,
  "kind": 65535,
  "tags": [
    ["nonce", "<unique random value>"]
  ],
  "content": "KEY COMPROMISED - DO NOT TRUST SIGNATURES AFTER THIS TIMESTAMP",
  "sig": "<64-bytes lowercase hex of the signature>"
}
Users MAY include a Bitcoin block reference for proof-of-absence:
["block", "<bitcoin block hash>", "<block height>"]
Requirements

Non-replaceable: Kind 65535 is a regular event (not replaceable)

Non-deletable: Relays SHOULD ignore kind 5 deletion requests for kind 65535 events

Unique nonce: Prevents replay attacks

OpenTimestamps Attestation

Users MAY publish a NIP-03 OpenTimestamps attestation (kind 1040) referencing the compromise declaration for cryptographic time proof.

Profile update convention

After publishing a compromise declaration, users SHOULD update their kind 0 metadata event to prepend [COMPROMISED] to their display name:
{
  "id": "<32-bytes lowercase hex of the id>",
  "pubkey": "<32-bytes lowercase hex of the public key>",
  "created_at": <unix timestamp>,
  "kind": 0,
  "tags": [],
  "content": "{\"name\":\"[COMPROMISED] Alice\",\"about\":\"Key compromised at block 850000\",\"picture\":\" https://example.com/pic.jpg\"}",
  "sig": "<64-bytes lowercase hex of the signature>"
}
This creates a visible warning even on clients that don't support this NIP.

Client implementation

Clients supporting this NIP: - MUST check for kind 65535 events when displaying any user profile or content - MUST show a prominent warning if a compromise declaration exists - SHOULD display the compromise timestamp - SHOULD NOT automatically unfollow compromised keys

Security considerations

Attackers self-sabotage by publishing compromise declarations

The spam war over kind 0 updates alerts all users

Services may run bots to maintain [COMPROMISED] profile names

NIP-102: Social key rotation

draft optional

This NIP defines a method for rotating Nostr keys through social attestation, enabling recovery from both compromised and lost keys.

Abstract

Users can rotate from an old key to a new key through community verification. Anyone can propose a rotation, and the community provides attestations to validate it. This works even when the original private key is lost.

Specification

Event kinds

65534: Key rotation proposal (non-deletable)

65533: Key rotation attestation (non-deletable)

Rotation proposal event

Anyone can publish a rotation proposal:
{
  "id": "<32-bytes lowercase hex of the id>",
  "pubkey": "<32-bytes lowercase hex of the proposer>",
  "created_at": <unix timestamp>,
  "kind": 65534,
  "tags": [
    ["p", "<old pubkey>"],
    ["p", "<new pubkey>"],
    ["old", "<old pubkey>"],
    ["new", "<new pubkey>"]
  ],
  "content": "Proposing key rotation for [reason]",
  "sig": "<64-bytes lowercase hex of the signature>"
}
The proposer can be the old key, new key, or any third party.

Attestation Event

Community members publish attestations:
{
  "id": "<32-bytes lowercase hex of the id>",
  "pubkey": "<32-bytes lowercase hex of the attester>",
  "created_at": <unix timestamp>,
  "kind": 65533,
  "tags": [
    ["e", "<rotation proposal event id>"],
    ["attestation", "confirm"]  // or "reject"
  ],
  "content": "Verified via [details]",
  "sig": "<64-bytes lowercase hex of the signature>"
}
MAY include: ["method", "in-person|video-call|signal|telegram|other"]

The old and new keys can also publish attestations to strengthen the signal.

Client implementation

Clients query for kind 65534 events and fetch associated kind 65533 attestations. Calculate weight based on: - Both old+new keys attesting = highest confidence
- Attestations from follows > follows-of-follows > unknown - More attestations = higher confidence

Never auto-follow rotated keys. Require explicit user confirmation.

Example flow

Lost Key: Alice loses her key, creates proposal with any key, shares event ID via Signal, friends attest, others manually update follows

Compromised Key: Alice publishes proposal from old key, signs from new key, dual signature creates high confidence

Security considerations

No automatic actions prevent false rotations

Social verification leverages existing trust

Sybil resistance through web-of-trust weighting

Non-deletable events create permanent audit trail

Relays SHOULD store kinds 65533-65535 permanently and ignore deletion requests.

quoting
naddr1qp…s3p9

I'm going to take a stab at one of the most difficult and important problems in freedom technology: key rotation. Can web of trust help? If so, how?

The canonical use case will be that of a compromised nostr nsec. Suppose Alice wakes up one morning to discover that her nsec has been compromised by a scammer who is sending DMs to all of her contacts asking for sats. She needs the community to know that this nsec is compromised, she needs to spin up a new nsec, she needs the community to know that this is her new replacement nsec, and she needs to do all of this ASAP. How does she proceed?

My guiding principle is something that deserves a name, but doesn't to my knowledge have one, so I'll just call it Occam's Design Principle:

“A product should be made as simple as possible, but not simpler.”

Our solution requires Alice to communicate this catastrophe to people who know her in the real world so that they can relay it to the community. So for starters, she will tell her friends Bob, Charlie, Dave, etc that her old nsec is compromised. Optionally, she will also provide them with a replacement pubkey corresponding to a new nsec, presuming she has created a new one and wishes the community to know it.

Obviously this is an imperfect solution, but there is no perfect solution, and we desire to keep things simple. Improvements will come later.

The Proposed Solution

We require no new event kinds or new NIPs, other than the Decentralized Lists Custom NIP.

Declaration of the Key Rotation Attestation List

Step 1 is to declare a new type of attestation that Bob, Charlie, Dave, etc. can use to effect the attestation described above. This only needs to be done once.

Following the Decentralized Lists NIP, this is achieved via a kind 9998 list declaration event, also called a list header:
{
  "kind": 9998,
  "tags": [
    ["names", "key rotation attestation", "key rotation attestations"],
    ["description", "This is an attestation whereby Bob, who knows Alice in the real world, can alert the community that her nsec has been compromised. There is only one required piece of data, which is the pubkey corresponding to her compromised nsec. For this, he uses the p tag. Optionally, he can also communicate a replacement pubkey, using the optional pubkey_replacement tag, presuming Alice has supplied him with one."],
    ["required", "p"],
    ["optional", "pubkey_replacement"]
  ],
  "id": "<id_key_rotation_attestation_header>"
}
Issue Key Rotation Attestations

Step 2 is for Bob to issue the attestation that Alice's old nsec has been compromised, and optionally to communicate the pubkey that she intends to replace the old one. This is accomplished via a kind 9999 event. It uses the z tag to point to the parent list header (above), the p tag to indicate the compromised account, and (optionally) the pubkey_replacement tag to indicate the new pubkey:
{
  "kind": 9999,
  "tags": [
    ["z", "<id_key_rotation_attestation_header>"],
    ["p", "<alice_pubkey_compromised>"],
    ["pubkey_replacement", "<alice_pubkey_replacement>"]
  ],
  "id": "<id_key_rotation_attestation_item>"
}
Attestation Support

Step 3 is for Charlie, Dave, etc to voice support (or rejection, as the case may be) for Bob's key rotation attestation using any one of several methods, with kind 7 reactions being the recommended method as described in the Decentralized Lists NIP:
{
  "kind": 7,
  "content": "+", // or "-" to downvote
  "tags": [
    ["e", "<id_key_rotation_attestation_item>"]
  ]
}
Alternatively, Charlie, Dave, etc could simply publish duplicate attestations using their own kind 9999 events, identical to Bob's.

Consumption

How are these attestations processed? If the end user wants to check whether alice_pubkey is valid (to the best of the community's knowledge), use this filter:
{
  "kinds": [9999],
  "#z": ["<id_key_rotation_attestation_header>"],
  "#p": ["alice_pubkey"]
}
Reactions to events returned by this filter would also be obtained with the appropriate kind 7 filter and gathered together. All of these results (kind 9999 and kind 7 events) would then be filtered or weighted based upon the end user's personalized trust metric of the event author. For starters, standard personalized PageRank or personalized GrapeRank metrics would do, easily obtained via Trusted Assertions. More sophisticated metrics might use a proximity score between Alice and the event author; authors whom Alice (previously) followed, for example, could be given the highest weighting. Perhaps Alice could even designate, ahead of time, a NIP-51 list of pubkeys that she would trust to make these attestations. But that would be work for the future; no need to support it in the initial rollout.

Future Expansions of the Protocol

Decentralized Lists provides multiple methods for future expansion of the basic Key Rotation protocol as described above. One might, for example, propose adding one or more tags alongside the p and pubkey_replacement tags. Perhaps a tag that indicates the reason for the rotation: lost, compromised, routine rotation, etc. Perhaps a tag to communicate the timestamp that the rotation is intended to take effect. The list of tags is just that: a list, that can be curated by your web of trust! In the event that multiple incompatible expansions are proposed, the community would hopefully (and probably) settle upon one or the other.

Conclusion

A client that implements the above protocol would be providing a great service to the nostr community and would lay a foundation upon which more complex protocols could evolve. In the event that a friend tells you that her account is compromised, this is the client where you would run so you could shout her predicament from the mountaintops. Such a client would therefore need a well designed interface to issue the relevant attestations and reactions. Any WoT Service Providers worth their salt would, in turn, want to listen to the output of this client and work them into their trust metrics. Therefore, such a client would want to use one or more standard methods to communicate the status of any given pubkey: Trusted Assertions, API, and/or some other method.

This would be a great contribution to the upcoming web of trust hackathon. It could be vibe coded, but ideally a team would form around an idea such as this and ensure excellent execution. And of course, I welcome ideas on how to improve this proposal. LFG!

nevent1q…7e7w

quoting
nevent1q…pzay

I'm honestly curious how many people I am going to piss off with this piece

https://untraceabledigitaldissident.com/pgp-nostr-digital-ownership-identity/

ellama works with ollama and emacs

2025-12-09T16:32:25Z

In reply to nevent1q…ydw9
_________________________

ellama works with ollama and emacs

Cool

2025-12-09T04:53:06Z

In reply to nevent1q…ez9x
_________________________

Cool

They also establishment the first compulsory public schools in ...

2025-12-09T04:50:14Z

In reply to nevent1q…wg06
_________________________

They also establishment the first compulsory public schools in America...

This same pattern I think has been known long before social media ...

2025-11-30T20:21:07Z

In reply to nevent1q…8qgs
_________________________

This same pattern I think has been known long before social media feeds or computers, and is the basis for most all propaganda. It's just now become automated.

Where is the Beef? Regulatory Barrier to Entry and Competition in ...

2025-10-23T22:33:00Z

Where is the Beef? Regulatory Barrier to Entry and Competition in Meat Processing

"In short, regulatory extortion tyranny. Inspection regulations are size prejudicial. I know one facility that was ordered closed because it wasn’t processing fast enough. The Food Safety Inspection Service measures its efficiency by pounds inspected per personnel-hour, creating an adversarial discriminatory attitude toward small plants.

In 1906 when Upton Sinclair wrote The Jungle 7 large companies controlled half the nation’s meat processing capacity. After a century of government intervention, 4 now control 85 percent. When licenses and compliance make entering and maintaining an abattoir more burdensome to small facilities than large, concentration and centralization is not an anti-trust issue; it’s a discriminatory regulatory issue."

—Joel Salatin

Video:
https://youtube.com/watch?v=5yStXjQSOR4

Full testimony:
https://judiciary.house.gov/sites/evo-subsites/republicans-judiciary.house.gov/files/evo-media-document/salatin-testimony.pdf

The interesting part from the Trezor news: ...

2025-10-21T18:46:13Z

The interesting part from the Trezor news:

TROPIC01 secure chip now in Trezor! ...

2025-10-21T16:07:49Z

TROPIC01 secure chip now in Trezor!

https://youtube.com/watch?v=EWxAc8wzfFM&t=928s

IMO, web-of-trust key signing attestations and revocation as ...

2025-10-07T22:21:03Z

In reply to nevent1q…6t3d
_________________________

IMO, web-of-trust key signing attestations and revocation as similar to PGP.

Funny, the service here can be better than many "fancy" ...

2025-10-03T21:07:05Z

In reply to nevent1q…cpxl
_________________________

Funny, the service here can be better than many "fancy" restaurants that seem dumbfounded by orders for just hamburger patties.

What stand is that?

2025-10-01T21:09:14Z

In reply to nevent1q…r022
_________________________

What stand is that?

World record 70 meter skateboard drop in: ...

2025-09-27T04:09:08Z

World record 70 meter skateboard drop in:

https://www.redbull.com/int-en/sandro-dias-ultimate-skate-ramp

Great that skating and surfing are also a part of this.

2025-09-27T02:33:20Z

In reply to nevent1q…4e38
_________________________

Great that skating and surfing are also a part of this.

Interesting interface for contracts. #nevent1q…h5a6

2025-09-27T01:57:37Z

Interesting interface for contracts.

quoting
nevent1q…h5a6
Miniscript in npub1cvqlzvmjercdn0ypsmv8f7j9lge6ahsnueh5rparh53wuswftv4q49yjt3 (npub1cvq…yjt3) . Wow i love this wallet

One of the first use cases (1989) for blind-signatures was for ...

2025-09-25T04:49:32Z

In reply to nevent1q…me2e
_________________________

One of the first use cases (1989) for blind-signatures was for toll roads in the Netherlands. Aaron van Wirdum (nprofile…9c7d) mentions it in his book The Genesis Book (p. 105).

Also, so many new cars—almost all of them—come with a ...

2025-09-25T04:33:30Z

In reply to nevent1q…me2e
_________________________

Also, so many new cars—almost all of them—come with a telematics module with a cellular modem that can be used for live triangulation of position from towers. Wire diagrams often detail their location and can be disabled, however it's unclear if vehicle warranty agreements might require it to be functioning for qualification.

Live vehicle tracking with many Automated License Plate ...

2025-09-25T04:18:26Z

Live vehicle tracking with many Automated License Plate Recognition (ALPR) devices.

quoting
nevent1q…v5rx
https://youtu.be/vWj26RIlN_I

Both System76 and Purism have hardware with Intel ME disabled. ...

2025-09-22T13:46:36Z

In reply to nevent1q…8tka
_________________________

Both System76 and Purism have hardware with Intel ME disabled.

https://puri.sm/posts/deep-dive-into-intel-me-disablement/

https://support.system76.com/articles/intel-me/

Yup! An estimate of an average annual stock increase of 2% is the ...

2025-09-14T16:34:50Z

In reply to nevent1q…ggp0
_________________________

Yup! An estimate of an average annual stock increase of 2% is the best I've found.

https://vongreyerz.gold/the-biggest-misconception-with-regard-to-gold-high-stock-to-flow-ratio-is-the-most-important-characteristic-of-gold

Curious...

2025-09-10T23:15:39Z

In reply to nevent1q…drl2
_________________________

Curious...

View and listen analytics are not a great metric... (as example ...

2025-09-10T23:01:47Z

In reply to nevent1q…acla
_________________________

View and listen analytics are not a great metric... (as example with bots from the video).

Are these linked from the Daylight website (I keep forgetting ...

2025-09-10T22:59:05Z

In reply to nevent1q…72w4
_________________________

Are these linked from the Daylight website (I keep forgetting it's address)?

What would analytics provide? Does not seem useful.

2025-09-10T22:51:52Z

In reply to nevent1q…ex0f
_________________________

What would analytics provide? Does not seem useful.

Has anyone been successful with installing Debian, Fedora or ...

2025-09-10T22:49:33Z

In reply to nevent1q…hrqs
_________________________

Has anyone been successful with installing Debian, Fedora or another distro on DC-1?

Fork Chromium? Firefox and/or Brave.

2025-09-08T22:07:18Z

In reply to nevent1q…ffem
_________________________

Fork Chromium? Firefox and/or Brave.

Nostr event nevent1qqsf0r7j56l0w3k25rqryewel2j4klvj9j9sw9evf40pusefln8xgkczyqdlnu3emjskxc2fhshnlse5qaawjk02jcru4nu5tmu03wez0hz7zsyj0a0

2025-09-08T21:46:34Z

Sol LeWitt's "Incomplete Open Cubes"

Thanks and enjoy!

2025-09-05T04:33:47Z

In reply to nevent1q…hxst
_________________________

Thanks and enjoy!

Paper with coordinates for the tetrahedron: ...

2025-09-03T01:39:00Z

In reply to nevent1q…gspl
_________________________

Paper with coordinates for the tetrahedron:

https://arxiv.org/pdf/2506.19244

Article on Quanta Magazine: ...

2025-09-03T01:28:26Z

In reply to nevent1q…gspl
_________________________

Article on Quanta Magazine:

https://www.quantamagazine.org/a-new-pyramid-like-shape-always-lands-the-same-side-up-20250625/

Nostr event nevent1qqswceyhp3fa5azcyevv9ynlhv508mn4ps3shv8mdv0fprdqacellagzyqdlnu3emjskxc2fhshnlse5qaawjk02jcru4nu5tmu03wez0hz7z2fctwx

2025-09-03T01:25:58Z

A tetrahedron stable on only one surface!

Yup!

2025-09-01T12:50:30Z

In reply to nevent1q…tnvt
_________________________

Yup!

There is now a RaspberryPi Development Kit available for the ...

2025-09-01T01:45:47Z

There is now a RaspberryPi Development Kit available for the TROPIC-01 secure element as well as standalone USB!

https://tropicsquare.com

Quite a different direction than the original goals of the ...

2025-08-29T22:49:09Z

Quite a different direction than the original goals of the Andriod team.

quoting
nevent1q…7wgw
Google plans to begin verifying the identity of all developers who distribute apps on Android, even if it's outside the Play Store, starting September 2026

https://developer.android.com/developer-verification

"We're currently working with a major OEM towards future ...

2025-08-29T22:42:34Z

"We're currently working with a major OEM towards future generations of their devices meeting our requirements and providing official GrapheneOS support."

quoting
nevent1q…5krd
We've received the Pixel 10 we ordered and have confirmed it supports unlocking, flashing another verified boot key and locking again.

Our Pixel 10 support will likely only be possible to complete after we finish porting to Android 16 QPR1 which is being released in September.

A second Pixel 10 we ordered has arrived at a package forwarding service in the US to be shipped to a country without Pixels available.

We'll order a Pixel 10 Pro (XL) and Pixel 10 Pro Fold for our main device testing farm today too since we'll supporting all 4 variants of them.

Previously, we likely would have been able to implement support for the Pixel 10, Pixel 10 Pro and Pixel 10 Pro XL in the next 48 hours. However, we likely need to wait for Android 16 QPR1 and our port to it since we don't expect a Pixel 10 device branch will be pushed to AOSP.

We've received confirmation that Android is switching to having quarterly releases across devices. There will be 3 quarterly and 1 yearly release of Android and the Android Open Source Project. Monthly releases are Pixel exclusive and will have far fewer changes than before.

Previously, only Pixels shipped the quarterly releases in practice. Other OEMs will now be pushed to ship those, but not the monthly releases which are now officially Pixel exclusive. Please note monthly Android Security Bulletins are a different thing from the monthly releases.

Android Security Bulletins are backports of a subset of patches deemed High/Critical severity to older Android releases. That currently means the initial yearly releases of Android 13, 14, 15 and 16 without the monthly/quarterly updates for those. This will need to change now.

The changes are acceptable for us and we can deal with it. We're currently working with a major OEM towards future generations of their devices meeting our requirements and providing official GrapheneOS support. #GrapheneOS on both Pixels and these future non-Pixels will be fine.

Pixels are still the most secure Android devices and the only ones combining a high level of security with proper support for an alternate OS. However, it's clear they don't value alternate OS support and won't remain the best devices for GrapheneOS once we have official ones.

We could continue supporting future Pixels such as the Pixel 11 and Pixel 12 after we have another option available but we won't depend on them continuing to provide alternate OS support. It's good that the Pixel 10 still provides it since our alternative is a year or two away.

Seems increasingly likely that Google might lock Pixel ...

2025-08-26T01:55:24Z

In reply to nevent1q…v3pl
_________________________

Seems increasingly likely that Google might lock Pixel bootloaders to only their distros...

If a Nostr relay requires AUTH—as based on a paid ...

2025-08-13T01:14:41Z

In reply to nevent1q…6a48
_________________________

If a Nostr relay requires AUTH—as based on a paid subscription—it would be one way a pubkey/npub could be associated with a group ID (the only metadata available, afaik). The other would be based on an IP, but that is similar to Signal et al (and mitigated with VPNs and etc). E-cash 'blind signatures' seem to be the best solution for relay 'subscriptions' without knowledge of a pubkey. It was designed for this scenario, even if from 1981.

Yup! It's also a bit of both. It certainly did not fail at ...

2025-07-17T23:38:58Z

In reply to nevent1q…gpyg
_________________________

Yup! It's also a bit of both. It certainly did not fail at all, there are many wins. It's just starting.

The 'no connection needed on the sender' part is ...

2025-07-17T18:11:47Z

The 'no connection needed on the sender' part is interesting.

quoting
nevent1q…znr5
sending bitcoin over bluetooth between bitchat android and iphone. both have a native cashu ecash wallet built in.

the ecash travels directly from phone to phone. the sender needs no internet. like instant and untraceable digital cash.

it's going to be insane. work in progress with thesimplekid (nprofile…h6wz) , zeugmaster (nprofile…zp7p), erik (nprofile…kl22) , gudnuf (nprofile…xy6n) , dvdc (nprofile…n7a8) et al.

Wondering if immediate mode could provide some motivation to ...

2025-07-16T18:09:03Z

In reply to nevent1q…6qeu
_________________________

Wondering if immediate mode could provide some motivation to render less (and more stable) which might be useful and an improvement to UX. Going to click on a link or button and then having it move because something loaded and changed its position can be a little frustrating. Similarly, navigating to an anchor (like a comment or sub-heading) and then it changes position as the page loads.

Try with (w/ pre-release toggle): ...

2025-07-11T20:41:33Z

In reply to nevent1q…3pmk
_________________________

Try with (w/ pre-release toggle):

https://github.com/parres-hq/whitenoise_flutter

Doesn't Keychat use ecash 'blind signatures' stamps ...

2025-07-10T20:54:49Z

In reply to nevent1q…h8gn
_________________________

Doesn't Keychat use ecash 'blind signatures' stamps also?

How's White Noise going to address spam on relays if only the group ID is known? Auth would reveal metadata and a different emphemeral key use used to sign each event? Blind signatures seem ideal here.

This is one of the few books that has the history of Tor correct ...

2025-07-10T05:07:09Z

This is one of the few books that has the history of Tor correct with origins beginning with Chaum mixnets, Cypherpunk remailers, Mixmaster, Free Haven... and NRL Onion Routing.

NRL is sometimes cited as the origin. They built on previous ideas and expanded it to TCP/IP. Folks from Free Haven later joined and implemented it into Tor, combined with other prior research and development.

Great work! Looking forward, lots of opportunity.

2025-07-09T21:22:47Z

In reply to nevent1q…gp4m
_________________________

Great work! Looking forward, lots of opportunity.

Should be a good one! #nevent1q…wryn

2025-07-09T21:01:40Z

Should be a good one!

quoting
nevent1q…wryn
dispatch - White Noise (npub1wht…r3ec) - tomorrow @ 1600 utc

rhr - friday @ 1630 utc

dispatch - pip (nprofile…fq84) - friday @ 1930 utc

https://citadeldispatch.com

https://rhr.tv

So much more possible too with MLS! #nevent1q…x69g ...

2025-07-09T20:56:31Z

So much more possible too with MLS!

quoting
nevent1q…x69g

🚀 It’s time. White Noise is live.

The encrypted messenger for anyone who values privacy, freedom, and real control over their conversations. No phone numbers. No emails. No compromises.

Download it. Explore it. Tell us what’s broken or missing. We’re building this with you.

👉 Android available now
📱 iOS coming soon (under review)

https://www.whitenoise.chat/download

quoting
nevent1q…q5ug
Message Layer Security (MLS) is how subscriber lists could work with Nostr! AND greatly improved DMs. Lots of possibilities. It could become as significant as TLS/HTTPS was to HTTP.

nevent1q…nfa0

Resources:

https://www.rfc-editor.org/rfc/rfc9420.html

https://github.com/rust-nostr/nostr/tree/master/mls/nostr-mls

https://www.whitenoise.chat/

False positives could be problematic, there is always some ...

2025-07-05T12:35:31Z

In reply to nevent1q…wpxe
_________________________

False positives could be problematic, there is always some probability. With matching 'what to send' (as with bitcoin) a false positive would just an event (tx) sent that shouldn't have been (easy to check and discard). With matching 'what not to send' a false positive would mean a missing event. Also, negentropy I think handles this case, bandwidth efficiency, already very well with set-reconciliation (NIP-77). Might not apply to the scenario you describe, however.

Upon further thought, LLMs may not be great for spam mitigation ...

2025-06-27T18:18:36Z

Upon further thought, LLMs may not be great for spam mitigation as it could be computationally more difficult receiving/filtering than sending in bulk. Though could be useful in latter steps. Thus ecash/lightning I think will thus be essential, outside WoT systems.

What next Mr. Beast gives a million to free software projects? ...

2025-06-27T15:00:27Z

In reply to nevent1q…eld6
_________________________

What next Mr. Beast gives a million to free software projects? 😎

Trivial-ish, there are a whole lot of other issues that can ...

2025-06-25T22:18:29Z

In reply to nevent1q…7jpv
_________________________

Trivial-ish, there are a whole lot of other issues that can surface in the process, probably not in regards to the UI though, as it's decoupled. So that is good.

Two I've noticed awhile ago: centralization of (and missing) NIP-65 info at relays (could be a whole research project) and a need for broader support for negentropy for greater efficiency with hundreds to thousands of relays to communicate (and not always online).

Even though, I don't think outbox has been implemented yet in ...

2025-06-25T22:00:57Z

In reply to nevent1q…akme
_________________________

Even though, I don't think outbox has been implemented yet in notedeck? Just a local relay to sync to, if I remember correctly.

Nostr browser (for apps), outbox and crossplatform I think are ...

2025-06-25T21:56:48Z

In reply to nevent1q…hzlw
_________________________

Nostr browser (for apps), outbox and crossplatform I think are the major distinguishers.