in spite of my age, I'm one of first digital native. I never used it and nobody explained me how to use. At same time I avoid most of analog instruments: multimeters, scope meters, calipers.
I agree that the ceiling of 4h is correct for high intense cognitive activities and that morning, after few hours after woke up, is the best time for these activities. And I would add that trying to do more the same day will affect the next day.
Meetings, phone calls are distractions, especially in the morning, they could also bring different thoughts far from current task.
To have the best result we must reorganize the company according to this, because most organizations prioritize visibility over results, but compensation, promotion and trust structures reward deep work instead of meeting attendance.
I've carefully read this interesting discussion: some political, mostly about full cloud services (AWS) vs partial EU providers, or lock-in vs indipendence.
I think the problem is elsewhere. The real advantage of big cloud players isn't their individual services. It's seamless integration and simplicity.
We need a service integration standard for infrastructure that enables:
- Service discovery
- Networking
- Observability
- Configuration
This benefits everyone: EU companies, US startups, enterprises anywhere avoiding vendor lock-in. A standard letting services integrate regardless of who provides them.
Not just container orchestration (Kubernetes), but something working across bare metal, VPS, containers, and remote machines.
The irony is that EU education is still broader and more grounded in fundamentals, compared to US one that has become increasingly skills-oriented.
I also prefer to design solutions that are portable and platform independent, cloud providers simplify and hide something to you, it has a cost (not just money) that you cannot quantify on long term and that's clear for who has experience in both worlds.
If we review the history we can notice that there was always an influence from politics/religion to science, literature, arts, philosophy and the use of them by politics, maybe to justify some decision and state of facts.
It helps to empower control over population and fits perfectly in the social and historical context: the emperor blessed by God, the evolution theory, the epic poems, theory of race, the industrial revolution, and modern times don't escape these patterns too, we just suppose to be neutral.
I think that during ice age it was more easy to travel from Sicily to Malta, maybe they'll be able to find traces of humans even earlier than 8500 years ago.
Anyway I think we have a lot to learn from our ancestors, how were they able to move such heavy megaliths?
Security teams don’t fail by missing bugs. They fail by fixing the wrong ones.
Gartner’s EAP category shifts focus from CVE volume to real attack paths across cloud and identity. Most alerts never reach critical assets. EAPs show what actually matters.
The smartphone is just an advanced walkie-talkie, currently limited only by the mobile operator, the law, the radio chipset, and the OS.
In a true emergency, who can stop you from modifying that architecture? Once you treat the device as an independent radio node (using its DSP power to run custom modems) you can establish a mesh network with a range of several kilometers.
We have a '4x4 car in our pockets; we’ve just been conditioned to treat it like a toy.
Not disagreeing with you, but you’re papering over a lot of complexity.
Note that cellular radios are highly specialized and the filtering circuits are tuned to specific bands. It’s not exactly like having a software defined radio in your pocket.
Next, at the modem level, you’ll need to implement and then sideload custom firmware. Finally, you’ll need to expose the right APDUs to the kernel to manage the whole thing.
TBH it sounds like a fun side project, but my point is you need to repurpose a lot of different parts of the stack to accomplish what you want.
I was pushing on the walkie-talkie case to gain the maximum results from existing phones, that's a true emergency case.
You’re absolutely right that the 5G/LTE baseband is a black-box nightmare to repurpose. But I’m not looking to hack the cellular modem; I’m looking for the dormant '4x4 car' already available.
For instance, many chipsets have an integrated FM receiver that is essentially a high-sensitivity VHF radio. By taking the raw audio output and applying a Software Modem (AFSK/FSK) in the user-space, you bypass the kernel/firmware complexity entirely. You don’t need to sideload a modem driver if you treat the audio jack or the internal FM bus as your physical layer.
The 'complexity' is real if you try to fight the manufacturer's fences, but it vanishes if you understand the full stack. A pair of wired headphones becomes your dipole antenna, and the phone's CPU becomes your DSP engine. It’s not about rebuilding the Ferrari; it’s about realizing there’s a VHF engine hidden in the chassis that doesn't need 'permission' to receive bits.
You just need a software demodulator the catch them, but for sending you'll need an external transmitter (an USB SDR or jack-to-FM).
> For instance, many chipsets have an integrated FM receiver that is essentially a high-sensitivity VHF radio. By taking the raw audio output and applying a Software Modem (AFSK/FSK) in the user-space, you bypass the kernel/firmware complexity entirely. You don’t need to sideload a modem driver if you treat the audio jack or the internal FM bus as your physical layer.
This is fascinating. Happy to do the research myself, but do you have any recommended reading/sources to learn more about this?
I'm glad you find it interesting. I developed the theory at university, studying how ASK and FSK modems work. To build this, you’ll need to understand the Shannon-Hartley theorem, band-pass filtering, Fourier transforms, and convolution.
For the practical 'how-to,' I recommend studying GNU Radio and SDR++; they show how to process IQ data or raw audio streams directly, and for sure there are other libraries. On the 'ancestor' side, look at the AX.25 Packet Radio protocol and AFSK (Audio Frequency Shift Keying). These are the same 'softmodem' principles used in FidoNet nodes decades ago.
GSM Arena can help you find phones with integrated FM receivers. You'll notice that many features are market-dependent, meaning: the receiver is often physically present but simply disabled by software.
The smartphone is talking to a highly sensitive receiver fed by a large sensitive antenna listening carefully in the direction of the smartphone. The base station is transmitting back a carefully directed beam with orders of magnitude more power than a smartphone. The system is highly asymmetrical. Ohh and maybe there is not one but many base stations talking concurrently to the smartphone so that if one looses some data the flow is maintained.
I’ve read all the posts and, as the 'old man of the village', I would suggest taking a look at FidoNet. It was running 40 years ago, for more than a decade, before the internet was available to the average person.
Store-and-forward, hierarchical organization, scheduled transmissions, working over dial-up and radio links, everything is there.
There is nothing new to invent, and it was far more reliable than the 10m real-world range of BT5 (not the 1km claimed for lab devices, which aren't commercial phones).
A BT5 mesh only works under well-defined conditions, which usually coincide with the cases where you don't actually need it.
FidoNet has a lot of it solved, for sure. But doesn't it rely upon pre-configured paths between nodes in order to handle message routing?
If so, then: Wouldn't it fall down completely when operating in the ever-shifting and inherently disorganized environment that a sea of pocket supercomputers represents?
I don’t take concepts as a 'full package'. I evaluate what is worth taking based on the requirements. The brilliant part of FidoNet is the asynchronous persistence.
In a 'sea of supercomputers,' a real-time mesh (like Bluetooth) fails because it requires an end-to-end path right now. Store-and-Forward allows a node to hold a message until it 'sees' any valid peer, turning every 'meat-bot' into a mobile post office.
My main concern with this entire discussion is the reliance on Bluetooth to achieve the result.
If we truly want to build a free and open intercommunications system, we must put all ideas on the table, establish clear targets (a doomsday system or inviting a friend for a drink), and evaluate what is truly available versus what is not.
Only from that foundation can we begin to define a project that survives the real world.
Well, no: In the scenario I outlined, there's now still just one node with the message for H. A passed it to K, and promptly forgot about (having passed it along to "any" valid peer).
---
In your scenario, both A and K store the message for H -- suggesting replication (or perhaps, redundancy) by visiting peers. And maybe replication is OK.
It seems obvious that it can spiral out of control, but our pocket supercomputers do have a fair bit of bandwidth even at Bluetooth speeds, and flash memory is very cheap and available (a gigabyte of flash can hold a lot of short-ish text messages and costs very little).
So the network can afford quite a lot of replication in an effort to promote distribution -- and maybe that can work. Maybe the message isn't stored by just A and K, but also E, I, O, and U because they happened to stroll by and see the outbound message for H.
But there must be limits, if for no other reason than without limits then any single bad actor can ruin the whole works by exceeding the bandwidth and storage capabilities of the network.
These limits could be hop-based, or time-based, or geography-based, or any/all of the above.
Suppose a message lives until any of 50 hops or 5 days or 50 miles is exceeded? Yeah, maybe something like that works. The capabilities can be mathed to find some version of "ideal," and probably enforced somehow to prevent bad actors from doing too much bad stuff.
(But we're very rapidly straying very far from Fidonet's normal distribution behavior here, and dismantling that concept was the main crux of how I got to thinking about these things may theoretically work to begin with.)
Thanks for posting - this is really interesting. An idea perhaps whose time may have come. Out of interest (no criticism implied) but do/have you use this tech? and if so what was your experience?
I never actually used Fidonet. I started on BBS systems just as the internet was becoming affordable, and I made the switch early.
However, I apply the concepts of FidoNet almost every day. I often design offline-first devices, where store-and-forward logic is a necessity, not an option. Many are deployed in remote areas where signals are never optimal, there a High-Gain Antenna is the only solution.
I also prioritize binary protocols over structured JSON; you have a much higher probability of delivering a few hundred bytes of binary data than a bloated text object when the link budget is tight.
Finally, I never expect Wi-Fi to work beyond 5-10m when the router is placed inside the metal structure (that's why my skepticism about BT on cruise ship).
The project is interesting, the concept too, the idea of indipendent communication tools also.
I'll tell you a story.
Usain Bolt, the world 100/200m recordman, is not faster than cheeta. He needs a motorbike or a car to be beat a cheeta. But even with a car or motorbike is unlikely is going to overtak a cheeta on the ground of savannah.
This to tell you are thinking about optimizations of a system while you need to choose the right system for the environment.
A 433 MHz based link and a strong modulation is much suitable solution than a BT class 2 device included in the phone.
And here the real hack, most of phones has an integrated FM receiver, higher sensibility than BT, a simple FM transmitter (88-108 MHz) and problem solved.
but for that to work, you need to attach an antenna, no? and where do i get such an FM transmitter? AND android does not support it in the software level, and there's no protocol for the waves?
To have an FM receiver work on a phone, you do need an antenna, the wired headphones serve that purpose perfectly. An FM transmitter is easy to find; you can use the simple 'Jack-to-FM' adapters designed for car radios, or much better, a USB SDR (which can range from a few kHz to GHz).
Regarding the 'protocol for the waves,' you'll need to play with modulation. That’s the fun part. In technical literature, there are many well-defined modulations (like AFSK or FSK) with clear suggested applications for low-SNR environments.
As for Android support, I have no idea. I understand that in this thread, 'free' sounds like 'freedom,' but freedom has a cost. The freedom of communication requires investment: in hardware, software, and the time to learn the physics of the environment.
It depends on which step of the staircase, from pure hardware to pure software, you want to position yourself. Some projects require staying closer to the metal, while others can be purely software. I move up and down this staircase depending on the specific requirements.
If the requirement is to communicate where consumer standards like Bluetooth fail, like in a ship, you have to choose the system for the environment. I evaluate these choices like an architect building a robust system, rather than just using what is available at the nearby shop.
reply