I think Samsung put out a couple smartphones about a decade ago with 16:9 sensors, but otherwise phone cameras are almost universally 4:3. Nothing wrong with cropping intentionally of course, but I see a whole lot of images that appear to be cropped accidentally.
Random unsolicited photography tip: your phone camera's aspect ratio is 4:3. Setting it to something else crops the image, even if that something else is misleadingly called "full".
It looks like you had to back up to fit the whole poster in the frame, thereby including a bunch of carpet and ceiling. It would be easier to frame uncropped.
I think the fediverse has a built-in legal risk in that any time someone posts, data is sent to a large number of servers when then make it available via the web or sometimes push it to additional servers (e.g. by user boosts or community subscriptions). This is currently done without any explicit license for the IP contained in that post.
I'm inclined to think that irrevocable permissions are the right thing here, in large part because it's impossible to guarantee that any subsequent signal from the original poster propagates to everyone who has a copy of that post, or that the server software responds how someone else expects it will.
There is a legal basis: congress passed a law, the president at the time signed it, TikTok sued, and the Supreme Court unanimously ruled against TikTok. That's a legal basis by definition.
Perhaps you mean that there is no rational basis. That's a reasonable position you can argue for.
I use a variation of this approach to display fediverse comments on a statically-generated site. It does involve a manual post to Mastodon, but I'm not very inclined to redo the whole site.
No single entity can ruin it. We've seen that happen over and over when someone's political or economic goals conflict with user interests.
BlueSky actually talks about this quite a bit, viewing the company as a potential future adversary of the current developers' goals. I'm not sure their design choices align with that in practice, but they articulate the argument well.
Another cool thing is the broader reach federation provides. Someone with a Wordpress site need only install a plugin and people can follow it with Mastodon and the like. Tag a community in a post and it shows up on Lemmy too. This is underused so far, but I hope to see it continue to grow.
And that is what I would recommend against, even on a server that does not ban that age. If someone's (young) age is relevant to a discussion they wish to participate in, I would suggest a throwaway account.
Why do you care?
If it's just about following the rules as a matter of principle, I suggest not doing that. Nobody is checking, and saying your exact age on public social media is oversharing anyway.
If it's about content moderation being strict enough to satisfy some comfort level, I wouldn't rely on that, but I also think 13 is old enough to start learning there are shitty people online and how to deal with them, preferably with some adult support.
A fair number of my contacts from countries where this is true also have Signal. If you don't, I suggest installing it and seeing how many people are there.
If it's hard to remember who uses what, start conversations from the contacts app instead of one of the messaging apps; in most cases it will tell you.
I don't think any evidence has come to light that WhatsApp's end-to-end encryption of message contents is broken, but it's also impossible to prove that it is correct because the client is not open source.
Volunteers were told not to carry a weapon because of outcomes like this.
Let's try out the counterfactual: the assailant pulls out a rifle, aims it into the crowd, and nobody else in the immediate vicinity is armed. What happens next?
There's a small chance he was just trying to scare people and disrupt the protest, but that sounds like the prelude to a mass shooting to me. It's likely many more people would have died in that case. We can't know of course and neither could the security volunteer; he had to make a hard decision in a split second in an emergency. He had to weigh the risk of shooting when he did against the risk of waiting, and he had the disadvantage of fighting a rifle with a pistol; it's much easier to shoot accurately with a rifle, and the ammunition is more deadly.
Mastodon's federation is not at all consistent even when it could get much closer with a little effort.
Servers don't remote fetch old posts from recent follows for example, nor replies to off-server posts from people on a third server. There's work being done on both, but I'm surprised it wasn't prioritized much earlier. Some other Fediverse software handles these situations better.