NetcoreNetwork

A new foundation for direct and secure device communication.

[NetcoreNetwork @netcorenetwork]

It’s time to own your life again.

Today, we have released the first version of Causeway that allows you to do just that.

Install now at https://t.co/GdVH2k17zB

[NetcoreNetwork @netcorenetwork]

Put me in coach

[Rebane @rebane2001]

okay heres the requirements to anyone replying:
must not pass through a 3rd party
must not double-transfer
must work cross-device
must work outside of lan/proximity
must work with other people's setups
must be fast for large files
must not be insecure
must be not annoying to use

[bella @bella_cor3]

This week has been crazy. I only write articles when I have a lot to say. https://t.co/EWFYMMP2m0

[NetcoreNetwork @netcorenetwork]

Now is the time to remove dependencies.

This is what building with Causeway means:

- Identity and coordination between devices is handled by a decentralized network. This is important because it’s trustless. You don’t need to rely on a single operator not getting hacked. You just need to rely on the math behind consensus. There are no emails or passwords required, just a public key to act as your device ID.

- Connectivity between devices is direct. This is important because every hop that you add to a connection adds an attack surface. P2P is the best route.

- Data is sent through encrypted tunnels. There are different transport options so you’re not limited to Wireguard traffic. This is important because Wireguard is more and more frequently being blocked by ISPs and strict networks. Causeway supports WebRTC traffic as well.

- You can still use another VPN. This is important because some p2p connectivity platforms don’t work if you have your VPN toggled on. We’ve just released an updated version of Causeway that works regardless, so your routing is really up to you.

Self-host your services, expose them only to those who need access, and lock down your infrastructure. Stay safe out there.

[NetcoreNetwork @netcorenetwork]

Today’s events highlight why reachability matters: restricting who can reach a service reduces opportunities to trigger bugs. Causeway enables encrypted p2p access without making services public. Limiting exposure complements patching.

[NetcoreNetwork @netcorenetwork]

I’ve got one word of advice for ya: decentralization

[Coin Bureau @coinbureau]

🚨BREAKING: A POWER OUTAGE at Google's London Cloud data center triggers WIDESPREAD disruptions across UK banking and online services, BBC reports.

Major services, including Revolut, HSBC, and Royal Mail, were affected, alongside court video links, raising concerns over reliance on cloud infrastructure.

Google ($GOOG) says the power issue has been mitigated, but full service recovery is still underway.

[NetcoreNetwork @netcorenetwork]

Why yes, check it out here https://t.co/RAcvkZz8Qq

[bella @bella_cor3]

“Elon musk just unveiled a flying car”

Cool, NetcoreNetwork just released new Causeway binaries that allow you to create p2p connections without having to turn off your VPN because one user mentioned that as a pain point with a different solution.

Small wins matter too 😪

[NetcoreNetwork @netcorenetwork]

If you want to remotely access a smart fridge, you should:

a) have to prove authority and authenticity in a trustless way and

b) access data directly from the fridge via an encrypted p2p tunnel. Also, permission to listen doesn’t need to mean permission to control.

Here2help

[bella @bella_cor3]

A lot of commentary on this is blaming internet connectivity itself, which is throwing out the baby with the bathwater (sad, wrong).

If you want to remotely access a smart fridge, you should: a) have to prove authority and authenticity in a trustless way (decentralized networks can help you here) and b) access the data directly from the fridge via an encrypted p2p tunnel. Also, permission to listen doesn’t need to mean permission to control.

Not every problem, but many begin with how communication occurs over the internet. For a message to get from Device A to Device B, it’s often a multi-hop process that requires reliance on third-parties for things like identity, coordination, and storage. Every hop and third-party reliance adds a set of vulnerabilities. For a simplified example, if you use Google as an identity provider and Google has an outage or gets hacked, you won’t be able to get your message through even though your devices may both be online and working.

The fix lies in stripping out dependencies and reducing data flows to only exist when necessary between authorized parties. This minimizes attack surfaces and maximizes signal-to-noise ratio.

Two critical characteristics of a better system:
1. Identity without a central gatekeeper. You control your identity through cryptographic keys. A decentralized network coordinates connections and acts as the trustless authority.
2. Encrypted communication between devices. A peer-to-peer layer connects devices directly whenever possible, with end-to-end encryption. When a relay is necessary due to difficult network topologies, it forwards encrypted data without being able to read it.

The headline next week will likely be something that sounds different, but has the same underlying pattern.

[NetcoreNetwork @netcorenetwork]

Real connections matter.

[NetcoreNetwork @netcorenetwork]

Hi 👋

[Mevin Kurray @K3vc0r3]

Show me an architecture that doesn’t centralise the trust and no third party is a single point of failure.

Then we can talk about digital ID

[bella @bella_cor3]

Really simple, direct p2p use cases of late. Ada is my cofounder's tortoise that we're keeping an eye on while he's travelling, and the directory I'm sharing has a few videos and a photo that I wanted to get to another coworker without a reduction in quality.

Features:
- free
- zero backend/cloud/third party
- encrypted, direct connections between devices

The connections appear local (you can see the localhost ports they're assigned), but are actually traversing NATs across different networks. This is automatically handled by Causeway.

The file sharing was just one line in my terminal to expose a directory on my laptop. I couldn't message or email the videos because the individual files were too big and would have to be compressed, so this allowed my coworker to download them directly from my machine at their native quality.

[NetcoreNetwork @netcorenetwork]

Direct, p2p connectivity should be the default.

[bella @bella_cor3]

p2p in today’s world has wildly different assumptions from p2p in the early 2000s, and it is not only viable now, but should become a default.

One massive change to be leveraged is that my phone is pretty much always on. This is true for a LOT of people: we don’t like to let our phones die or turn off. This is important because the beauty and curse of p2p is that the 2 devices communicating must be, well, open to communication. If Ankita’s laptop wants to send something to my laptop, they must both be alive for the duration of the send.

But, since our phones are pretty much always on, with increasingly better resources (I’m looking at you, 2 TB iPhone Duo) they can act as gateways of sort if need be.

This is just one example of changed assumptions. Another big one is improved infrastructure. Again, we use phones that have dynamic IPs. We find ourselves behind hard symmetric NATs quite often. Most people aren’t network engineers, don’t know what this means, and just want apps that work. Tech like Causeway takes out the networking complexity and just hands your devices connectivity on a silver platter.

Improved underlying infrastructure also fixes the monetization issues of both old p2p apps and current centralized apps. Old p2p apps were very difficult to monetize due to their architecture. It generally required goodwill, which is unreliable. NetcoreNetwork solves this.

Centralized apps have a different economic problem: they’re often “free” for the user, because their business model is to sell as much data about the user as they can harvest. The reality is they’ve introduced a third party that didn’t need to be there: themselves. This is also a clear security risk, all of your data routes through their hands, adding an additional term to the threat model equation.

And on the thread of security, p2p is much better than it used to be. Protocols like Wireguard and WebRTC support encrypted tunnels for traffic so your data is safe. Causeway has these options built in.

Why does this matter? Freedom and quality of life. You can read some of my other writing for more on that.

[NetcoreNetwork @netcorenetwork]

Freedom tech will save the world.

[NetcoreNetwork @netcorenetwork]

Good things take time.

[bella @bella_cor3]

I have been patient for 4 years. Not trying to over-sell something we didn’t have ready, nor trying to generate hype with raise announcements or bought followers. Nothing inherently wrong about those things, just not what I wanted to do.

Tomorrow @netcorenetwork launches Causeway. It is our flagship product.

Causeway enables better utilization of devices. It facilitates direct connectivity between peers whenever possible, and utilizes the underlying distributed NetcoreNetwork for identity, authentication, and coordination.

Good things take time.

[NetcoreNetwork @netcorenetwork]

Causeway is coming soon 👀

One use case we’re testing: connecting self-hosted tools across different networks.
Here’s Immich running on one machine and being accessed + used by another peer through its own localhost.

Self-host what you want & let Causeway handle the connection

[NetcoreNetwork @netcorenetwork]

@larry0x Hi Larry, nice to meet you. You’ll want to check me out.

[NetcoreNetwork @netcorenetwork]

@bella_cor3 Correct.

[NetcoreNetwork @netcorenetwork]

Direct, secure, remote access be like:

[NetcoreNetwork @netcorenetwork]

The architecture of communication is the architecture of power.

[Nym @nym]

The architecture of communication is the architecture of power.