The manufacturer web site is almost unusable and doesn't have an ordering button. There's a "Where to buy" link way at the bottom, that doesn't work for me. Web search shows this is about a US$ 200 charger. Ouch. Thanks for the review but yikes. Also I don't want to install a phone app to use or update the charger. You are right that the missing features being important (PC interface, bidirectional USB charging).
You really have to see what the db is doing to understand where the bottlenecks are, i.e. find the query plans. It's ok if it's just single selects. Look for stuff like table scans that shouldn't happen. How many queries per second are there? Remember that SSD's have been a common thing for maybe 10 years. Before that it was HDD's everywhere, and people still ran systems with very high throughput. They had much less ram then than now too.
WTF. What could possibly go wrong. Flip phone here I come.
Sounds like it would be nice if Savannah offered Forgejo hosting.
Ok I used to feel sorry for non-libre streaming software users, but this is now in "one born every minute" territory. Thanks.
What the heck is this thing? Should many of us care?
Hmm ok, though if a security program needs frequent updates, that's a cause for concern in its own right.. :/
So do that. You can do that with Signal.
Do you know of anyone doing it? Other people have said there are difficulties.
You wouldn’t register on websites, but you would communicate with them over plaintext. I hope that makes it clearer.
It is ok, in that era (dialup or wired internet) unencrypted http was basically as secure as unencrypted landlne phone calls. People still have unencrypted phone calls all the time. Typicalally sites would show public content (like product pages on an e-commerce site) by http, then switch to https for checkout to protect stuff like credit card numbers. Encrypting everything became important when wifi became widespread. Wifi hotspots would hijack DNS and spoof entire web sites to steal credentials. Also, LetsEncrypt made it possible to bypass the CA scam industry, making https-everywhere more popular. Public awareness also increased due to Snowden's disclosures.
The RSA encryption patent also expired in 2000. Before that, US website operators were potentially exposed to hassle if they didn't use a commercial server with an RSA license ($$$). But, it didn't apply outside the US and FOSS SSL servers existed for those wanting them.
Those are nice generalities but I think they ignore reality. Jami seems like sort of a side project to its developers. Bug reports often are answered with a suggestion to make sure everyone is running the latest version of Jami, which is often useless advice. Like if you try to call your friend with your new phone and the call doesn't complete, it's unhelpful for your phone manufacturer to say your friend should get a new phone. You might be interested in helping fix the problem but your friend just wanted to have a phone conversation and doesn't want to get dragged into a debugging project. It's even worse if the other person is not your friend but rather is someone you just met and exchanged numbers with. If you try to follow up with a phone call and there is a problem, GAME OVER. You permanently lose contact with that person. You can't possibly suggest Jami as a Skype replacement after that happens to you once or twice.
Another thing with comms programs in general is you really can't debug them with just one computer. Their whole function is to let two computers talk to each other, so you need two computers where you control both ends and ideally control the network as well, so you can insert delays, network faults, etc. If the Android version has trouble talking to the Iphone version, you need both kinds of phones. I'm not sure if Jami's devs really understand that. I've worked on telecom stuff in the past and it's just the reality of that field.
Yet another (I'm not sure of this) is that Jami is a peer to peer program so I suspect some of the problems revolve around firewall traversal gotchas of various types. I don't know if there is a cure for this while keeping the basic architectecture intact. I do like it in principle and I know that people get BitTorrent working reliably without too much trouble, so maybe Jami is just missing some trick.
Finally, Jami is pretty old and back in those days, people hadn't really thought about the subtleties of encrypted group chats. Signal does a better job, and these days there is a standard (RFC 9420) for how to do it (I don't know if Signal follows this standard). It would be good if Jami were revamped for that, but 1) that would break interoperability again, and 2) I don't know if it's workable at all with Jami's architecture (serverless, using a distributed hash table for peer discovery).
For now I've sort of given up on Jami and am trying to figure out what to use instead. It's unfortunate that the main devs don't seem to have that much interest in making Jami reliable. Randos like me capable of making small contributions can't really help much with more involvement from the experts.
I found the wikipedia article mostly incomprehensible but it says a few things. You are probably better off asking on MSE or Reddit, sorry to say. Wikipedia's math reference desk has slowed down a lot in recent years though that's possibly another place to try.
It's an old "Soshine" branded NiMH AAA cell claiming 900mah. I'm not about to test it but I did use it for a while. I've standardized on Eneloops since then. Anyway this is FYI so you know that NiMH leaking is a thing.
Does that mean they are enlarging the inventory now? As opposed to dismantling old bombs as they make new ones (modernization while keeping the number constant)? I thought there was a treaty capping the total number but haven't been keeping track.