@BiggestBulb
@kbin.runI have been creating a bot using Node and would love to have a cloud-based logging solution to store my logs (since Fly.io monitoring isn't the greatest and doesn't store logs more than ~100 at a time). So far, I've looked at:
Sadly, all of these require a business email.
Since I'm doing a small personal project, I don't quite have one and I would prefer not to have to get one. I would also prefer the logging service be as simple as possible - this is a very small project and isn't customer-facing, so it really only needs the logging features (stuff like metrics are not needed and I'm handling exception logging with Sentry).
Lastly, it would be cool if it was cheap / free!
Thank you!
For example, if I (on kbin.run - which is Mbin, but for the purposes of this let's just assume it's Kbin) go to a random magazine on kbin.social, I will often see a prompt that the magazine may be incomplete and that I should visit the original instance for all the content.
Why doesn't the request to that magazine automatically trigger a "pull" from that instance for that magazine, or at least cause it to check if the number of threads is the same (and conditionally pull on that)? I would think by pulling the changes then, magazines would never be out-of-date.
I get that it would be a lot heavier of a load on the servers, but in combination with good caching techniques (maybe setting a time of 1 day or something until the next pull occurs, idk) I feel like that could be mitigated.
Is this maybe an implementation detail of ActivityPub?
Thank you!
This is the one thing keeping me from using Ecosia at this point. I use year filters a LOT as a programmer, and I really don't like how shady Brave generally is. However, even changing "freshness" to "year" in the URL just makes it get set to "any time", which is not ideal.
Is this an issue that is overcome-able somehow? Alternatively, are there any decent Ecosia alternatives out there which actually have a "year" filter?
Thank you!