Civil disobedience is the duty of everyone.

From my understanding, you are pretty safe as long as you don't provoke them (walking through the middle of them might be considered provoking) or near their calves. This article from the UK states "Where recorded, 91% of HSE reported fatalities on the public were caused by cows with calves". Basically, mothers with a child are going to be very protective.

Cows are a domesticated creature, so they are generally docile, but I would exercise caution because if need be they will use their mass and strength against you. I've heard of stories of farmers running from cows and narrowly escaping under a fence. Most of these did involve a farmer trying to separate a calve from it's mother. I've also heard stories of cows jumping fences.

And as far as memes go:

Is it price gouging if there is a heat advisory is my question, and how enforceable is that. For water it's just cruel, especially in places with little access to drinkable tap water.

This is what happens when you try to extract more and more value off the top of labor, without any added value other than line must go up. When suppressing wages is the only way to improve corporate profits, profits are capped and stockholders hate this. This is in theory suppose to encourage innovation to increase efficency (without just resorting to skeleton crews or pressuring labor for more output). Monopolies stop innovating due to market control and look at other methods of increasing profits with leverage rather than market competitiveness.

Sadly it wasn't a bid to open source the AI, rather than a bid for payment.

Google tried to add support for it in their product

Is like saying that google tried to add support for HTTP to their products. Google Talk was initially a XMPP chat server hosted at talk.google.com, source here.

Anyone that used Google Talk (me included) used XMPP, if they knew it or not.

Besides this, it's only a story of how an eager corporation adopting a protocol and selling how they support that protocol, only to abandon it because corporate interests got in the way (as they always do). It doesn't have to be malicious to be effective in fragmenting a community, because the immense power those corporations wield to steer users in a direction they want once they abandon the product exists.

That being said, if Google Talk wasn't popular why did they try to axe the product based on XMPP and replace it with something proprietary (aka Hangouts)? If chat wasn't popular among their users, this wouldn't of been needed. This could of been for internal reasons, it could of been to fragment the user base knowing they had the most users and would force convergence, we really can't be sure. The only thing we can be sure of is we shouldn't trust corporations to have the best interest of their users, they only have the best interest of their shareholders in the end.

Meta is allowed to use the ActivityPub standard just as much as any other standard. This does not mean anyone who decides to use it must interact with others who use it. SMTP will block your mail if you aren't from a larger server, have the right signatures and even then. Servers block HTTP over VPNs often, and there are even rules about referencing content via other servers on HTTP (CORS). Just because a standard is open doesn't mean everything using that standard has to communicate with each other.

The beauty of this is that those running instances can't restrict access of other instances to the fediverse. If Meta does start using ActivityPub, every current instance can block it. Other entities could want to run an instance that federates with Meta who has the resources to do so. Currently the biggest issue is the vast difference in scale between current instances and Meta. But if other entities got into the fediverse that federated with Meta this would still be a decentralized system, just with larger nodes between them. All of this still allows those who run small instances to block these larger instances that are more mainstream and keep it the way they want it.

The benefit of not having half the screen devoted to trying to get you to download the app is a huge bonus.

I fear a lot of this is bot accounts.

Just as it's impossible to stop scrapers from archiving data on traditional websites. "Deleted" data is probably in a database somewhere, being sold by someone. As you said, you lose some degree of control over your data as soon as you post it. Data is valuable, and if there is a will there is a way.

There seems to be a lot of FUD going around with the defederation news. The problem, as most problems seem to currently be, is the population is exploding and the tooling isn't there to support the real growth in numbers. Beehaw has been a community for quite a while, and they were just here first so have more established communities, you can't blame them for that. They have every right to defederate instances, especially when their main concern is being able to moderate content for their users. Each instance serves their users first, other instances lack of user moderation shouldn't be their problem. They said they'll open back up once they can manage the moderation work load.

As for the fragmentation, this is really how lemmy was designed to be. There is talks of adding federated community listings and community browsers to lemmy itself to support discovery. Really, these features just weren't needed a couple weeks ago and now they are. In my opinion, the larger communities should have communities on multiple instances. You can cross-post across instance communities as well. Hopefully in the future the fragmentation can be fixed via the use of tags and other possible organizational tools that help federation but keeps things decentralized.

The established instances have dominance due to the first-mover advantage, which is causing the centralization at present. Overall, the experience is going to be different to a lot of reddit users due to the very nature of decentralizing things. I feel confident solutions will be found for most of these issues, and make the federated experience easier to navigate while still supporting the decentralized nature. But the fact is, this isn't and never will be "reddit' as it was, which was a centralized system with a single authority (the ToS and admins).

The numbers are a little higher than you mention (currently ~3.2k active users). The server isn't very powerful either, it's now running on a dedicated server with 6 cores/12 threads and 32 gb ram. Other public instances are using larger servers, such as lemmy.world running on a AMD EPYC 7502P 32 Cores “Rome” CPU and 128GB RAM or sh.itjust.works running on 24 cores and 64GB of RAM. Without running one of these larger instances, I cannot tell what the bottleneck is.

The issues I've heard with federation are currently how ActivityPub is implemented, and possibly the fact all upvotes are federated individually. This means every upvote causes a federation queue to be built, and with a ton of users this would pile up fast. Multiply this by all the instances an instance is connected to and you have an exponential increase in requests. ActivityPub is the same protocol used by other federated servers, including Mastodon which had growing pains but appears to be running large instances smoothly now.

Other than that, websockets seem to be a big issue, but is being resolved in 0.18. It also appears every connected user gets all the information being federated, which is the cause for the spam of posts being prepended to the top of the feed. I wouldn't be surprised if people are already botting content scrapers/posters as well, which might cause a flood of new content which has to get federated which causes queues to back up; this is mostly speculation though.

As it goes with development, generally you focus on feature sets first. Optimization comes once you reach a point a code-freeze makes sense, then you can work on speeding things up without new features breaking stuff. This might be an issue for new users temporarily, but this project wasn't expecting a sudden increase in demand. This is a great way to show where inefficiencies are and improve performance is though. I have no doubt these will be resolved in a timely manner.

My personal node seems to use minimal resources, not having even registered compared to my other services. Looking at the process manager the postgres/lemmy backend/frontend use ~250MB of RAM.

For now, staying off lemmy.ml and moving communities to other instances is probably best. The use case of large instances anywhere near the scale of reddit wasn't the goal of the project until reddit users sought alternatives. We can't expect to show up here and demand it work how we want without a little patience and contributing.