I remember when sending messages and files through IR was a standard default feature in (dump) phones two decades ago. It is a bit sad how technology in some ways regresses when certain anti-incentives apply.
IRDA is 1-to-1 and basically requires both users to do nothing else but use IRDA (including being within line-of-sight of each other). For a use case like talking to a family member a few seats over on a plane, IRDA won't help you.
Bitchat, at least in principle, doesn't require you to sacrifice the entirety of your phone to constantly run Bitchat in the foreground, and can work over larger distances (and with a mesh architecture which lets you reach people that you wouldn't normally be able to reach).
Writing an app that has the equivalent of 2000s-era functionality is a day of work at most. You don't even need to, you can achieve similar objectives via Airdrop / hotspot names (the latter being used as a loophole to communicate across prison cells). This is not what Bitchat is.
I did not mean to say bitchat does the same, but that mainstream technology moved away from direct p2p, that could have evolved to sth like bitchat, to mediated modes of communication. Instead eg mainstream technology going from 1-1 IR to a p2p mesh architecture of communication (with modern bluetooth having higher range as IR etc), we got cloud, proprietary platform-specific protocols/apps etc.
Yeah, it was growing pretty rapidly during the libp2p days and tons of interesting truly-distributed things were popping up all over, but it has fallen rather far from that height.
There seems to be somewhat of an upswing lately though. Federation is cool again, and many of the implementations active now seem much more stable, instead of weird half-research projects that killed themselves by ignoring the real world too much (which was sometimes true to their goals, which is fine but unfortunate).
Standardizing a non proprietary chat protocol over BT would be a pretty interesting prospect.
Who would advance it? Can you even get multiple parties to agree on what's in it? Is there any identity required? What's there to stop this being another "Bluejacking" vector but now with dick pics?
Given all of the above the proprietary route seems inevitable, even for protocols over Bluetooth.
Apple (sort of) did it, with (proprietary) Airdrop, and yes, it was "Bluejacking, but with dick pics."
AFAIK, they changed policy a few years ago, so that even if you set discoverability to "everybody", it changes back to "contacts only" after a few minutes.
IRDA is 1-to-1 and basically requires both users to do nothing else but use IRDA (including being within line-of-sight of each other). For a use case like talking to a family member a few seats over on a plane, IRDA won't help you.
Bitchat, at least in principle, doesn't require you to sacrifice the entirety of your phone to constantly run Bitchat in the foreground, and can work over larger distances (and with a mesh architecture which lets you reach people that you wouldn't normally be able to reach).
Writing an app that has the equivalent of 2000s-era functionality is a day of work at most. You don't even need to, you can achieve similar objectives via Airdrop / hotspot names (the latter being used as a loophole to communicate across prison cells). This is not what Bitchat is.