Hacker Newsnew | past | comments | ask | show | jobs | submit | lormayna's commentslogin

I remember one of my professor that created a map of all Italian regions in logo. It was probably 1992.

Yes! I have a degree in telecommunication engineering,but statistics is one of my favourite topics to study. I found things like bayesian inference or MCMC not really easy to master properly

/r/Italy is the perfect example for this study


My checklist to secure a VPS, enforced by an Ansible playbook.

* Disable SSH root login

* Disable password login and use only certificates

* Enable fail2ban

This have been worked for more than ten years and never been hacked.

I never understand the need for port knocking.


Any suggestion to migrate away from Airtable?



FYI, Grist has a very good Airtable migration tool. Brings over column types, references, simple formulas, attachments etc: https://www.getgrist.com/airtable-alternative-self-hosted/


Check out Bluetivity. Tons of functionality and easy to use.


Baserow


Unfortunately it seems it not supporting email sending out of the box


It depends what you need, there are many options these days. https://chatgpt.com/?hints=search&q=Any%20suggestion%20to%20...?


What are the difference with systems like Motion (https://motion-project.github.io/4.0/motion_guide.html) ?


Motion is a great software and it overlaps with CheapSecurity. However this software pretend to be: 1. a single-camera-per-instance CCTV with a web dashboard and Telegram bot (motion is a full-featured NVR/motion daemon: multi-camera, masks, timelapse, SQL logging, external triggers, etc...) 2. One independent process per camera; multi-camera is done by running multiple instances. (motion is multi-camera support in one process) 3. Small Flask dashboard with live stream, settings toggles, and bulk actions on recordings. (motion is functional stream/status pages) 4. Specifically optimized for low-power ARM boards like the Odroid XU4 5. Last but not least small Python/Flask/OpenCV codebase, easy to hack on...

That's it


I am living in Poggio a Caiano and I never expect it will be mentioned on HN. I know very well the history of Bianca Cappello and I am not surprised about the malaria. The area around Poggio a Caiano (Poggio means exactly "small hills") was a swamp and malaria was very common.


Then Mussolini came to power and drained all those swamps.


The area around Poggio a Caiano (west of Florence, between Campi Bisenzio and Signa, just for whom that know the area) was drained by the late Medici's and their successor, the Lorena's family.

After the first world war, they built a big area for blimps, with also a big hangar, but I am not sure if it happens during the Fascism or earlier.


and all the trains arrived on time


And you can leave the keys into the door /s


I have a Vespa PX 125 from 1984. It's a very robust motorbike, very less maintenance and really funny to drive with the gearshifter. The only problem is about brakes: there are basically useless and you should be really careful on using them, especially if you are driving on wet road. Bad brakes and small wheels is a terrible combination.

Probably the main regret to WFH is not using my Vespa anymore as I did when I was going everyday in the office.


My favourite football team was really at risk of relegation, then I created for me and my friends an MCMC bayesian simulator to estimate the relegation match by match. It was an opportunity to get used in real life to some concepts (MCMC, Metropolis-Hastings, etc) that I always struggled to understand. And my team got saved from relegation with an amounts of points very close to the number of points that my model forecasted

I also wrote an honeypot that emulate an Ollama instance: beside the attackers, it's funny how many people are looking for free inference. Somebody from Brazil try to use my honeypot to write to chapters of a book about traditional magic rituals. My next step is to extract the data collected by this tool to extract IoC and malicious prompts and share them with the community.

In the same scope I wrote also an Ollama scanner: it fetch from Shodan the open Ollama instances, verify that they are reachable and check if they are real sending a dummy query.


Tottenham?


Fiorentina, in Serie A. After 11 matches we have only 4 points and we won the first match only in December: in the past nobody got saved with a so bad performances in the first matches.


I am an happy user of Meshstastic since more than one year (I have two active nodes and a third one is in the making). I am living in hilly countryside and the difficult that I have experienced is about reaching other nodes: with the standard antenna, I can barely connect with nodes in a 500 meters range, with a better antenna (coaxial collinear is the best IMHO) I can reach more than 10km.

I don't think the Meshstatic approach of "flooding" the network with all the messages can be scalable in the long run, they need to implement some sort of routing protocols (like BATMAN), but they are heavy and complex to implement


None of MeshCore, Meshtastic or Reticulum will scale well, especially not on top of a heavily constrained radio technology like LoRa. Flooding is inefficient for obvious reasons, AODV-esque routing (which MeshCore tries to do for DMs and Reticulum tries to do in general) is prone to almost-immediate path failure on unstable underlying transports, and the hidden node problem always bites on haphazard/unplanned mesh radio deployments where people show up with nodes in random locations on the same frequency.

The cracks are already extremely visible in MeshCore in the UK, where overheads from adverts and dropped packets from collisions mean it is already horrendously unreliable and most of the chatter in the Public channel is people sending test messages and being unsure whether anything they sent was ever heard by anyone.

Most other routing protocols (BATMAN included) are also not that well suited to situations where the underlying transport ends up asymmetric, e.g. one node can't hear others but it can be heard, and that's an extremely common occurrence/failure mode in wireless meshes like this. It's a difficult problem to solve with coordination between nodes, let alone without.


You have two conditions: not dense enough or too dense and the fractal nature of population mean you can have both. Radio bandwidth is a precious resource and if you think somehow that anything good will come out of sending a packet N times you are not likely to manage a wireless network successfully.

There are systems like

https://en.wikipedia.org/wiki/Automatic_Packet_Reporting_Sys...

But they are pretty specialized and not that scalable


Any promising mesh networks, radio networks or routing protocols worth looking into?


Agree! And we need also to consider that a mesh protocol for Meshtatic/Meshcore should support mobility and have to run in a low power devices


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: