HN user

bergie

8,209 karma

Sailor, hacker, and an occasional adventurer. Author of Create.js (http://createjs.org/) and NoFlo (http://noflojs.org/).

More on http://bergie.iki.fi and https://lille-oe.de/

[ my public key: https://keybase.io/bergie; my proof: https://keybase.io/bergie/sigs/94Ea8rkF51hWAkqI5uBmafa01SABlUwEamPyaPswvoM ]

Posts318
Comments1,466
View on HN
reticulum.network 15h ago

Distributed Development with Reticulum

bergie
3pts0
bergie.iki.fi 17d ago

Reticulum Is Interesting

bergie
5pts1
www.leash.ax 21d ago

Leash: Browser Without URL Bar

bergie
2pts2
bergie.iki.fi 1mo ago

Development Dependencies Considered Harmful

bergie
2pts0
reticulum.network 1mo ago

Distributed Development

bergie
2pts0
solar.lowtechmagazine.com 3mo ago

Rediscovering the Handcart

bergie
3pts0
signalk.org 6mo ago

Off-grid boat telemetry with Meshtastic

bergie
2pts1
signalk.org 10mo ago

Off-Grid Boat Data with Signal K and Meshtastic

bergie
3pts0
www.theatlantic.com 1y ago

The GPT era is already ending

bergie
55pts28
www.ben-evans.com 2y ago

A Month of the Vision Pro

bergie
2pts0
arstechnica.com 2y ago

I worked exclusively in Vision Pro for a week

bergie
4pts0
www.theverge.com 2y ago

2023 in social media: the case for the Fediverse

bergie
3pts0
arstechnica.com 2y ago

280M e-bikes are slashing oil demand far more than electric vehicles

bergie
7pts0
arstechnica.com 2y ago

Musk shut off Starlink to prevent Ukraine attack on Russian ships

bergie
30pts22
www.stilldrinking.org 3y ago

Tech Erosion

bergie
5pts0
bergie.iki.fi 3y ago

Flow-Based Programming, a way for AI and humans to develop together

bergie
166pts111
arstechnica.com 3y ago

Apple plans to support sideloading and third-party app stores by 2024

bergie
7pts1
blog.kodigy.com 3y ago

The state of Flow-based Programming

bergie
115pts51
arstechnica.com 4y ago

Google Play Store will promote tablet apps with “quality” ranking

bergie
1pts0
www.ben-evans.com 4y ago

Tech Questions for 2022

bergie
4pts0
www.antipope.org 5y ago

Lying to the Ghost in the Machine

bergie
63pts36
bergie.iki.fi 5y ago

Building an IoT Dashboard with NASA Open MCT

bergie
1pts0
arstechnica.com 5y ago

Treasury nominee Yellen is looking to curtail use of cryptocurrency

bergie
10pts23
blog.jim-nielsen.com 5y ago

Cheating Entropy with Native Web Technologies

bergie
1pts0
www.weforum.org 5y ago

Germany drafting law to give people the legal right to work from home

bergie
4pts0
bergie.iki.fi 8y ago

Managing a developer shell with Docker

bergie
1pts0
bergie.iki.fi 8y ago

MicroFlo on ESP8266: measuring air quality

bergie
2pts0
bergie.iki.fi 8y ago

Building an IoT Dashboard with NASA Open MCT

bergie
3pts0
medium.com 8y ago

Publishing and reusing web widgets as Web Components

bergie
1pts0
business.f-secure.com 8y ago

Tips for Business OpSec [comic]

bergie
2pts0

You still need a build tool, and that tool is likely broken if you need to return to the project in a year or two.

TypeScript benefits can be had without a build step by leveraging JsDoc.

Starlink has worked great for us so far from Europe to Polynesia. Prices keep going up, so would be nice if the service had actual competition.

The backups are sadly becoming trickier, as fewer and fewer carry SSB radios or operate shore stations.

And yet we do have SSB, and also an Inreach as backups. You never know when Elon wakes up and decides he doesn't like sailors.

I resisted WhatsApp until we started cruising with our sailboat. So many processes require WhatsApp. In many places you can't do customs and immigration without it.

Well, maybe not 100% true. There might still be the remnant of an old paper-based process around, but since nobody uses it, it would be a recipe for spending days queuing in random offices.

Once we're back in Europe, it will be a happy moment when I can finally uninstall the app.

I think the reasonable way to look at LLMs is similar to how you'd work with junior developers. They can churn out code, but do need constant guidance. Of course, (some of the) real juniors will eventually become seniors. It remains to be seen if LLMs will.

The traditional longer-range P2P is HF radio and maybe Winlink email on that. APRS over HF is also possible, and Reticulum would be too if hams were allowed to use encryption.

On the passage from Panama to Polynesia we had daily HF radio contact with Hawaii and California. Sometimes radio weather was pretty bad, but generally it worked out.

In practice nowadays passage communications for 99% of boats is WhatsApp over Starlink, with maybe Garmin InReach as backup.

A few boats, yes. But it is still a "new thing". Before leaving Panama I ordered a stack of cheap Heltec V3 Meshtastic boards so we can give some to our buddy boats

We are in the South Pacific with our sailboat, and are using Meshtastic every day to talk between ourselves and with various buddy boats. The boat has a solar-powered repeater (CLIENT_BASE) on the mast that increases communications range significantly.

This all works great with no local SIM cards or other subscriptions or infrastructure needed.

We plan to run experiments with Reticulum when we stop for the cyclone season. Reticulum would open a lot more possibilities with both LoRa and internet-based comms. The Columba app seems to do a lot to bridge the usability gap, but work will need to be done to integrate Reticulum with our boat systems the way we have with Meshtastic (alerting, telemetry, digital switching control).

a person working with a bunch of agents is a lot more productive than just a person

[citation needed]

I try LLMs for something every couple of months, and I have yet to see them produce anything actually correct. Calling non-existing library methods, confabulations, etc.

But sure, they produce a lot of stuff in a short while. The utility of any of that another question.

Now, I think the author would consider it "solutionism", but the other day I spent a bunch of time browsing Reticulum's NomadNet sites (using the Columba mobile app).

And while aesthetically it was more early 90s than 1999, it filled me not only with nostalgia, but also with some optimism for the future of the Internet. Something I haven't felt in a while...

It is kind of funny how most of them scapegoat that Dye guy (who was poached by Meta). As if a single person was responsible for all that bad design, and it isn't a failure of the whole organisation.

This thread is going to be very contextual. I'm currently sailing on a small sailboat, and hence the items will be quite different than what would be useful ashore:

* Wacaco Nanopresso - manual espresso pump. Great coffee anywhere off-the-grid. We also have their grinder but that's not listed as it is above the $100 threshold

* Klean Kanteen insulated water bottle - fill up from watermaker water, stays nice and cool

* Seeed T1000-e: waterproof Meshtastic radio that allows me to communicate with our boat and crew also when out of cell coverage

* Shelly 1: WiFi/Thread relay that makes it easy to automate navigation lights and other circuits

* Ruuvi Tag: waterproof battery-powered Bluetooth temperature/humidity/pressure sensor. Battery lasts arpund two years. We have a few of these around the boat, including one in the fridge