Apparently the app suite from Simple Mobile Tool on Android has been sold to an AdFarm company. All the apps now seem to have massive tracking, several of them now require you to pay (even if you have bought the "Pro" version earlier) while the rest have, of course, ads. So my calculator now require internet access and uses several seconds to load.
Jakby ktoś tęsknił za aplikacjami z serii #simple to mam dobrą wiadomość.
Wygląda na to, że powstał projekt, który przejął te aplikacje i coś z nimi robi. Wrzucone są także na #fdroid , więc wygląda, jakby to było coś poważniejszego.
Wie ich eben hier im Fediverse durch einen Beitrag von @citoyen_candide, weitergesagt durch @anonymiss gesehen habe, wurde Simple Mobile Tools verkauft. Folgender Artikel bestätigt das auch noch einmal. Das ist traurig, da diese Opensource Tools von recht vielen Menschen genutzt werden welchen Opensource, Datenschutz, sparsamer Gebrauch von Rechten etc. wichtig ist. Und so kann man nur hoffen das die Anwendungen geforked und dann von der Community weiter entwickelt werden.
i just want a simple editor, like a word editor, like a google doc or something, that will spit out a basic accessible static html page or two for me, ptooey!
I can read html/css but not spit it out in my sleep
Like what can it do that Simple #Queue Service can't? I know it's push based and that has it's benefits, and obvs it has integrations with SMS/email that probably come in handy, but those seem like improvements you could just make to #SQS instead of having a whole separate system.
@schizanon It’s for a different kind of use case. Decoupling control to allow for limited self-service, or to allow one part of your system to not have “knowledge” of other parts.
I also tend to think of SQS as just a way to distribute work across many workers, while SNS is a way to publish notifications of when things happened. I don’t always need to distribute those notifications across workers, so I can choose to subscribe a Lambda, or if I have high volume I can subscribe an SQS queue and use a poller running in ECS/Fargate. My publishing code doesn’t need to know what the consumer is doing.