simply put, programming is glorified automation. There are jobs where the process that needs automating makes money.

Had a distinguished collegue (from the Bell Lab days) say to me recently:

“IDEs take up a lot of RAM on my machine. Vim takes up a lot of squishy RAM in my head. I need squishy RAM to hold info relevant to problem solving, not options available in my tool chain.”

There is a very effective approach (34:00), that big companies like cloudflare use, to ship a product in a fast and quality way. It bears parallels to what you are describing. In essence engineers should not get hung up in the details to trying to solve everything.

1. Just build a proof of concept
2. Discard the prototype no matter what and start from scratch keeping the initial feedback in mind
3. Build something internally that you yourself will use
4. Only once something is good enough and is used internally, then release it to beta.

So that tedious process in trying to flush out all the details before seeing a product (or open source effort) working end to end, might be premature before having the full picture.

This is the best suggestion for DIY, I can even get away without a printer and just write by hand. Perfect! Wish I could pin this comment.

nothing wrong with being self taught, you could follow these basics topics before poking holes in firewall.

1. VLANS: learn how to separate your LAN into networks with different security requirements. For wireless, try to make a “main” and “IoT” network so that IoT network that can’t talk to your “main” network but “main” can reach IoT devices. For wired, try to have a Management network, and a “Dirty network” etc.
2. Firewalls and Routing: You will need to be able to route between your VLANS and set firewall rules to allow certain traffic. Best practice is block everything and allow only what you need.
3. NMAP: learn how to do NMAP scans of your network to discover hosts and their open ports/services. This is a similar approach that “hackers” and script kiddies use on the public internet to find vulnerae and open services. Being able to probe your own network is crutial in understanding how others might approach in penetrating it.
4. Wireguard VPN: Learn to access your network remotely by setting up a wireguard VPN. Wireguard is preferred because it is “stealthy” and will not respond to unsolicited attempted to probe your network. Start small by using wireguard to access between VLANs so you don’t run the risk of using the internet.
5. NGINX and Reverse Proxy: If necessary, learn to expose your services or blog or website by only exposing nginx and proxying to your services. Many guides on securing NGINX exist. Try not to expose anything, but sometimes necessary if you want others to reach your website/blog/hosting etc.

That’s a rough outline that you can use to guide yourself and achieve milestones with hands on experience. In your pursuit you’ll run into certificates and domain name hosting and stuff. But all this is on the web so let your curiosity (and paranoia) drive! Have fun!!

The table of contents hints there is only one section relevant to security, Lab Firewall Config.

Anyone have experience with this book that could vouch for other chapters that explore best practices for security?

to preface what might sound like slander, I really would love to get my hands on apple hardware. It is engineered rather well and the geek in me can appreciate that. However, getting access to your own hardware is an issue.

While I have some concerns about their objective features, to my shame, the greatest problem is with the brand and their practices.

I think the root cause of all my issues stems from their morals and aggressive/elitist business practice - specifically their quest to squeeze money out of users and hide behind the lie of “we are doing this for the user’s benefit”.

I have no issue paying money for features I want or entities I’d like to support. In fact, I’m more inclined to financially support those who I believe in.

And apple loves to gatekeep features and keep them exclusive to apple. They effectively benefit from hard work of others who contribute to open standards and services, but at the same time do not share their own. Greedy.

if I could pin this comment I would

I see what you mean now, that makes sense.

being on equal footing

agreed. Now how can we level the playing field with a multi billion dollar corp lol

agreed!

And with Meta’s resources and reach, they could stand up a Lemmy.world equivalent easily. Play nice, break their arms jerking each off the Fediverse. And once enough of the instances are reliant on the Meta instance, cut off everyone who won’t pay to federate.

I agree with the second part of your comment, and have concerns with the first part of your comment.

I’m all for allowing others to subscribe to Lemmy or Mastadon content, which is why simply defederating isn’t as attractive as ToS. I want others to see that their communities/intrests/heros/what have you/ exist outside of Meta. I want the average person to contribute even if they don’t know how to set up an instance. What I don’t want is Meta hosting content then paywalling it, cutting off others.

For the first part about limiting to one instance… Well FB is technically one instance from a “domain” perspective. They have load balancers and tons of servers hosting their “instance”.

like I said before, I’m not a policy guy, I don’t know how to solve this. But it would be nice for those who are to spear head this and rally up volunteers so we can get in front of it. If there are no solutions, defederating would be the easiest.

Not yet. The rumors are confirmed by Meta reaching out to a Mastadon admin, Kev, from fosstadon.org. He kindly made public the email.

Mail from Meta to Kev, from fosstadon.org, and reply

I tell him that I am currently in a simulation and thus it must be the last game I played.

If I get a fat check that means this is all a simulation ;)

thank you

I’m having a hard time believing that is the case for “search.” Cards and “google news” is another story.

As much as I dislike Google’s practices, they are doing a service by indexing where websites are and allowing them to be found based on keywords.

I feel if I go to “google.com” and search for <some Canadian news site> Google should show me links to <some Canadian news site> so that I can visit the site directly. Any law that retards that is shooting Canadian news outlets in the foot.

Now if Google somehow finds what you’re looking for and does not take me directly to the website and instead parses the site, presents the content, and shows its own ads, as opposed to ads hosted on <some Canadian news site>, then yeah - google can go play in traffic.

am I understanding it correctly that if I’m in Canada and search for, say ArsTechnica, or other news source, Google will not show those results to me? Like they indexed the site and will omit it from a search?

Or are they pulling news in their “cards” or whatever they call them when they show previews and users never enter the site. Havent used Google Search in so long don’t even know what shenanigans they are up to.