(If you run git blame on serval mesh's source code, you'll find my name on about 80% of the code)
Serval mesh uses Wifi and Bluetooth to share files and communicate securely. But it can't bypass google's removal of IBSS from Android. We've kept the code that turns on IBSS on some Android handsets version 2.3.3 or lower. If you really want a mesh network between phones, you can still get your hand on some old ones...
Android's bluetooth & Wifi-Direct stack are a buggy mess. It's far too easy to stumble over a bug that prevents you from getting any data through. Plus both API's are built around having the user confirm each and every connection. Almost completely useless for building a self organising network.
Then there's Wifi. Sure you can turn most phones into a hotspot... If you use reflection to call a hidden API. The carrier hasn't done anything to disable it. And in some cases, only if you have a functional cellular data service. But there's no easy way to tell if there are other nearby devices waiting to connect to you....
The main problem with this new weather app is that nobody will have it installed when they need it. Getting emergency weather information is not going to motivate people to use this app day to day and form the adhoc networks that are needed for it to work. Also this article and the summary is crap, IBM did not invent mesh networking.
port 220, irq 7, dma 1.
I do not miss having to diagnose resources conflicts.
Then you should be able to record your time spend helping other people's projects.
Management can't see what they aren't measuring.
MR=MC, maximum efficiency.
Bullshit. Utter, utter crap. Mathematically false. Empirically false.
A "typical marginal cost curve" is anything but typical. Nobody builds a factory that runs at peak efficiency when it's half full. No firm has a cost structure that matches your Econ 101 text book.
I highly recommend the work of Steve Keen in this area if you want to know more.
Ah, "risk averse". Such a stupid concept when it comes to financial advice. The better way to plan a portfolio, is making sure you can meet your short to medium term cash needs without being forced to sell any long term investments if they temporarily turn south.
Distressed selling is the worst thing that can happen to your portfolio, and you should plan ahead to make sure you can avoid it as much as possible.
Forcing every developer in the same office to separately download a complete copy of the full history is inefficient. But then git does have a way to reference objects files from another path.
For large (but probably not Windows large) git repos, you could add a "git alternate" reference to a network share for your ancient history. So long as you are careful in how you manage that folder, and never remove anything from it, this can work quite well.
Giving each team a low latency, local mirror of this folder would be enough for many use cases.
So run your own streaming server and keep everything at home. Plex is fairly easy to setup.
It's not too hard to automate ripping DVD's so the only user intervention required is swapping discs. Then you can use software like FileBot to organise everything consistently. But getting episode numbers of TV show DVD's right is a fiddly process.
... with all participating ISPs competing
By not paying NBNco enough of their CVC charge. IMHO the CVC charge should be abolished. NBNco are building a fiber network that should be able to cope with future speed requirements. But they are price gouging everyone, and treating that bandwidth as a scarce resource.
Seriously? You have no idea how fork actually works.
fork() exploits the MMU by marking every page in the parent process as readonly, then sharing these pages with the child process. There is no immediate copying of memory.
Then whenever *either* process attempts to write to any of these pages of memory, the kernel will trap & duplicate the page before allowing the write to occur.
fork() is pretty quick. But you have to be careful to pre-initialise as much immutable state in memory as you can, then keep your mutable state centralised.
fork()-ing a new browser tab from a pre-initialised process may save you a lot of startup time. But if you then go and write small values all over the place, you could easily lose a lot of those gains.
users aren't streaming YouTube music for hours in a row
Actually, some users are. (eg)
Everyone likes to obsess over the government's debts. But it is the debts of private citizens that should be your biggest concern.
During a boom, tax receipts go up and welfare payments go down. So the government debt can be reduced. If you want to blame the government for something, blame them for not saving during recent booms.
Now we are in a slump. Tax receipts will be down, welfare payments up. The government *should* be spending (responsibly...) to cushion the blow, but they actually have little choice in the matter. Austerity policies now would be a huge mistake. Taking money out of circulation, when the flow of money in the economy is already reduced, will just make a bad problem worse.
Many IOT devices have some kind of incoming data stream from the internet so that you can control them from your phone. This might be is via some company run cloud service, with questionable security.
it's a device that infringes my copyright, gives you root access in response to trivial credentials, has access control that depends entirely on nobody ever looking at the packets, is sufficiently poorly implemented that you can crash both it and the bulbs, has a cloud access protocol that has no security whatsoever and also acts as an easy mechanism for people to circumvent your network security
"One day I woke up and discovered that I was in love with tripe." -- Tom Anderson