Hacker News new | past | comments | ask | show | jobs | submit login

I don't think that this MobileCoin is her cup of tea, it is more like Marlin Moxiespike's.



She is still the CEO though, so whether or not it is her cup of tea, she is ultimately responsible for allowing it to remain.


Not CEO, President… the interim CEO is a well known donor.


yes, it looks like MobileCoin left with Moxie


No, it's still part of the official Signal build.

I wish such cruft would be removed from Signal.


Cruft is like dust bunnies, it grows if not cleaned up!

I literally just removed some code from 2021 that was echoing huge JSON files into build logs that nobody looked at.

It reduced the pipeline run duration from 45 to 30 minutes.

Now, a crypto coin will probably be harder to remove, but there's a weird inertia around long-lived repositories where people are afraid to make any changes. Although I hope the crypto portion is feature-flagged and can be somewhat easily disabled.


You know the app is open source, right? You can check this yourself and see how hard it would be to remove.


ah sorry about that, didnt realize it was still in the official build.


This illustrates the lasting power of bad decisions.

I wrote off Signal when I heard about MobileCoin, and didn't look at Signal again, and didn't known MobileCoin left.


I broke off libsignal at that point.

I've encountered this argument ... repeatedly. Let's explore the DIY route:

If you can build your own Signal server, you too can serve you and your own circle of friends. The bar is not that high (Java and VPS).

Signal clients are even easier but it remains mostly an unique build-challenge due to not so strong documentation and by the virtue of mastery of multi-platforms. Having said all that jazz, step back and ask yourself this, what am I losing by building my own Signal-protocol network?

      Anonymity 
Now, you would easily stick out like sore thumb to all the Internet overwatch, even within VPN tunnels. That's a risk for me.

What am I actually gaining?

Not much: a more unique hash signature of client app (it has downsides); the ability to perform a unique but slight tweak of hash/key/encryption algorithm using same Signal protocol (dangerous rabbit hole), and avoidance of XDR/NDR/IPS/IDS firewall, and the biggest one: zero spreading of hashed contact info (more on this below).

-----

Alternatively, let's take the original route: your own client against "the" Signal server:

Now, Signal protocol would be open to misshapen protocal usages (think "fuzzing"). Might be a good thing but certainly not at this early stage; do we have the manpower to stand guard over a protocol like ISC Bind9 team do with their DNS?

The one area that is not firmed up 100% (more like 99.999%) yet is the Privacy Information Protection axiom and that is centered around the exhanges of hashed "Contact" address book.

This there is largely understudied and under-whitepapered: how to exchange contact info in safe privacy order just to build your network: I keep that Signal client app option off for now and manually add my contacts. That's why I think that Signal team is moving away from telephone number.

So i am now dual-tracking usage of libsignal.



Wow it’s not even named MobileCoin anymore, despite what the link on that page says.

https://www.sentz.com/blog/welcome-to-sentz


WTF this is really weird and doesn't inspire confidence at all


It didn't (leave), see sibling comment.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: