It’s all good. Like I said, no insult at all. There’s no reason why you would ever have encountered a beeper, it’s one of those things that once SMS came around everybody just collectively decided to move on from. Unlike floppies or rotary phones there wasn’t some continued use for it.
(This is not an insult, I just had a realization that I think might affect you)-- do you know what the name comes from?
Years ago there was a thing called a beeper before everyone had cell phones. It was a one way paging system-- you’d give your friends your beeper number, they’d call it, type in their phone number, and their number (or whatever they dialed in) would appear on your beeper. You’d then use a landline phone to call them back (early versions of the system had no text or reply capability, only numbers and only one-way).
I always thought it was a cool name. But thinking about it I realize someone less than maybe 25-30 years old might literally have never encountered such a device. Much like a 5.25" floppy disk or rotary dial phone, they went out of style years ago and a young person might never have encountered one.
Curious if that’s you?
What’s wrong with Beeper?
This is really not accurate. Matrix is not designed to be a super privacy first protocol. It’s like Lemmy in the it’s designed to solve a problem and be a useful federated collaboration tool. It borrows features from a number of popular messaging platforms. Message history is stored on the server but encrypted client side so privacy is preserved. It supports group chat rooms. It supports voice and video. And most importantly, it supports bridges- you can connect your matrix to other services that are completely incompatible with matrix using a bridge. Perhaps the best example of this is Beeper, which is built on matrix. They are trying to replicate the user experience of the old app Trillian- beeper can link with a number of chat services including Google messages, slack, WhatsApp, telegram, signal, etc. Thus you get all your chats in one place.
Not matrix? XMPP is a good idea, but the wildly different levels of support among clients cause problems even back in its heyday Matrix solves some of that, fully encrypted, chat history stored on the server in encrypted form, supports gateways to other services.
Mainly conflicts with mDNS. However it’s shitty IMHO that the mDNS spec snarfed a domain already in widespread use, should have used .mDNS or similar.
Zelle works pretty good, the main problem is the security limits.
Let’s say you hire somebody to build a shed for $5,000.
You can’t just pay him $5,000. The first day maybe you can pay him $1,000, then the next day you can pay him another $1,500, then you’ve reached the 30-day maximum for a new contact so you have to wait till day 31 to pay him the other $2,500.
After that if you want another shed you can pay the $5,000 instantly.
Sounds good to me. You should also look into cryonics. Basically you sign up with a company and donate your body to them, when you die they pump you full of antifreeze and then vitrify you in liquid nitrogen. Right now there’s no way to recover from it, the antifreeze is toxic and we don’t yet know how to undo the cell damage from freezing. But the idea is someday in the future we will figure those things out, and then hopefully be able to thaw the frozen dead person, fix the damage caused by the freezing process, fix whatever problem killed them in the first place, and reanimate them.
For a lower fee, they will cut off your head and just freeze that. Idea being that someday in the future they will be able to transplant your brain into an artificially created body.
In fairness, the scan required such astronomical resources because of how they were scanning it. They took the cubic millimeter chunk and cut it into 5,000 super thin flat slices and then did extremely high detail scans of each slice. That’s why they needed AI, to try and piece those flat layers back together into some sort of 3D structure.
Once they have the 3D structure, the scans are useless and can be deleted.
In time it should be possible to scan the tissue and get the 3D structure without such extreme data use.
You’re absolutely right. But that actually makes even more sense. Squirt superheated plasma into a solid mass, it basically all melts together into a slurry, then the deuterium cools into gas and is released, the resulting material which is solid at room temperature ends up looking like scorched foam
Easy. Electroplasma is very hot and very energetic. When it ruptures out of the conduit, The hot energetic plasma not only mechanically fractures the materials around it, but the plasma itself is a form of matter that will, when it’s energy is released and it cools, return to whatever state it would normally be at room temperature.
Surface ships use deuterium and anti-deuterium as fuel, deuterium is liquid at room temperature. Assuming the combined plasma is also deuterium, that would mean it is eventually condensing to liquid. So I imagine the interaction between the plasma and some other material would turn the other material into a sort of spongy texture, which is probably dark due to being scorched. Thus, I don’t think that’s rock at all. It is scorched material from around the plasma conduit, that has been melted and integrated with the plasma which then returned to a lower energy state, namely deuterium steam or liquid.
The explanation I’ve always had- I think this was from some official source but I could have just made it up.
Starfleet ships use EPS (Electro-Plasma System) to route power around the ship in the form of electro-plasma (a highly energized form of plasma). The warp core generates a lot of this plasma, which is piped through conduits to various devices around the ship. The EPS system and its related systems generate a lot of treknobabble about ‘scrubbing plasma conduits’ (apparently done from the outside using a field generator tool, but still boring), ‘replacing plasma relays’ (the valves that route plasma around, apparently they go bad frequently); problems like ruptured plasma conduits are dangerous and require immediate repair, etc.
Because this all works in a grid system, whenever the ship takes damage (especially energetic damage like weapons fire) the EPS conduits can carry energy spikes all over the ship. That’s why as the ship takes damage you see random small explosions and sparks all over the place- something hits or spikes the EPS grid and the shockwave ends up, well, wherever in the grid it ends up.
Of course many EPS conduits go to bridge terminals, especially as those terminals may have direct connections to the ship systems in question.
Of course in reality this would be seen as a horrible safety risk, and a bridge terminal that could probably run on a car battery shouldn’t have explosive plasma running through it especially when it can explode and harm the operator. In fact one could argue a safe starship should keep all EPS stuff as far away from any essential human-inhabited areas of the ship as possible (especially the bridge).
One counter to that might be that perhaps the consoles actually play some role in EPS switching, but that seems a bad tradeoff to me.
Welcome to Clock 2.0, the new time and reminder experience from Microsoft! Powered by Bing AI and Microsoft OneDrive.
and for all this, your alarm reminders become yet another datapoint for personalized ads, your phone alarm to wake you up then plays at full blast through the living room computer and wakes everybody else up, and you agreed to a 750kb privacy policy that displays in a 2"x3" window with 500 pages to scroll through.
What do you mean? I haven’t followed the development directly, I’ve just been a user and so far things seem to be going pretty well. Curious what shortsightedness you are talking about?
Okay so how does modern XMPP protect this? When I last used XMPP, some (not all) clients supported OTR-IM, a protocol for end to end encryption. And there wasn’t a function for server stored chat history (either encrypted or plaintext).
Have these issues been fixed?