kurokawad

Because the linked app (columba) is an Android app. I should have specified I was referring to that. But I don't follow why you quote MeshCore, it has nothing to do neither with columba nor Reticulum (the protocol columba uses).

I don’t really like this from the Reticulum repository: “[…] The Reticulum Protocol is defined entirely and authoritatively by this reference implementation, […]”.

The reason there are so many apps trying to solve offline decentralized communications is that there’s no standard protocol or path for it. Everybody tries to sell their app as the real solver.

Also, OS-dependant (iOS/Android only apps) won’t give any progress to the state-of-the-art.

> Because the Internet was built around centralized infrastructure.

Yeah, well... No.

> We finally have this possibility to use true P2P email.

I mean, email is literally peer to peer.

> Your mail address is derived from your public key: <64-hex-characters>@yggmail

The email address is literally 64 hex characters? How am I supposed to use this on a daily basis?

I have serious doubts who are the target of this or what is the point of this to exist at all. It is literally worse than email.

This will lead to engineers and tech people with less and less communicative skills... Being able to summarise your work and build solid descriptions about the main points of the commit is something so basic that should not be lost... If english is not your main language or you are not that good at writing, I understand that you could make a draft and ask AI to improve it or rewrite it, but this tool is directly a black box that builds the entire commit message based on a couple of prompts, as if it was an impossible task to be done by a human.

Uh okay! I was not aware of this. Thanks for pointing that out. Why is there so much difference in the NuGet downloads between both libraries tho?

To me, it's pretty much unbelievable that Microsoft introduces an agent framework while for JSON serializing third-party Newtonsoft is still the go-to.

Edit. I was not aware that the gap between System.Text.Json and Newtonsoft narrowed, take my comment with a grain of salt, please!

The trailer is hell good!! I love it!!

AFAIK cellular comms aren’t designed to be ad hoc. They require base stations (whose placement is very studied) to build coverage “cells” (cellular). The network is responsible of delivering a QoS, it’s not a best-effort like WiFi.

However, if I’m not mistaken 5G has V2V comms (Vehicle to Vehicle) specifically designed for self-driving cars, drones and IoT and that is the most “ad hoc” it can get

The 3GPP spec is “available”, but the implementation in practice is closed. Stuff like the scheduler is what actually brings value to the company delivering a good service. Being closed, the interoperability of network components from different vendors is just impossible. That’s the point of O-RAN Alliance.

Cellular comms. are all complex, proprietary, closed standards by big telecoms companies. There are some projects trying to solve this: OpenRAN, OpenAirInterface, O-RAN Alliance.

This project tries to build an open solution following O-RAN standards for RAN software. It is targeting telecom. companies for their Radio Access Network (RAN). Their infrastructure is divided into the Core Network (like a simple internet network) and the Radio Access Network (base stations, antennas and all that stuff). Phones and tablets are User Equipment (UE), nothing to do with srsRAN.

The fact that the software being written in Rust is supposed to be valuable information to be put in the title is interesting.

Nobody would say “Performant intracontinental public transport routing in C++”, or any other combination. It’s just something around the Rust language.