I guess I'm confused about Matt wanting to "right the ship" so to speak, while also shoving this through. (Idgaf, it's a product call ultimately)
But it seems the clean, sustainable, long-term way to do this was to have the akismet plugin simply self-register. Why was this hack easier than just doing that?
God I love this place, a simple fking question gets downvoted.
Good. The moment they add it, all kinds of apps will start to abuse it, for "sekhurity" (read: engagement) reasons. See e.g. all the apps that now disallow taking screenshots, for no legitimate reason.
Personally I'd be in favor of a hard app store policy, that if an app notifies you about something, all the importantdetails (like full message text) must be included - specifically to allow the user to view the important information without having to open the app itself.
I'm referring to what sounds like a feature of the app, not the OS... The app... already chooses what to send through the OS notification API so I really don't have any idea what scenario you're worried about.
I generally sympathize, I also don't like when apps block screenshots (or even more stupidly, they can block Android's amazing "select text from anywhere" feature...). But I don't think there are similar concerns for Signal allowing me to hide notification content from the OS.
Right. I'm saying most apps shouldn't be allowed to send a notification at all if they're not going to put the proper content in it. As it is, many apps already choose to omit notification body, instead supplying nothing or some noninformative text, forcing you to tap through to the app to see what the notification was about. If Signal is doing anything unusual here, is that it has a switch to enable showing actual content.
I get it. I am stubborn. That behavior results in a polite but direct email/review followed by an uninstall. I'm so tired of being treated like disposable crap by everyone trying to make a buck the cheapest and shittiedt way possible.
In the Signal app itself there's an option to hide the message body or both the sender and body, that way the OS wont have anything to store in the history.
I used to handwave cloud portability. Turns out when you're shipping things and need extra services and you have deadlines, you build against the platform. I think the GP comment was probably expressing wariness of the free cloudflare tier that entices you to build against their APIs and their product shape in a way that inevitably locks you in. Sure, you could migrate, but that's expensive.
Yeah, good point. For a little hobbyist site of no importance, I'm not too worried about vendor lock-in, but that calculus changes as it gets more important.
That's the catch though. By time you're scaling, there's tension between roadway and revenue and headcount and it's the worst worst possible time to need to reachitect.
I would be curious to hear you expand on that, walk me through it, maybe a small paragraph to explain what over inclusion happened with the weird fascist, what baddies you're vaguely referring to, and connect those dots?
Are you saying the electricity I use hasn’t increased at a rate 2.6 times faster than general inflation.
Or are you saying that, for example, my low-energy-per-wash washing machine is maintainable despite having a welded drum? Or that my phone does have a user replaceable battery.
But it seems the clean, sustainable, long-term way to do this was to have the akismet plugin simply self-register. Why was this hack easier than just doing that?
God I love this place, a simple fking question gets downvoted.
reply