chadsix

Great Job!

I built something similar but different -- specifically just for tasks without voice -- https://asht.ar -- that might be worth checking out!

We are at 1000+ users and growing! ^^

To be fair, it's much easier than one can imagine (try ollama on macOS for example). In the end, Apple wrote a lot of longwinded text, but the summary is "you have to trust us."

I don't trust Apple - in fact, even the people we trust the most have told us soft lies here and there. Trust is a concept like an integral - you can only get to "almost" and almost is 0.

So you can only trust yourself. Period.

Exactly. You can only trust yourself [1] and should self host.

[1] https://www.youtube.com/watch?v=g_JyDvBbZ6Q

Great point!

We offer 5 because we're geared toward helping people host appliances as opposed to raw network setup! We also offer automatic RDNS with this as well as the Cloud Seeder appliance!

Thanks again for your comments and as well thoughts!

I am part of a company that promotes self hosting and provides external routing for self hosting [1]

We made Cloud Seeder [2] an open source application that makes deploying and managing your self-hosted server a 1-click issue!

Hope this comes in handy for someone! :-)

[1] https://ipv6.rs

[2] https://ipv6.rs/cloudseeder https://github.com/ipv6rslimited/cloudseeder

You can also do this with 1-click and no effort using Cloud Seeder [1]

[1] https://github.com/ipv6rslimited/cloudseeder </shameless>

And for those of you that don't have an external IP, you can use services that provide egress for you like IPv6.rs. [1]

[1] I'm DevOps there! ;)

> if you have to reason about how the operator will handle legal threats, you shouldn't bother reasoning about the messenger at all.

That's true.

You need to run your own platform people. XMPP is plenty simple, plenty powerful, and plenty safe -- and even your metadata is in your control.

Just self host. There's no excuse in 2024.

Wake up people!

Why should the arrest of someone else affect YOU?

I for one am a fan of the short and sweet. I think it's very straight forward -- if someone follows the video they can do the same, with you, in real time and I think that's great.

Good job and good luck with your speech tomorrow. It's really good that you're promoting self hosting -- this really is the final line for the battle of the people vs big data on the internet.

I'm surprised that nobody suggested self hosting a GitLab or Gitea instance. [1]

[1] https://ipv6.rs/cloudseeder

While we haven't made a box, we made the software side in GoLang [1]

This lets you host the most popular self hosted apps with a click[2] and you get an IP from us. :-)

[1] https://github.com/ipv6rslimited/cloudseeder

[2] https://www.youtube.com/watch?v=TjklYTxE8ks

And you can self host it on your own computer with 1-click [1]

[1] https://github.com/ipv6rslimited/cloudseeder

In light of the issues being uncovered about Signal (storing messages and media encrypted, but storing the key unencrypted on the same filesystem) among other things, I thought it might be worth making sure everyone on HN is aware that Jabber (XMPP) is doing very well.

We've been addressing this by taking all of this 'trust' out of the equation at IPv6.rs which is all in the open [1]

</shameless>

[1] https://github.com/ipv6rslimited/

We help people self host hands free [1] so different factors guide decisions for them. :)

[1] https://ipv6.rs/cloudseeder

Cloudflare is definitely less trustworthy than a random outsourced IT guy - there are many random IT guys across the world at Cloudflare [1].

[1] https://blog.ipv6.rs/understanding-tls-mitm-and-privacy-poli...

We made a simple way to lock QBittorrent into a VPN in a container [1]. It's probably simple enough to follow what we did in the config script to set it up for your use case (all open source [2]).

[1] https://www.youtube.com/watch?v=PrH6Ci_4eig

[2] https://github.com/ipv6rslimited/cloudseeder

There are definitely easier ways to get IPv6 if you don't want to deal with the networking.

I feel like I'm doing a lot of plugging of IPv6.rs [1], but I guess that's a testament to just how much demand there is for IPv6.

[1] https://ipv6.rs

You should never use an LLM/AI Chatbot with a third party service for anything that could be confidential, private in nature, or may have to do with your security.

All of the LLM/AI providers can read your contents. The only thing between them and your chats is "trust," and we've all had promises broken on us before.

Trust is not security.

Shameless plug: You can definitely use IPv6.rs and Cloud Seeder [1][2] to run Ollama and OpenWebUI on your own computer (confidentially) and access it via TLS remotely (via phone, etc.).

[1] https://ipv6.rs/cloudseeder https://github.com/ipv6rslimited/cloudseeder

[2] https://www.youtube.com/watch?v=g_JyDvBbZ6Q

> Then, if your server’s hard drive grows legs and walks out of the data center, your users’ most sensitive data will remain confidential.

> Unfortunately, for the server-side encryption at rest use case, that’s basically all that Disk Encryption protects against.

If you aren't able to self host, then encryption at rest is a real use case and the next best thing to actually controlling your data. That being said, obviously self hosting with FDE@Rest is the best.

Or you can end up like the people who lost their data [1][2].

[1] https://spectrum.ieee.org/thousands-of-bitcoins-stolen-in-a-...

[2] https://www.youtube.com/watch?v=g_JyDvBbZ6Q

You can literally just self host and run open source software and it will be the same experience or even better since you won't have your meta data spied on at the same time.

Just wanted to chime in and say thank you Seth for all of the work you did to create LetsEncrypt.

You've made the internet safer for all of us.

I believe that IPv6 [1] is without a doubt coming in the future. Even with carrier grade NAT'ing and the likes, there are too many major providers who have already switched to single stack IPv6 natively.

That said, I agree that 240/4 is necessary to assist with the transition. Due to the fact that most network operators aren't even dealing with /24's, it becomes increasingly hard to facilitate bridges between the legacy IP and IPv6 so more IPv4 space is always appreciated (until the day we don't need to bridge at all).

[1] I may have a bias due to affiliation with https://IPv6.rs

We do backwards and forwards compatibility between v4 and v6 using NAT64+DNS64 between IPv6 -> IPv4[1] and a reverse proxy (delorean) for IPv4 -> IPv6 [2]. To ensure reachability to IPv4 endpoints without a domain, we use visibleip.com [3].

For our users, it doesn't matter if it's IPv4 or IPv6 - they can reach it, and it can reach them.

[1] https://blog.ipv6.rs/ipv4-activated-via-nat64/

[2] https://github.com/ipv6rslimited/delorean

[3] https://github.com/ipv6rslimited/legacydns

That's unfortunate. Thanks for the heads up.

Thanks for posting this. Given the alleged racketeering issues Cloudflare may have been engaged in [1], it does seem quite important people know the background of CF. Someone appears to have flagged it, but I wrote a post covering some of the issues with CF as a MITM [2]

[1] https://news.ycombinator.com/item?id=40481808

[2] https://blog.ipv6.rs/understanding-tls-mitm-and-privacy-poli...

Again, none of this explains why they asked for 120k/year and shut it down after they didn't pay.

It doesn't matter the reasoning - its the execution wherein lies the issue - this is an extortionary business practice plain and simple.

By the way, it appears gambling sites are fine on CF [1].

[1] https://community.cloudflare.com/t/using-the-services-for-on...