Some dingbat that occasionally builds neat stuff without breaking others. The person running this public-but-not-promoted instance because reasons.

  • 0 Posts
  • 238 Comments
Joined 3 months ago
cake
Cake day: September 26th, 2024

help-circle
  • Blocked as in sites reject traffic, or blocked as in can’t connect to the VPN?

    The former is on the far end and not uncommon. A lot of sites reject connections from known VPN endpoints because the same tunnels that provide privacy to you also provide privacy to attackers quit often. You just need to decide if the site is important enough to use without a cover.

    If it’s the latter, that would be a near end issue and would likely be your ISP or someone nearby that is looking to control your traffic.







  • Like others said, self signed or internal only domains work. Really though for the minimal cost of generally less than $20/year you can make it a lot easier by just buying a domain.

    From a pure security stance it could be argued that a personally owned CA is more secure than any public one since it’s possible for others to create a trusted cert with a public entity. Cloudflare ends up doing that for any domains you register with them, but that’s really only an issue for things facing the web and using self signed certs will typically cause problems for any pre-compiled client apps you might use.


  • My two main boxes are split to be storage vs compute. The NAS box has a minimal CPU and a pile of 3.5 drives for the low cost storage and they hypervisor has all the CPU and fairly small storage.

    Basically the goal in my setup is all the working data is in one place and the handling in another with various snapshots and RAID mixed in to avoid the risk of “oh shit did I just…?” situations.

    So anything that could be called bulk data gets offloaded to the NAS directly via mounts and any cache/working data is held locally. If your lab space grows to a notable level over time eventually you need to consider disk I/O as part of the design and having the bulk data on another box let’s you effectively trade some network load in for disk load.


  • That’s a big part of the appeal of the fediverse for me. Setting up a personal site used to be fairly easy, but was largely isolated and unidirectional. With the AP protocol, and frankly a lot of self-hostable apps in general these days, you can make something to converse with the whole globe and you don’t even need to make a big effort to help people find it.

    Webrings still exist, but finding them is less than trivial when they get drowned out by the noise of corporate sites. I’ve used IRC within the last year, but had to look up the proper use of nicserve commands. The old web mentality is still out there, but for the major part people want simplicity. Few want to go through the learning curve to deal with some of the more esoteric parts of it when they can just auth into a site and do a thing.









  • The company doesn’t have ‘less’ liability, it has separate liability.

    You wouldn’t expect that you would be responsible for the actions of a roommate in most cases. Creating a business entity separates the business from the person running it. The taxes are separate, the owned properties are separate, the liabilities are separate.

    Say you own a small restaurant, The building it resides in (if you owned it) is owned wholely by the company. You also own a personal residence. Now a customer comes in and suffers some injury and they sue. They would sue the business and if it all went badly for you they might take ownership of the business assets including the building it’s in. They could NOT however come take your personal residence that’s not property of the business.

    If you tried to do some shady biz and change ownership of the assets away from the company before a judgement was made then the customer could feasibly ‘pierce the veil’ as they say and include you into the suit personally.