This little device costs 15 euros and will soon be your free NOSTR backup server for your publications. Can also backup the texts from people you follow.

Will soon be released. If there is interest I can add a small bitcoin miner inside to function as lottery ticket.

Just zap if you want that feature to be added here.

Reply to this note

Please Login to reply.

Discussion

Yes to all of the above

Is this running a relay?! Blossom server too please!!

I'm a big fan of blossom myself, that is certainly a must-have.

Storage is 32 GB maximum with an external SD card. Good enough for a few million publications but a bit smallish with pics or videos.

On further releases can try to push storage into higher values.

Blossom is retarded, we already had BitTorrent which is good whereas blossom has nothing good about it

Different animals. Blossom delivers what IPFS only promised which is great for small individual files (image) repeated ad eternum that were depending on URLs.

Torrents are great for large volumes of data where the load is better/faster shared by many hosts.

People are pacient enough to wait a minute for one torrent to start (torrent initialization and swarm search), they wouldn't be patient to wait one minute for a small image to load.

Other than that, I'm a big fan of torrents too.

Ok, I relent, this sounds reasonable

Congratulations on being the nostr dev that has convinced me to stop talking out my ass about Blossom 🤙

Hey, we should be fighting on the these posts or whatever 😂

Anyways, what I'd really like to see working one day on NOSTR would be something like this: https://geti2p.net/en/docs/how/intro

But simply also far of reach for now. Nevertheless I'll check the possibility of adding torrent support on this device.

I fundamentally believe BitTorrent is better at decentralization for a very obscure reason: because its "bencoding" data format is geographically neutral, doesn't force users to encode any English language terminology

The nostr protocol has English forced with how it uses json

But if Blossom is useful, hopefully the encoding formats can be upgraded in the future

Will it be open source?

100% open source

I'll be taking requests for new features, fixes and improvements as long as the hardware can support them.

Can’t wait to test it. I’ll be your customer!

Thanks! This little device really became fun to just plug on the work laptop from the company and see the news popping there.

Hmmm.... We gotta talk about this. This could unlock the something for nostr gaming

🫡

Cool idea!💥

ship it with an alby hub on it

Was looking into this request. It is written in Go, so it would need to be rewritten in C++ to work here and still without assurance.

Will see what can be done as alternative.

what hardware do you have there?

it would require an OS, yes. probably also a bit more resources?

Love it

Still zapping but wouldn’t the btc miner feature negatively affect longevity of a device that you actually want to have longevity?

I'm of similar opinion to yours, in either case I have never observed an ESP32 to suffer wear issues.

The data itself is stored on the external memory card. So even if the device breaks, the data is saved. Some memory cards advertise a life span of 20 years for usage in surveillance cams.

Last but not least, this should be an optional feature. Maybe a warning can be added. The miner itself will only use one of the CPUs (has two of them) so I'm curious to see how it would react with less one CPU available.

It’s a fun idea and if you or anyone using it ever hits a block it’s a massive marketing win.

Warning plus options for it to fail and then limp to another device seems like a reasonable compromise for the potential upside…

Yep

Cool!

Very sus, seems like it's going to spy on my porn collection or something

Kinda want one

lol. On this case the code is open source, can be verified before compiling and installing there.

But most people don't compile their own apps. F-Droid seems to help ensure the compiled binaries are open source, not just using the name of a related open source project and lying about being open source

You are right.

99.999% people just trust the provided binaries.

To more or less reduce that worry, there is a neat feature on github that permits to compile the code directly from their docker instances and let you download a freshly compiled binary.

The geogram code for ESP32 is not so big, it is relatively easy to read for manual inspection: https://github.com/geograms/geogram-tdongle/tree/main/src

I distrust F-Droid, but I would never even think about going along with github

The other option is compiling yourself. For a small project there aren't many other ways of making it more comfortable for users to perform these actions.

Oh, I was confused what thread I was in, sorry!

I woke up to a notification in another thread about F-Droid and open source apps, so my replies to you were all confused until this one 🤙

No worries, already good to read your feedback and know there are more people who care for this kind of tools. Otherwise it does feel lonely writing them.

When everything clicks together, nostr is going to flood with people and the only loneliness you'll feel is empathy with the people you don't have time to reply to in your many notifications

Chat, is this real?

Yep. The source code is being written here: https://github.com/radio3-network/geogram-tdongle

There aren't many docs in digital format because I use paper too often but took a picture of the overall functionality.

It interacts with another app of mine (just android for the moment) to share messages and presence information.

Yesterday was working on the website feature. I want these tiny devices to host small web pages with status, navigate the publications and so forth. This because I want the device to be reachable from the outside as a your own private and portable relay.

I'm not yet 100% sure that the bitcoin lottery ticket can be added and run OK, but will give a fair try after adding the most critical feature like NOSTR backup.

Wow, this is really cool! Interested in getting one!

Tbh, regarding the Bitcoin Miner…I think if you ask, yeah, everyone will say they want it because they just view it as another feature that can be the bolted on with no downside. I think you’re taking the right approach by stress testing and making sure it still functions fine. If it doesn’t, then taking it out certainly wouldn’t be a deal killer.

Yes. One step at a time, implement the more useful features and then go for the stretch goals.

To be quite fair, I'm building this device mostly to myself with things I'd use on daily basis because I couldn't find something already available.

I'll keep you posted.

IMO, that’s the best way to build. There’s an unfilled need and going out there and building it. I need this too but don’t have the technical prowess that you do, haha.

But yeah, I’m definitely very interested!

It won't unless you intergrated a used ASIC chip

On https://geogram.info you find the ongoing development of an app for exchanging messages using BLE, radio waves or the internet.

The development started about an year ago on ESP32 and Android devices and after many experiences it is finally becoming available. Small previews were published earlier like this example: https://primal.net/e/nevent1qqswe3t8xlr3ted45hks7wj2mz65q0njh4pwfns6s57ly4ahapnellg0vujn7

NOSTR is used by default for authenticating messages and identities, will incrementally grow to become a fully compatible relay.

I'm publishing first the web app (my apologies are not yet fully working) and then you should see the Android version following soon after. The ESP32 version (fixed station) comes last once the format/protocol is settled because development there is the hardest.

If you'd like to test and provide early feedback, just head out to the site and try things. Around October the site should be fully running.

Wow. Will this be compatible with bitchat, or just simply better than bitchat?

If there is interest, can likely add compatibility.

Would need to look on how bitchat is talking BLE. From my previous experiences on Android had to use a different method to make sure the smartphone wouldn't block BLE.

On geogram BLE is exchanged on a quite unique manner to overcome limitations on message throttle.

Coming back to this again -

We're going to need a better version of the nostr protocol before we can really develop much of a radio network on it

The current version is javascript-centric and English-centric and wastes a lot of data in the encoding to stop computers from needing to translate it to be readable by noobs

It's cripplingly wasteful and very stupid in an internet context but would be even more crippling in a p2p radio context

More than & before p2p nostr radio networks develop, it seems like we first need new nostr encoding standards that don't do stuff like waste multiple bytes to encode a boolean value by insisting on giving it a special name transmitted with every message

Yeah, I just don't use the NOSTR format for radio communication and won't be waiting for a better format to come around.

In the meanwhile just exchange very small packets of information and that's how it goes. It is already difficult enough to exchange signatures when the average communication message can't go above 16 letters on bluetooth and about 50 characters in other radio formats.

I don't have a good answer yet but will continue experimenting until reaching somewhere that is shorter and at the same time keeps all the good stuff from basic json notes.

Do you have time to explain a little more? What is nostr used for vs what the radio part does?

For example on BLE communication the long messages are broken into pieces. The first piece is the header which indicates how many pieces to expect (2 characters), a specific identifier for that message (2 characters), the last 4 characters of the verification signature and the call sign for the destination (6 characters).

This gives enough information to:

1) permit knowing when pieces are missing (many are lost during transmission and need to requested again)

2) to know if they are targetted to the device listening (otherwise ignore)

3) in the end to verify if the last 4 characters of the verification result are matching with the full verification result based on the NPUB associated to that callsign.

For this to work, at every minute or so, all the devices advertise their callsigns and NPUB on bluetooth broadcasts to whomever is listening.

On the other radio waves is similar, albeit adapted to the conditions of each frequency or limitations of the radio protocol.

There are flaws on this approach. For example, someone can spoof a callsign and present their own NPUB but this is meant for local usage without internet available. When there is internet, it is possible for someone to register a callsign with an NPUB on the central geogram server, which then periodically distributes an offline list of NPUB mapped to callsigns.

For example, if the radio wave is Wi-Fi like the newer Wi-Fi Halow or ESPNOW that can reach between 1 and 10 km then there is no need for these procedures, just send the normal NOSTR json files as you'd do on internet because they are fast enough for that kind of data bandwidth.

I think I kinda get it

What about decentralizing the central geogram server?

Nice little device!

Esp32 and LCD? Idk about Bitcoin mining though, unless you fabricated an ASIC chipset?

Basically a lottery ticket. USB-powered ASIC for mining btc are since many years useless. This device can request shares and process them, but it is like a drop of water in the ocean type of luck.

Now it could run xmr mining 😉

Wouldn't certainly mind, but can only find a miner for the older algorithm of Monero: https://github.com/virtual-coin/wolf-cpuminer-multi?tab=readme-ov-file#algorithms

Check out xmrig, it has cli mining

Unfortunately that code is for different CPUs. Don't know how to port 😢

What do you mean? It's a cpu miner? Different CPUs? Yes, but if it can run on a ARM or similar chipset, it should run on any cpu with compute.

Or am I mistaken?

Different instruction sets. Usually they don't change that much, but there is no support for ESP32 CPU there.

To give an idea, even emulating software from other CPU is slow like heck. At most they've only been able to run Windows 3.0: https://www.youtube.com/watch?v=aPtNELB45U8

Yeah I get you now. Have you looked at a raspberry Pi option?

Look at the difference in price by yourself. Anyways talking to you reminded something feasible. Geogram isn't only an ESP32, there is also an android and a web app.

Can't include a monero miner on ESP32 but can certainly add one for the other apps.

Look here: https://github.com/XMRig-for-Android/xmrig-for-android/

Some of these phones are used in geogram as stations that don't go anywhere and are always plugged. So we might as well use them for mining when the owner decides so.

Yes, well I thought you knew about xmrig for Android, but yes low hashrates but still a miner. And given xmr's mining protocol, it's less a lottery when it's part of a pool mining cluster.

Putting one of those usbs in the hands of third worlders at scale, well now there's something...

Phones are the way to go.

ESP32 is cool but still out of reach for those regions, whereas androids you kick any stone and find two of them underneath.

It would indeed be interesting to see them all mining XMR.

That why I love monero. Every device can be a miner, and everyone can pool mine and earn some xmr. Coming from South Africa, there's a lot of smartphones and people looking for ways to make money

Yes, monero in my opinion is the only cryptocurrency worthy of that name.

The rest are just casino coins, not really made for the people on the streets.