Damus
Open in Damus
adingbatponder :nixos: ๐Ÿ‘พ profile picture
adingbatponder :nixos: ๐Ÿ‘พ
@adingbatponder :nixos: ๐Ÿ‘พ

Tech by the people, for the people.

Washing up โŒจ๏ธ #RISCV #RiscvAssembly washing up #Raspberrypi sorting socks :raspberrypi: ๐Ÿ—œ๏ธ #tibber taxi service #HomeLab #macOS shopping
โš›๏ธ #physics cooking ๐Ÿงฎ #mathematics homework ๐Ÿง˜๐Ÿปโ€โ™‚๏ธ #iyoga #choir #iyengaryoga
#meshtastic ๐Ÿฆ€ :nixos: #nixos #reticulum #radicle ๐Ÿ‘พ
(Photo: Steve Carter nostr:npub1p2m4l0hd5gvxglqef9yj438lrxu9jasr55ra2yn0v4548l6hq3hsqyf398 )
nostr:npub1w2vtvsws4xywnxn50zrttckqnc53euv5vqtekhef9u5akhu4gtdsnvzxys
LXMF: fa01207bb431ff3aeea472de3e81beab

๐Ÿ’ฌ ๐ŸŒ: ๐Ÿ‡ฌ๐Ÿ‡ง ๐Ÿ‡ฉ๐Ÿ‡ช ๐Ÿ‡ซ๐Ÿ‡ท ๐Ÿด๓ ง๓ ข๓ ท๓ ฌ๓ ณ๓ ฟ ๐Ÿ‡ฆ๐Ÿ‡น
Site: https://loramesh.org
๐Ÿ“š Currently reading -: ISBNs: 9781408714959 ; 1718502125; 9798335024334 ; 9780593357668; 9798335024334
repo ๐Ÿ‘พ: https://repoducible.org

npub1v26qqfgnmjm7ltqaajrkl8qxd4aw5w8f7ej3j78hcqf60havy0mq6nfwh6npub
[email protected]nip05
https://fosstodon.org/@adingbatponderwebsite
Relays (1)
  • wss://relay.momostr.pink/ โ€“ read & write

Recent Notes

O Tristรฃo · 2d
And an addressbook helper link? To centralized?
note18rfsy...
adingbatponder :nixos: ๐Ÿ‘พ profile picture
adingbatponder :nixos: ๐Ÿ‘พ @adingbatponder :nixos: ๐Ÿ‘พ
Meshtastic and meshcore are excellent for assessing the radio aspects in your area: what can be heard and how the terrain etc. works for or against you, how many others are "in the game". reticulum can be used in addition afterwards when you know that the bottleneck is not the lora radio connection or line of sight issues, and allows more options provided others are on board too (the hard bit) but with a seamless internet connection option too. All fun.
note1j53lf...
adingbatponder :nixos: ๐Ÿ‘พ profile picture
adingbatponder :nixos: ๐Ÿ‘พ @adingbatponder :nixos: ๐Ÿ‘พ
Yes. Each machine is its own .#configuration from the main flake. But because experiments on a given machine can last weeks, I like to keep a branch and only push to branch on repo when the project build works as hoped. Then merge to main in codeberg and merge main to all other branches (machines) that would profit from that project. Kind of quarantines experiments. Not sure I am being sensible or orthodox.
adingbatponder :nixos: ๐Ÿ‘พ profile picture
Using a repo like codeberg and #git for managing a #flake for #nixos that applies for all multiple machines of a fleet each, having their own git branch, using the .#<machine_of_fleet> is really hard. Does anyone do this too? Why is it so hard? For example I have not stopped using #checkout as a command because it makes no sense to me and leads to confusion, and use switch and restore. Also I have made a mental note not to refer to "main" in any operation other than the one master machine. Tips?
1