I take it we’re talking about announcing and not hosting? If so, a the piracy communities might be interested in learning about it.

It’s OK in some instances where it’s a tool that helps your hands. Once you start outsourcing your head to chatgpt, you’re voluntarily letting your mental faculties rot in favor of percieved comfort.

Didn’t have much of an aim beyond trying to cook it up from scratch as a personal research project. That includes the protocol, since I’m handling keys in a creative way to facilitate both encryption and user “authentication”.

I did start a projects aiming to be a more decentralized/federated discord more akin to how IRC was back in the day. Time to revisit it, it seems.

They’ll have a “retina” scan of a brown-eyed cyclops.

Some VLAN-related nuggets that you may find useful for your post/blog:

• 99% of the time when people refer to VLAN, they’re talking about 802.1Q (VLAN tagging). There are others, so it’s up whether you want to cover those as well.
• The word “Trunk” can mean different things, depending on vendor. In the Cisco world, it means a line/port carrying multiple VLANs. With many other vendors, such as Aruba/HPE, it refers to link aggregation which isn’t necessarily relevant to VLANs
• A lot of hardware still use VLANs even none have been configured. For example, defaulting all switch ports to have an Access tag of 1 makes it behave like a dumb switch. This can cause issues later if you’re configuring VLANs elsewhere
• Anything connected to a VLAN-enabled switch will have to be connected to a port with a default VLAN tag. This is usually referred to as an “Access port” or an “Untagged port”
• “How do I configure the switch to allow units on VLAN 123 to talk to VLAN 321?”. You don’t. Connect both VLANs to a router which will route between them. Either connect the router to both VLANs individually and skip the tagging on the router, or you can run a single trunk between the switch and the router which carries both VLANs. The latter requires you to configure VLANs on your router accordingly.
• It might make sense in many cases to have the VLAN tag the same as the last octet in the IPv4 subnet. Makes it easier to keep track of.
• A PC can implement VLANs on its network port, allowing you to connect to a trunk port and access several VLANs with one cable.

Source: VLANs have been an integral part of my career for 20ish years.

Sounds like your sort is not according to your tastes. Try top n-hour. Remember to actually subscribe to communities relevant to your interest, then you can use that feed to see things that are more relevant to your interests.

Lemmy doesn’t have an algorithm - it doesn’t have any particular content to force feed you in an attempt to keep you engaged. You’re not being shown what you might like, you have to select that yourself.

I work from home most of the time.

Pro:

• The cantina is excellent.
• Flexible working hours.
• No dress code.
• No commute

Con:

• Too much office gossip and drama

deleted by creator

I’m pretty sure a significant portion would be equally offended by him having the most vanilla consensual sex in missionary position with a black woman.

The API stupidity a while back. Reddit is unusable without 3rd party clients, and inc3 Joey didn’t work anymore I said goodbye to the few communities who’s members might recognize my username, and proceeded to delete my account.

“Defeated” might be overstating it, but Pakistan generally overperformed compared to expectations, as they have a significant advantage in AWACS capabilities (Saab 340, I think?), whereas India is more limited, in the form of a few IL76 and some homebrewed systems in the works.

In this age of BVR capabilities and standoff munitions, airborne radar and intelligence is key to operational success, and Pakistan knows this, whereas India has taken more of a brute force approach to modern aerial warfare, something that was obsolete 40 years ago, if not before.

That’s because the unredacted European names are distractions from the redacted mentions of the orange lardsack.

I don’t think I’ve ever been called cool and normal before now.

That’s because the unredacted European names are the distraction from the redacted mentions of the orange lardsack.

Just for the record, MacOS is a descendant of FreeBSD. At least it was for quite a while.

I wish I was.

As long as you have the ram to run it, I find that ZFS covers most of my needs unless I am dealing with something that necessitates beegfs. My basement server has 12 drives in JBOD, tied together with ZFS, and it works fine.

Personally, I’d have some sort of enclosure that could also house a raspberry pi and similar, which mounts those disks in ZFS and shares them via NFS. That’d ensure compatibility with any OS, but it might be overkill.

Whenever I hear MacOS, just assume complete and utter incompetence on my part. I still don’t know how to right clicking to open a context menu.

But for a more general approach, how portable does it have to be, and how much storage would be ideal? A few TB, or are we talking about PB?