Jerry on PieFed

Just a techie guy running feddit.online to allow people to communicate, make friends and acquaintances. Odd coming from a happy introvert, right? (https://jerry.hear-me.blog/about)

I also own these publicly available applications:
Mastodon: https://hear-me.social/
Alternative Mastodon UI: https://phanpy.hear-me.social/
Peertube: https://my-sunshine.video/
Friendica: https://my-place.social/
Matrix: https://element.secure-channel.net/
XMPP/Jabber: https://between-us.online/
Bluesky PDS: https://blue-ocean.social/ (jerry.blue-ocean.social) Mobilizon (Facebook Events Alt): https://my-group.events/
and more…

  • 24 Posts
  • 71 Comments
Joined 2 years ago
cake
Cake day: September 29th, 2024

help-circle
  • This is the email bomb protocol. This person creates a ton of accounts at different Fediverse servers and probably other applications, using the same email address on each, so the owner of the email gets pounded with emails. This is to cover up or make it impossible for the person to see that their bank account or whatever has been compromised and to prevent recovery.

    Eventually the email provider protects itself by rate limiting the incoming emails so they aren’t even seen. This causes the SMTP servers to continue trying to send the emails due to the temporary failure, generating even more email.

    Ultimately the email provider will shut down the email address, and that poor person cannot see any of the emails sent by the bank with warnings or account instructions, and it certainly delays recovery until all the assets are removed from the account.

    You should close registrations or at least require approval.

    I don’t know how it works on Peertube, but on Mastodon, the email validation is sent even if approvals are required, so it doesn’t stop the bombing.

    You can check your logs for some way to recognize the incoming requests and set up a firewall rule if you have access to a firewall that can do this.











  • Jerry on PieFed@feddit.onlinetoTechnology@lemmy.world•*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    27
    arrow-down
    3
    ·
    3 months ago

    My understanding is that while the older Pixel phones had MTE capability, it was off by default and could only be enabled under the dev settings. Google did not enable it by default because Android depends heavily on vendor board support packages, proprietary SOC drivers, and HAL modules. Google felt that driver code quality from 3rd-parties is not clean enough to enable kernel-level MTE without risking bootloops and spontaneous reboots. Even worse for C++ apps, which often read slightly past their allocated memory blocks.

    Instead, Google rewrote critical core Android system daemons using Rust. Like the keystore, Bluetooth stack, DNS resolver, and others. I believe using Rust essentially makes MTE unnecessary.

    Also full synchronous MTE mode has high CPU/memory bus penalties (could be 5-10% under heavy memory loads).

    Google probably decided that since hardly anyone used MTE anyway on earlier Pixel devices, they could use the space in the chip for other uses.

    The point is that the post makes it sound like using a Pixel 11 under Android results in less security than before, but for most people there is no change since they never used MTE anyway.





  • There are two answers to this depending on what the reason is for asking.

    If you are asking because you are concerned about scrapers reading your posts and violating your privacy and your rights, then understand that even if an instance is 100% effective at blocking them, the post is sent all over the place in clear text anyway. It doesn’t matter for them which of the federated servers your post is read from. They will read your post many times over. For this case, then, there is little incentive for a server owner to block bots if it’s just to protect your posts from ingestion.

    If you are asking because you are concerned about scrapers sucking the life out of a server because there are multiple different AI companies trying to read every single post in the database multiple times over for training, which ends up causing gateway timeout errors and poor performance, then admins, for this reason, should take action.

    On my PieFed server, feddit.online, as of yesterday, the firewall discarded 99K requests it deemed were for AI scraping while processing the remaining 300K requests. Those 99K requests would have been expensive requests, not just upvotes and such, but requests asking for huge amounts of text, and so the impact on the server and infrastructure would have been much more than a 25% tax on the system.

    And if the bots realize your server is not well protected, it gets worse. 3 months ago I peaked at 1.2 million requests in one day, of which over 700K were AI bots. Now it’s down to consistently under 100K from bots because many of them have given up, I like to believe.






  • Wine requires Linux knowledge to get the configurations correct. I don’t think many Windows users will be able to get any Windows applications running under Wine. And it’s the same Wine that any Linux user can install for free.

    If Zorin came packaged with Crossover, then maybe it would run Windows apps better because Crossover would manage the Wine configurations and the required Windows infrastructure installs.

    Maybe.

    But not many old machines will have the capacity to run Linux, Wine, and a Windows application. But Zorin’s hype leads one to believe that a 15-year-old machine won’t struggle.






  • I read the post and understood the problem. Then I read Dan’s reply. And he’s fixing it. In fact, he’s fixing it in the exact way the blog post says it should be fixed, “… but those filters should be manually triggered and always removable.”

    Here’s Dan’s reply:

    “… I hear the community: you want text-only posts. We are going to build this as an opt-in feature. If you want microblogging, turn it on. If you prefer the classic media-only experience, nothing changes.”

    Why was this blog post even written then? Now it’s seeming to be personal.