• 0 Posts
  • 131 Comments
Joined 3 years ago
cake
Cake day: June 25th, 2023

help-circle



  • yes, though to be fair, it’s not like this is just sitting in their bank account doing nothing. It’s mostly invested somewhere doing stuff to make them richer. So if they were taxed at a fair rate, idk, 90% or so, that would mean less investment, which in turn does help companies grow and pay salaries, R&D etc. They don’t send a trillion to a scrooge mcduck bunker on the cayman islands, they create shell companies there that own their stock etc. for them. They could not pay this tax since they just wouldn’t have the cash to pay x% of 3.5T. Which would either force them to sell stock to pay tax, potentially tanking the stocks value, or pay the tax directly in stock, making their holdings more government owned over time.

    As a socialist, I’m fine with either tbh. just saying this is not cash floating around that can just be spent to tackle humanities problems, if only it was just taxed properly.






  • I wouldn’t fully agree with that. There is some of that, but then also there’s very little historical record of poor people. Up until like 1850ish, only rich people could really read/write, and their books and correspondence is what a lot of historical research is based on. And the rich people themselves didn’t write about the filthy poors a lot. And there are historians that would very much like to study this topic, l but it’s exceedingly difficult for lack of resources.

    Now that said, there is quite a bit of bias still. Not just toward poor “unimportant” people, also towards women. E.g. Milan was ruled by the Visconti family, which was a powerful name back then. The last Visconti ruler died, leaving his son in law in power. He’s called “Francesco I Sforza” in most history books, even though Sforza was kind of a minor name back then, and he himself would sign letters with the Visconti last name of his wife, Bianca Maria Visconti. And even his sons (and I think Grandsons) would still use the Visconti name. But because 18th and 19th century historians thought it’s no good to refer to a man by the last name of his wife, and that the wife must have been unimportant anyways, this was the new Sforza reign, not the continued Visconti reign. But we have letters of her managing the whole city while he was off, of her disagreeing with him quite strongly and openly in letters, leading everything when her husband was ill, dealing with diplomacy and military affairs etc. So in a lot of ways they were reigning together, not one single strong man doing everything.

    There is a growing group of historians that do study these kinds of things and it is slowly shifting. And I don’t doubt that this also happens in regards to poor people, just less so due to lack of available sources. But of course there’s also institutional pushback, nationalistic infighting, funding being assigned based on biases etc. it’s not all rosy.

    And I’m no historian, so this in large part based on the “inventing the Renaissance” book by Ada Palmer(History professor at Uni Chicago and also a really good scifi writer). It’s an amazing read, not just about the period, the different power dynamics and personalities, stuff like homosexuality and atheism in the period etc., but in large part also on how historians work, how perceptions among historians changed through the ages, how some misconceptions (like “women aren’t important”) persisted for centuries. It’s without a doubt the best history book I read in a long time and I can’t recommend it highly enough.










  • Yes. And that requires the participants to self-regulate and be educated, at least beyond a certain number of participants (and this number is more in the 100’s than 1000’s of devices in a city size area).

    In case anyone is interested, in meshtastic, for a regular handheld device, set it to client if in a less populated area, client_mute in densely populated areas. router/repeater only for really well positioned nodes (think top of a mountain, NOT top of a tall building), router_late for ok positioned nodes where there’s other, better router nodes around, but they can cover some dead zone that the better router ones don’t cover. And then there’s other like client_base for e.g. a rooftop node to help handheld devices inside the house reach outside. And follow the guidelines of your local area group/forum/whatever on number of hops, band to use etc.

    None of that is really complicated, but a lot of users will just buy a device, turn it on excitedly with default settings, see that messaging works and not dig deeper, and then worsen then network for everyone.

    With meshcore, there’s a repeater firmware and a client firmware, it’s not just a setting that can be selected in the app. Default is client, and switching to repeater mean reflashing the firmware. And more clients don’t really matter for the network, since they don’t repeat. So much less risk of an unwitting user worsening the network.

    And if anyone wants to play with this, all the devices should support both meshtastic and meshcore firmware, so you can play with both and see which you prefer.

    And if you’re curious why I prefer meshcore, these are all the nodes I was able to hear on meshtastic and meshcore, respectively, in the same location, with meshcore I can reach twice as far in each direction


  • I’m definitely not an expert radio operator or anything, but this is how I understood it.

    With Meshtastic, no, it actually gets worse beyond a certain point, especially in dense areas. Each radio rebroadcasts messages, so more message fill the air, causing more congestion. setting devices to client_mute (no rebroadcasting of messages) alleviates this to some extent, but most people don’t do that. In general, a few well placed nodes are better than a lot of clients.

    Meshcore with dedicated Repeater nodes alleviates that a bit, as a node is either a client that can originate messages, or a Repeater that can only rebroadcast. And it has a bit better routing protocol, reducing unnecessary duplicates in some cases.

    The radio band is license free in many countries, but there’s still some restriction, e.g. 10% duty cycle in my country, which means no radio can be sending more than 10% of the time (so 1 minute in every 10 minute window). That combined with (afaik) nodes only being able so send one message at a time limits how many messages can be in flight at an instant. And more clients increases background chatter from e.g. node announcements and duplicates, leading to further congestion. And in meshtastic, since packets “flood” out in all directions, and each node rebroadcasts again, and it’s not directional, all the packets travel all over the place when you send a message. You could have a packet traveling in circles between new nodes for a long time.

    E.g. in my region, originally the default for meshtastic was 7 hops on long range fast preset. That led to congestion so they switched to medium range fast, then recommended limiting hops to 5, and now ideally to 3, just so there’s less chatter and less utilisation of the channel. 3 hops is barely enough for me to get out of the city I live in. Meshcore also does floods, but also can keep track of paths so you can have a relayed connection along a specific path that does not flood out in all directions, along with putting up repeaters being a conscious and strategic choice by users, so you get something more like a dedicated highway of repeaters that are placed high up and can relay messages much better than some client down at street level could. And the hop limit is more like 64 (I think it can be higher but that’s what is set somewhere in the firmware). And repeaters are stationary, so they don’t need to announce themselves to the network that often (e.g. every 3 hours in meshtastic vs every 24-48 hours in mesh core). All of that means less channel utilization and longer reach.


  • I agree, that would be amazing. I also hope it will help with some truly local community building (no troll farms from halfway across the planet spamming shit). Weather stations are already possible with sensor nodes, and most big repeaters have weather data. Though not like weather forecasts or anything.

    The main issue would probably just be congestion, not even bandwidth. Once it’s used a lot, some packets will just be dropped due to congestion and you don’t get a reply at all.

    A bit less of a problem with meshcore, with meshtastic in densely populated areas most users still don’t set their devices to client_mute, causing unnecessary rebroadcasts and even more congestion. Though with enough adoptions maybe governments might lower their restrictions on duty cycle, allowing for more traffic.