IMHO, worthless though it is, I don't get why Diablo-likes are called ARPG's. They have lots of A and no RP. (They are Gs tho.)
Because in 1996 experience points, leveling up, character attributes, and magical loot were all closely associated with RPGs. Over the intervening roughly 30 years those mechanics have been adopted by games all over the spectrum. However the genre-name for Diablo-like games stuck due to convention.
Also Diablo being called an ARPG predates Dark Souls by 10 to 15 years.
Buy your own domain name and put it in front of someone else's service. This is going to be a ton of work to do correctly and you're unlikely to be able to host it out of your house.
Also, something you're running off a Raspberry Pi in your house is not going to meet most definitions of 'reliable'.
Many ISPs will also block inbound SMTP unless you have business account (and sometimes even then) because it's a common malware/spam vector.
If you insist on going through with this the key thing is to make sure that you're not an open relay.
100% agreed. It's well worth outsourcing to someone else for $10/mo versus the amount of work it takes to do it well unless you're a large business.
I'd make this argument for DNS too - a lot of work for how easy it is to pay someone else to handle it.
Arch-install had me create a user iirc. Most of the rest of that page was done by installing the KDE meta package for me.
A lot of the things on that page are FYIs, not things you need to do. I still don't know what you mean by detonate or disarm .
Disarm? I don't remember having to do anything like that...
Machinima wasn't really a thing in the early 90s. Closest I can think of is Reboot but that started in 94 (what I'd call mid 90s...).
https://www.androidpolice.com/android-13-blocks-accessibility-services-sideloaded-apps/
It just takes an additional warning acknowledgement.
Google isn’t fully stopping sideloaded apps from using accessibility services, though. Once you’ve run into the dialog saying that accessibility services are restricted for the app in question, you can activate access under the app info screen in the top right corner via the “allow restricted settings” menu entry, so if you’re a power user interested in augmenting your phone with a legitimate app, you can still do that. This seems like a loophole that nefarious apps could circumvent by instructing users to enable restricted settings. Thus, it’s possible that Google will still change this behavior before going live with stable Android 13.
Things like screen reader access have huge potential uses by malware. Generally it should not be trivial for a program to get that level of access to everything you do.
Yes, why do anything ever?
When all of your factory tooling and off the shelf parts are in imperial, you use that. :shrug:
Sounds like spam.