If he was food motivated to teach with, sure 😁

I usually set out options and give the command to eat. I’m getting better at guessing which food he wants though.

If they can smell and taste better than us, I’m sure water is closer to soda for them with many different flavors. My dog gets breta filled water, but prefers mountain spring water > rain puddle > breta filtered > tap.

My dog is the pickiest eater I know. The problem I have is that it is never consistent. One day nothing is good enough, another he ignores steak for kibble, the next is a cat food day, then all of a sudden it is time for steak!

He has the forbidden knowledge that you can crave certain food at the moment, but he has no way to tell be what exactly he wants haha.

Let me introduce you to: https://reddthat.com/c/dog_doesnt_eat !dog_doesnt_eat@reddthat.com

Those pride flags look awesome 👍 love the color selections!

There are literally hundreds to thousands. Many of them are horded by governments, APTs, and pen testers. I personally abused a 10 year old CVE for pen tests that was known to be used by non US government entities for a zero click code execution on opening a word doc.

Then there are things that are vulnerabilities but cannot be fixed as they are intensic to how Windows functions. Some can be hardened from the defaults but break compatibility and some cannot be fixed without a complete rewrite of how Windows and AD work. Disa stigs will give you defaults that can be hardened. Requirements for all domain users to see all GPOs, users, groups in order for AD to work is an example of something that cannot be fixed without a complete rewrite. That means an in privileged user can get a list of all users, all domain administrator, names of all computers on the domain, etc. As an attacker, that is invaluable.

Short answer, that list is to big and changes constantly. None that would be comprehensive, but disa stigs is a good place to start.

If you think anything on the Internet can ever be forgotten… Your going to have a bad time. Passwords, one of the most protected data types, are compiled from beaches into huge databases so that hackers can use them to try to log into website. There are literally dozens of not hundreds of those password databases on the public Internet to be downloaded, not to mention private or dark web collections. If passwords are not safe, what makes you think publicly available social media would be any different?

Even if somehow the whole federation agreed to purge all post every year, things like the Internet archive and Google cache of pages would retain the data.

I believe the setting is allowed by instance default instead of user setting in the app. It also fails to blur user avatars in nsfw posts viewed with blur enabled which results in porn being showed from the user avatars, even when the post its self is blurred.

There are many variables that makes a yes no answer impossible. Currently there are too many instances for a lawsuit to be brought to each. The instances are in different countries, do different laws would have to be navigated for each. For example, in the US, Google has like to piracy websites. Google doesn’t allow housing of piracy on their platform. Google does some removal of listings but it is but exhaustive.

Google is not being held liable, and I bet if an instance happens to cache piracy content due to a user interacting with another insurance, Google and ISPs would be interested in helping that instance so president isn’t set that creates liability for traffic that happens to traverse servers, if it is but being served by the server.

This is a very ELI5, and isn’t a full discussion of all the variables. A difficult question even limited to one country’s laws.

Realistically, the while point of a federation us to make it impossible to shut down, or censor world wide, the community as there are simply too many different servers. This works against corporate attacks as well as legal.

It will likely depend on how popular Lemmy becomes as well as the server physical location \ DNS registry that of used.

Having a piracy channel on an instance located in a country that does not recognize intellectual property, and a DNS registration in a TLD that doesn’t respond to piracy complaints should be pretty bullet proof. Only thing that companies could do at that point would be to try to get a court order to have the DNS entry blocked by US \ EU \ etc DNS providers, or a court order for ISPs blocking the server IP address. These could be easily circumvented by changing the server IP if it happens and updating the DNS.

A way to keep everything out of the browser history would be awesome.

For best practice, my personal recommendation would be to not have any service public facing besides a VPN that requires MFA. segment self hosted services into separate VLANs based on how sensitive the content is. Disallow all traffic between VLANs unless required and only allow based on port number, specific resources needed. Don’t forgot to disable outgoing Internet access unless required. Devices like Chinese made video cameras should never have an Internet connection.

My network looks something like: home vlan, work vlan, Netflix \ hulu streaming devices, cctv, wireless work, wireless home, wireless guest, iot, servers, network management. Would be way overkill for vast majority of people, but I would be hypocritical not to considering what I do and I do have a different threat profile than most.

Another thought: self hosted through VPN with MFA and nothing public facing is probably safer than cloud as long as you have cold backups.

It was meant more as a joke than criticizing hosting your own services. I personally have a VPN with MFA, and services that I host for my self that are segmented to a paranoid level (home camera system on own vlan, restricted from being able to reach any other vlan or the Internet, etc) with a deny all and explicit allows on per host and traffic type. The amount of work that went into building the network is probably overkill, and it is still susceptible to nation state and supply chain compromise but hopefully whoever gets in will curse me if they try to move around the network.

Realistically, every added service and host is added attack surface and chances for misconfiguration \ supply chain attack, but being alive is a risk too…

I’m guessing system admins and dev op is over represented here so some of our home networks may be targeted as a path into a corporate environment, but I’m guessing the chances are low. Sadly even the most secure networks are not an impossible target. The attackers are well ahead of defenders of networks. Attackers need exceptions, while defenders need everything perfect. Much harder to accomplish.

As an offensive security worker… I can’t help but read people listing out their attack surface 😂

Bonuses are discretionary. Stock is questionable, especially if it is not immediately 100 percent vested, 401k tells me they are completely out of money and can’t / won’t source additional funding.

In tech, you should always be looking at the next job, even if you are comfortable where you are. Loving what you do, who you work with, work life balance can all offset certain amounts of money, but knowledge and experience is either always growing or growing stale. I’m guessing at early 30s, you are not in an exec position and changing companies with lead to faster career growth than sticking around for the company to turn around it’s books and promote you.

It is always good practice to set up certificates everywhere. I do it for all of my internal services. Each person has a different level of care for how important privacy and security are and some people have abnormal threat profiles.

With that being said, options are usually to run self signed certificates, roll your own certificate authority for your network, or get valid certificates from a service like letsencrypt.