Squiggs

Public Key

npub169wexa9lrqpq5k7fkjrfkcrng30acuu02srjyhcp7pyhgqhzumpq0hvfmu

Profile Code

nprofile1qqsdzhvnwjl3sqs2t0ymfp5mvpe5gh7uww84gpeztuqlqjt5qt3wdsspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsj288ml

Publishing to

nostr.mom

relay.damus.io

nos.lol

Author Public Key

npub169wexa9lrqpq5k7fkjrfkcrng30acuu02srjyhcp7pyhgqhzumpq0hvfmu

Show more details

Last Notes

2026-03-16 09:49:16 UTC

#nevent1q…knjk

2026-03-11 16:56:33 UTC

#nevent1q…lcyr

2026-02-07 10:49:57 UTC

- reply

I like Heltec V3s as they are inexpensive, widely available and each unit can be configured to any of the world region frequencies.
I print my own cases, but V3 cases are widely available too.
I actually prefer MeshCore to Meshtastic, but the V3 is supported by both.

2026-01-30 12:19:08 UTC

- reply

2026-01-14 16:36:33 UTC

- reply

I've also found MeshCore to be a better LoRa messaging system than Meshtastic and welcome each integration as useful progress.

2026-01-13 21:49:40 UTC

City fox in London
https://nostr.download/b5a5f9e048cf8e746087650c7f7bd253fcc13186e5a8adefb0370f08eedbead1.mp4

2025-12-14 09:49:14 UTC

- reply

I wonder whether there's a "nothing stops this train" aspect to all centralised systems, and to state systems in particular.
The state may even realise that ever increasing surveillance ends up doing more harm than good, but by its nature, it's an impersonal system, and has no effective means to bring about stronger communities (where it tries, it's counterproductive). So, when attempting to solve problems, it just keeps pulling harder on the system levers it can control, until eventually something breaks.

2025-12-13 09:36:23 UTC

- reply

Agree that they are obvious, although in a busy area if you aren't looking out for them I think it's easy to get picked up on the cameras before noticing and avoiding.
I think this stage is part testing, part picking up any wanted people they detect (plain clothes police came back and forth from crowd into the van), and a large part normalisation to mass public-space facial-recognition monitoring.

2025-12-13 09:28:05 UTC

- reply

Yeah, it's all part of the net that's being assembled around us. If a phone's IMEI, IMSI etc gets linked to the incoming digital ID and the increasing volume of facial data, the correlation step will be much lower overhead, and so I expect much more pre-correlated data will be gathered.

2025-12-13 00:18:17 UTC

Seeing more and more of these mobile facial recognition units around London. https://nostr.download/2904594e7f0fb0ffb7c0a9cb0bd5a34166a709d81389cea9cf2ba889a710a750.mp4

2025-12-10 23:29:33 UTC

- reply

Can't zap this post. Message says wallet not properly configured.

2025-12-07 14:03:45 UTC

- reply

Should really be working now.
I tested it by zapping my own post 😳, which would normally be bad form.

2025-12-06 20:41:11 UTC

- reply

Might be working now

2025-12-05 11:47:48 UTC

- reply

Yes, I need to fix that 😳

2025-12-04 19:15:04 UTC

https://nostr.download/fbb04332989f1bc89175c16b07e4dc5592b7b582b211839ac2158a97694c3110.jpg
@nprofile…6x8w now hosts an off-grid, solar MeshCore room server and repeater, building up decentralised communication capability.
#meshradio #meshcore

2025-11-08 17:33:26 UTC

- reply

It feels like diffusion language models might suit this use case.

2025-09-24 14:54:00 UTC

Any mesh radio notriches using MeshCore?

2025-08-26 06:30:26 UTC

- reply

Subtle zap! messaging 👍⚡

2025-08-26 06:11:09 UTC

- reply

$123456

2025-07-07 23:32:42 UTC

- reply

LoRa's long range but low bandwidth already enables telemetry messages from as far as orbiting satellites with $20 hardware (https://tinygs.com/).
For motivated, low time preference users, such as Nostriches, I think there must be a way to hyper-efficiently encode/decode longer text messages using local language models, trading work at sender and receiver for better transmission efficiency, mitigating bandwidth constraints and enabling far wider mesh coverage.
Whether or not it can be made to work, I'm finding it interesting to explore https://njump.me/nevent1qqsdpgmuuxq7wl3w8nmjlj75h7tpjm6t65ce7g5jfsdkwx603a6y6ccpzpmhxue69uhkummnw3ezumt0d5hsygx3tkfhf0ccqg99hjd5s6dkqu6ytlw88r65qu397q0sf96q9chxcgpsgqqqqqqs5pjyw6

2025-06-04 14:00:25 UTC

- reply

It starts with an gentle interest in mesh radio, ecash etc and soon you are on your way to being hardcore like this guy;
https://youtu.be/HAX8GFn5uCI

2025-05-21 10:37:42 UTC

- reply

Big fan of Never Too Small

2025-04-20 09:49:10 UTC

- reply

Maybe a book cover image provides deeper context than just the book title in text form?
The AI should recognise the book cover image and base the chat on its trained knowledge of the book's contents and related concepts.
Is there a good first prompt?

2025-01-08 10:21:32 UTC

- reply

🍊

2024-10-31 08:14:05 UTC

- reply

As I'm from the UK I have 868MHz nodes, so anywhere I go in Europe there's a good chance of picking up a mesh. I usually seek out a sightseeing spot like a tall building for the line-of-sight range.
Tall buildings are good but balloons are better. Back in the UK when someone had a balloon up over the English Channel, it got me connected all the way over to the Netherlands.
Maybe we could have a Nostr balloon node at some point!
https://image.nostr.build/19efc4a083a89ba2e0663ed2b9b52f656e853aa7137367483d87d7fd23a4d049.jpg
https://image.nostr.build/3c13e8c401e16195027397c7e3056c4ef666cffd55a85bc9157b38877e4d6168.jpg

2024-10-31 07:49:18 UTC

- reply

Great work! Is this going to be a regular activity at events?
I picked a couple of nodes after Nostriga when sightseeing from the roof of the
Latvian Academy of Sciences.

2024-10-20 05:03:53 UTC

- reply

Interesting to hear these reactions still happen. My dad would spend a couple of months a year in rural Japan in the 1960s and 70s, setting up factories. He thought in many cases he was the first white man they had seen, and sometimes children would run away in fear at the unexpected sight of a strange giant walking along a lane. Back then, after losing so much weight on the first trip, he would take blocks of cheese and some tinned western food to sustain him. Now, even living outside London in the UK, there are stores with a choice of natto varieties.
Nostrasia was my first trip to Japan, and I only visited cities, so a very different experience - I absolutely loved the place, the people and the culture, and plan to come back to see more of the country. I wish I had visited while my dad was still alive. We still have a number of handmade gifts from people my dad worked with all those years ago.

2024-08-27 07:10:30 UTC

- reply

An aspect of this compression approach I'm exploring which I've failed to describe properly so far is the potential uses of the local LLM.
In an abstract sense, I'm thinking of LLMs as being stores of vast amounts of 'work' undertaken during their training, which can be hooked into as a shared reference point by both sender and receiver.
When the sender uses the local LLM to find a semantic equivalent of their message (which I see as reducing the entropy), parameters such as temperature could be set to be as deterministic as possible. Then when the same LLM under the same parameters is used during decoding, I'm hoping that a small set of information such as first word, most frequently occuring words can be used to dramatically cut down the decoding search space.
I intend to experiment with combinations of these approaches for efficiently narrowing down the decode search space. It may be that different message sizes and content types benefit from different encoding types.
I'm no expert in any of this, just an enthusiast. It's likely that others could do this better, or have already done so but not applied it yet. Feedback welcome.

2024-08-09 13:14:18 UTC

- reply

I finally found the clip from "Contact" (the film of Carl Sagan's book) that I have been looking for - https://youtu.be/yCkD5GOjvx8

2024-08-09 11:25:50 UTC

- reply

# Semantic Ultra-compression for Low Bandwidth Communication
## Concept Overview
In any communication system, there is work required to transmit information. This work is distributed among three main components:
1. Sender
2. Transmission System
3. Receiver
Traditional high-bandwidth systems place most of the workload on maintaining the transmission infrastructure, with minimal effort required from senders and receivers. However, in very low-bandwidth scenarios (e.g., mesh radio networks), this approach becomes impracticable.
The Semantic Ultra-compression project aims to shift the workload from the transmission system to the senders and receivers, enabling effective communication over extremely limited bandwidth channels.
## Key Components
1. Shared Reference Dictionary
2. Encoding Process
3. Transmission
4. Decoding Process
## Process Flow
1. Pre-setup:
- All participants download a shared large language reference dictionary and the encoding/decoding application.
- This represents a significant upfront investment of time and resources by all users.
2. Encoding (Sender's work):
- Sender types a message
- App finds closest semantic matches in the reference dictionary
- Sender manually reviews and selects best combinations to convey intended meaning
- This process may involve multiple iterations and careful consideration by the sender
- References are hashed into a Merkle Tree
3. Transmission:
- Only the top Merkle Tree hash is transmitted
- This minimises the work required by the low-bandwidth transmission system
4. Decoding (Receiver's work):
- Receiver's app receives the Merkle Tree hash
- App performs intensive computational work to reconstruct the message:
* It systematically tries combinations from the shared reference dictionary
* Each combination is hashed and compared to the received Merkle Tree hash
* This process continues until an exact match is found
- The receiver may need to wait a significant amount of time for this process to complete
- Once a match is found, the app reconstructs the exact message approved by the sender
- The receiver reviews the decoded message to understand the sender's intended meaning
This flow emphasises that both sender and receiver invest significant time and computational resources in the communication process, offsetting the limitations of the low-bandwidth transmission system. The decoding process, while computationally intensive, results in an exact reconstruction of the sender's approved message, ensuring fidelity of communication.
## Benefits
1. Enables communication over extremely low-bandwidth networks
2. Preserves exact semantic meaning of messages as approved by the sender
3. Utilises participant resources instead of transmission infrastructure
4. Ensures perfect reconstruction of the original message, eliminating ambiguity
## Challenges
1. Requires significant pre-setup (dictionary download)
2. Encoding process requires manual effort from the sender
3. Decoding process is computationally intensive and potentially time-consuming
4. Balancing compression ratio with semantic accuracy during the encoding phase
5. Ensuring the shared dictionary is comprehensive enough for various communication needs
## Optimization Strategies
While the basic conceptual model demonstrates the core idea of shifting work from the transmission system to senders and receivers, it presents extreme inefficiencies, particularly in the decoding process. Here are some strategies to address these inefficiencies:
### Partner Merkle Tree Hash
The primary optimization involves the sender's app generating a partner Merkle Tree hash that accompanies the main message hash. This partner hash is designed to be low-work to resolve and contains information to drastically reduce the permutations needed to decode the main message hash.
#### Concept:
1. Divide the shared dictionary into multiple sections (e.g., 1024 sections).
2. These sections could be organised:
- Randomly (to distribute common phrases)
- By semantic association (grouping related concepts)
- By frequency of use (to optimise for common communications)
3. The encoding process tracks which dictionary sections were used.
4. A partner Merkle Tree is created from this section usage information.
5. Both the main message hash and the partner hash are transmitted.
#### Decoding Process:
1. The receiver's app first decodes the partner hash (low-work process).
2. This reveals which dictionary sections were used in encoding.
3. The app then only needs to check permutations within these identified sections to decode the main message hash.
#### Benefits:
- Drastically reduces the number of permutations to check during decoding.
- Maintains the low-bandwidth transmission requirement.
- Preserves the security and privacy aspects of the hashing system.
### Additional Optimization Ideas:
1. **Adaptive Dictionary Sections**: Dynamically adjust section sizes based on usage patterns to further optimise common communications.
2. **Layered Hashing**: Use multiple layers of partner hashes for extremely large dictionaries, each layer providing more specific guidance for the decoding process.
3. **Semantic Tagging**: Include broad semantic categories in the partner hash to help guide the decoding process towards relevant dictionary sections more quickly.
4. **Frequency Hints**: Incorporate usage frequency data in the partner hash to prioritise checking of more commonly used phrases or words.
5. **Error Correction**: Implement a simple error correction system in the partner hash to allow for some transmission errors without completely failing the decoding process.
## Potential Applications
1. NOSTR protocol over LoRa radio
2. Disaster communication scenarios
3. Censorship-resistant messaging systems
This concept leverages the motivation of specific user groups (e.g., NOSTR and mesh radio network users) who are willing to invest more effort in the communication process to overcome bandwidth limitations. The significant work required by both senders and receivers makes this approach suitable only for scenarios where traditional high-bandwidth communication is unavailable or undesirable. However, it guarantees exact reconstruction of the sender's intended message, making it reliable for critical communications in challenging environments.

2024-08-06 08:52:46 UTC

- reply

I've started to work on a variation of this idea, on a hobby basis.
Seeing what's happening in the world, I think I need to step up my efforts.

2024-06-17 13:49:16 UTC

- reply

By default, ISPs where I am are required to block that link as it's Russia-based RT, ostensibly to keep us 'safe' from mis/disinformation. Actually, I don't know many people who take news stories from any source on trust anymore.
Once I got to the article, I saw it references western sources for it's information anyway, and there's no attempt to block those. The attempted block just makes me more aware of the efforts to manage my perception.

2024-03-02 18:50:24 UTC

Just noting an idea that dropped into my head as I experiment with Meshtastic over LoRa, which I'm (almost certainly naively) thinking could allow "compressed" message size such that consumption of relay storage is dramatically reduced and transmission could be supported even on low-bandwidth decentralised mesh networks over LoRa radio...
- Train a custom, single-purpose LLM for a type of Dictionary-based Redundancy Compression (DbRC), such that messages can be losslessly described by the minimal-size format of reference(s) to the model (base best-match reference plus modifier references to refine it to an exact match)
- Clients and Relays can download a copy of the DbRC LLM (existing practicality of local voice recognition data files on mobile makes me think this could be too)
Each message is optionally passed as the reference(s) to the shared DbRC LLM
- Clients/relays without a local copy of the LLM can decompress (and compress, if this would ever be worthwhile?) via a service (assuming they have sufficient bandwidth)
I know basically nothing about compression approaches or custom LLMs, so is this even practicable?
Has the challenge of Nostr over low-bandwidth mesh networks been solved already?

2024-01-13 20:19:17 UTC

- reply

Was your sump pump overwhelmed too quickly to move precious items?
Or no sump pump at all?
https://jenkinsrestorations.com/the-basics-and-the-benefits-of-a-sump-pump
Really sorry to hear about this. Thanks for everything you do.

2023-11-02 07:46:56 UTC

@npub1sn0…jdv9 🫂

2023-10-31 01:52:19 UTC

- reply

Signs up saying no Halloween events on Shibuya streets. Last night there were some access restrictions.

2023-10-30 13:14:11 UTC

- reply

I'm back at my hotel (phone died). It looks like the building and sign in Leo's photo

2023-10-30 12:39:16 UTC

- reply

I think there's more than one Belle Salle on Tokyo. I'm at the Sumitomo Fudosan Shibuya First Tower Belle Salle now, and can't see anything matching your photo - have I got the right Belle Salle?

2023-10-27 14:02:07 UTC

- reply

Some Kato track in there? https://www.katomodels.com/
I'm flying over the Black Sea on my way to Nostrasia right now - hoping to check out some of the local model railway culture while I'm there.

2023-08-05 08:56:35 UTC

- reply

"Deletion-compliance relay crawlers" sending then deleting notes from random nsecs could do a reasonable job of flagging relays that didn't comply (whether they claim to or not).
Couldn't detect "logical deletion" this way, though. So likelihood of a copy somewhere is high.

2023-07-16 10:08:33 UTC

- reply

I signed up a while back but no acknowledgement or confirmation, so I can't book flights or accommodation as I've no way of knowing if I have a spot reserved.

2023-07-16 10:03:33 UTC

- reply

Same for me. Can't book flights and accommodation until I get confirmation

2023-04-20 20:28:20 UTC

- reply

... using self-hosted, decentralised AI

2023-02-26 10:26:54 UTC

- reply

I haven't thought this through yet, but maybe encrypted border wallet entropy grid sets fit in here somewhere?