Profile: 5dcd8ebc...

The Neocons are all announcing "the war to end all wars" (i.e. WW3) today. They seem to have settled on WW3 instead of a bioweapon to stop the election this year.

For censorship resistance, there are several huge threats not really addressed by Nostr: ICANN DNS, cabal TLS, ISP.

Low handing fruit: never ever use ISP nameservers. Run your own resolving DNS server. Do NOT use the ICANN root zone unmodified. Practice adding private TLDs - from the common 'LAN' TLD for local names to secret TLDs that you share only with trusted collaborators to public alt-TLDs (like .NOSTR) that anyone can use by configuring the name servers you supply. Always use your own primary DNS server. Use peers (even competitors) or 3rd party services for secondary service. Note that 3rd party secondary services will only handle ICANN TLDs. Consider becoming a server for the opennic.org collection of alt-TLDs. It is good practice.

Cabal TLS is not secure and never has been. The cabal can forge certs and MITM https and other TLS connections. The problem is that common browsers trust all cabal CAs for all certs. The first step to addressing the problem is a PKCS#11 policy for the browser. I just learned that all browsers are supposed to support that last week (I was working on an extension to "veto" certs via user supplied rules or js code). Normies need a simple way to use private CAs with confidence they will be trusted only for designated domains/TLDs (and that cabal CAs are NOT trusted for those domains/TLDs).

When I started on the internet, we connected peers via rs232 cable, a leased line, or a 24x7 phone call with a dial-up modem. These methods improved, and additional tech like coax, 10baseT, ISDN, Wifi, etc were added. The internet remained decentralized until around 1996, when globalist began pushing for a more centralized approach. Not only ICANN, but convincing people to drop peer connections and just use an ISP, drop self-hosting and just use a service. All this centralization was so convenient. Nicky Haley advocates a national ID to access an ISP. Elites will be pushing for this. It is past time to relearn peer connections.

The best technique IMO is virtual global mesh networks. These support a mix of ISP and peer links and do not rely on the original internet routing (BGP) which required too much manual intervention. The best virtual nets are e2ee with authenticated IPs (IPv6).

IPv4 must die. It has become a tool of centralization. (But you probably have to compromise to accomodate normies until they can install a p2p enabling VPN on their devices.)

I haven't figured out how to do lightning with self-custody BTC yet. I am willing to have a custodial lightning wallet - as long as I can limit the BTC at risk and keep the BTC myself. Actually running a lightning node myself seems to have requirements that are not worth the small amount of BTC at risk. Is it possible to have a self-custody wallet with someone else's node? How does the node operator get paid?

I read up a bit more each week.

There is no such thing as "unlimited" internet of any kind. It is a mathematical impossibility - like "zero bandwidth transmitter". Fiber has a high rate to the home, but you connect to the same routers and switches at the ISP office as when you have cable. I actually prefer cable (unless your application truly requires Gbit or more over the internet) because fiber has a higher cost to install, longer MTTR (takes longer to repair), and shorter MTTF (fails more often).

What is called "unlimited" means "unmetered" - you are charged a flat rate. This causes many perverse incentives for both ISP and customer, which I won't go into here. (Similar to an all-you-can-eat restaurant - which is never truly all you can eat and also has perverse incentives on both sides.) The economic incentives are much saner when paying for actual bandwidth consumed. A compromise is "tiered" plans, where you pay a flat rate for each capped tier, with an option to auto upgrade (if slowing down services is not an option).

What kind of security issues? Of course, you should not give clients of any services you offer (like http) access to your "home network" (assuming that means LAN your personal stuff is on). A firewall is the general answer.

I have a minimum of 2 LANs, one called DMZ is connected to internet peers (including ISP - you really should have more peers and non-ISP ones) and one for your home stuff. Servers are receive requests from the DMZ. A typical configuration is to have 1 or more (local) cloud servers running VMs connected to the DMZ. If the cloud server is also the gateway for the home LAN, a firewall on the host OS maintains the separation. (I do that because the main cloud server has 2 PSUs and is more reliable than a cheap router. I am reconsidering because so much stuff is down during maintenance on that server.)

Whatever the gateway, a firewall on that gateway should block incoming connections to the home LAN (with exceptions - need a longer discussion). For Linux, I use iptables - but that is sadly becoming obsolete. I need to learn nftables, and if you are just learning linux firewall, start with that. There are high level systems like firewalld that sit on top of nftables or iptables - and make things simpler for the specific scenarios the designers considered. While a laptop generally is one of those scenarios, the local cloud server setup is generally not - and things like firewalld make it MORE complicated, so I just use iptables on the gateway.

Simple things first: all your reliable servers must have ECC ram. Do not compromise on this. I won't go into all the reasons.

The most frustrating part of self-hosting has always been power. I've been doing this for 40 years (starting with Series-1 minicomputer), and the most common server component to fail is the PSU. This is mitigated by having 2 PSUs - much more reliable and much more expensive. I can get a used 1 PSU server for $100 plus shipping and maybe additional ram or disk. I am looking at $1000 used or $2000 plus for a new dual PSU server.

The next item is the UPS. These fail all the time. If nothing else, the batteries wear out in 3 to 5 years. You want more than one. Any server with dual PSU should connect to 2 different UPSes. Or at least your 1 UPS and a dedicated wall outlet with surge supressor. You want an extra UPS to swap in or take up load when one fails (or the batteries fail). The UPS thing is a huge pain - I would pay a reasonable amount for a service that provides N UPSes for N sats/usb per month and exchange them by mail to replace or change batteries.

You need Gbit ethernet switches - maybe even 10Gbit switches for high bandwidth applications (like SAN). Always have extra. I prefer "dumb" (unmanaged) switches. I've seen too many security holes in managed switches. Always buy cable that supports the faster switches - you will probably be upgrading (if we still have a country able to buy from China were all the stuff is made).

In addition to an OS that supports VMs (I use EL8 and Fedora with KVM), you can use old laptops or old desktops as lower reliability servers for experimentation.

Is this the kind of info you are looking for?

Thinking of hosting a website?

You got 4 main options:

1) Shared hosting plans

2) Rent a VPS

3) Rent a dedicated server

4) Host it in your home

Shared hosting plans:

This option is the cheapest, but you got a few problems. First, the host usually will use Cloudflare to save money. That's how they give such low rates, because they don't even really host it. They just have a tiny 1 core CPU that's not even fully allocated to you, telling Cloudflare what the files are. Cloudflare will be happy to censor you at government request.

Second, its not using open source software. You usually get cPanel, which is a company collecting your use-data. Maybe you say you don't care, but your customers should. This lack of open source also means shared hosting plans usually are not setup for email privacy.

Rent a VPS:

This is the best option in my opinion. Although it's not perfect, don't let perfection scare you. The main issue is you're sharing hardware with other random customers, which has security issues for tinfoil hat level privacy. Ultimately the cost of a dedicated server isn't worth it for most.

The other issue you MAY run into is if your host really doesn't allocate any resources to you, and they share all of them even if you paid for allocated. I nickname these "slut VPS"

Dedicated:

High cost, with the most security & privacy. You can get cheaper plans though with less resources. By the way, SimplifiedPrivacy.com is on a dedicated in Malaysia, with an Iceland DNS host.

Hosting in your home:

Due to the corrupt centralization of the internet, residential ISPs will bandwidth cap. Depending on your country and provider, they likely won't even let you buy unlimited because they want to force the use of data centers. They are looking to control the internet, and also to prevent their IP addresses from being commercially restricted due to controversial use. But you can host Tor Onions without much issue beyond speed.

Conclusion

In conclusion, I recommend a VPS for most people. Tinfoil hat privacy people go for dedicated, like me.

And normies go for shared and are bitch slaves to cPanel & Cloudflare's empire. But..

If you want us to design your site and have an easy and private experience, we’re here for you. A team of friendly cybersecurity and graphic designers at your disposal. Just 1 DM away

Only one of those options is self-custody.

Replying to Avatar JohnnyG

Flat Earth maps have the Artic at the center. And the Antartic is a govt conspiracy.

We found the top of a door frame a good place to secure a long ethernet cable. There are other creative ways to incorporate into wall decor. In an office with a drop ceiling, just run it through the ceiling.

Will not all of these take up a taunt against him, speaking with mockery and derision: ‘Woe to him who amasses what is not his and makes himself rich with many loans! How long will this go on?’

Will not your creditors suddenly arise and those who disturb you awaken? Then you will become their prey.

Because you have plundered many nations, the remnant of the people will plunder you— because of your bloodshed against man and your violence against the land, the city, and all their dwellers.

Habakkuk 2:6-8

In Western world since 4000 yrs ago, the earliest models of the earth were statistical (predicting sun, moon, weather for crops) - they just didn't think about the shape of the earth. The Greeks are the first well known people to develop a geometric model of the earth. It was straightforward to do measurements to determine the rough geometry and size of the earth.

The sky was more difficult due to the distance, and they split into two speculative camps: Pythagoras (earth orbits sun orbits central furnace) and Aristotle (earth as center of the universe). The telescope (an invention financed and published by Pope Urban viii, patron of Galileo) allowed measurements capable of distinguishing these models. (With a result much to the consternation of establishment science.)