I think it’s too late for this to be useful. Number spoofing is ultra-common these days and most of the unwanted calls I receive are from spoofed numbers that appear to come from local areas.
If we start blocking the spoofed numbers then eventually we’ll just be blocking every possible combination of digits that can exist.
What we really need first is better detection and blocking of calls using spoofed numbers.
Are you just talking about dynamic DNS services for one or a few home servers?
There’s always DynDNS, but that’s a paid service. I actually discovered that dynamic IP address service was provided free by Google when using Google Domains as the registrar, so I moved a few of my private domains over to Google several years ago to save myself $55 a year.
Unfortunately, Google Domains is shutting down and all registrar services and existing customer domains are getting moved to squarespace and I’ve not yet been able to determine if squarespace is going to be offering the free dynamic DNS service or not.
While there is merit to your post, I will point out the obvious: your post is hosted on an instance named “lemmy world” and you are citing US enforcement codes and sections, but lemmy.world (the servers) do not reside inside the United States. Lemmy.world (the server) would be subject to the laws of the country in which it is hosted, the admin team would be subjected to the laws in the countries in which they reside, the community moderators would be subject to the laws in the countries they reside, and the lemmy.world users would be subject to the laws frrom where ever they reside.
So, you can’t simply link to a writeup about some US regulations and assume it’s going to be exactly the same everywhere and for everyone.
That is a great point. I don’t know if the admin team are proactively reporting that activity to law enforcement, but I hope they are.
You don’t have to explain how liability works. I get it. What I don’t get is how removing that specific community is going to limit their liability when the perpetrators will just target a different community.
How does it limit liability when they could continue posting that content to any/every other community on lemmy.world?
Doesn’t that send a clear message to the perpetrators that they can cause any community to be shut down and killed and all they have to do is post CSAM to it? What makes you or anyone else think that, upon seeing that lemmyshitpost is gone, that the perpetrators will all just quit. Was lemmyshitpost the only community they were able to post in?
How would you respond to having someone else forcibly load up your pc with child porn over the Internet? Would you take it offline?
But that’s not what happened. They didn’t take the server offline. They banned a community. If some remote person had access to my pc and they were loading it up with child porn, I would not expect that deleting the folder would fix the problem. So I don’t understand what your analogy is trying to accomplish because it’s faulty.
Also, I think you are confusing my question as some kind of disapproval. It isn’t. If closing a community solves the problem then I fully support the admin team actions.
I’m just questioning whether that really solves the problem or not. It was a community created on Lemmy.world, not some other instance. So if the perpetrators were capable of posting to it, they are capable of posting to any community on lemmy.world. You get that, yeah?
My question is just a request for clarification. How does shutting down 1 community stop the perpetrators from posting the same stuff to other communities?
How does closing lemmyshitpost do anything to solve the issue? Isn’t it a foregone conclusion that the offenders would just start targeting other communities or was there something unique about lemmyshitpost that made it more susceptible?
I thought data caps for home internet were a thing of the past…
For the past 15 years I’ve had a data cap on home internet, but never had a data cap prior to that.
That’s led me to believe the exact opposite of your observation; unlimited data is a thing of the past and data caps are a thing of the present and future.
Pixel tablets are not priced as if Google is “desperate to sell Pixel Tablets”.
I think the author is confusing “marketing team motivation” for “desperation” just because they got a push notification.
They are making an assertion as if it is a statement of fact…and they are, in fact, wrong. That’s ignorant and not helpful for discussion or helpful for understanfing and solving the actual issue. If they had actually asked an innocent question it would be different, but they didn’t. That is why the responses are the way they are.
No, not programmatically. The only way to ‘move’ an instance is for a community of users to create a new community elsewhere and arbitrarily start using it as their preferred community. There is no way to force it and there is no mechanic for moving.
By claiming that the problem isn’t DDOS, you’re just advertising your ignorance. Cloudflair is outstanding for protecting static web content against DDOS, and Lemmy.world is well protected against that. The problem is certain dynamic pages and api calls that can only be rendered from costly realtime dynamic database operations…those are the url that the DDOS attackers are focusing on and those are the kinds of content that cannot be easily protected by cloudflair.
Your premise, though, is still accidently correct. The way to mitigate instances being targeted by DDOS is to spread the user base and community hosting across a vast number of instances so that no one instance is such a rewarding target for DDOS attack.
deleted by creator
I sell most of my old/used but still functional tech on ebay/craigslist. For very low resale value items (under $40) it makes no difference; but for more expensive resale value items, having the original box/packaging/manuals/accessories increases the resale value significantly. My auctions routinely sell for $30 more than comparable items.
It pays (literally) to keep the original box.
I’d never heard of STIR/SHAKEN…but after looking into it, supposedly T-Mobile was one of the first mobile carriers to implement it…and I’m on T-Mobile…but for the past several years, I keep getting unwanted spam calls to my cell phone that appears to be originating from very regional local numbers (area codes and number prefixes that are local to my area)…because of that I just assumed that they had to be spoofed since the calls are always an unwanted telemarketing robo call and never involve an actual business that is local to me.
So I don’t know how they are still doing it, but somehow telemarketers are causing calls to route through exchanges that are completely local to me.