I'm working on a Rust API wrapper around the existing common API to make it easier to use. Implemented the calls that could let someone do this exact thing at scale last night.
It's nowhere near ready for production and is still missing a lot of basic API functionality even for a simple bot, but I think it'll be ready to publicly release in an alpha state within the next couple days.
It'll probably slap you on a watchlist, but that's not really a huge accomplishment. As far as getting charged, it depends on where you live and what you say. If you start talking about blowing up buildings or something, well, I hope you have a good lawyer on retainer before the feds hunt you down.
I looked at the relevant code while checking how the voting API works, and part of it is that it checks if the instance has downvoting enabled. So, it doesn't bypass it because the instance wouldn't accept the downvote.
Maybe we need a post complaining about posts complaining about Reddit so we can complete the cycle until we need to add another link into the chain.
Yeah, I mentioned on another comment that storage space is the last thing to worry about, 1GB of storage is typically a fraction of a penny.
It stores them on a local pictrs server and pulls them from there, which, to my understanding, holds them for a week.
It's not that bad, I'm hosting my instance in a small corner of a friend's server and not making any impact on it.
That's correct. I'm replying to you on jamie.moe right now, but in reality, what I'm seeing is a copy of what lemmy.world has. When someone makes a post, leaves a comment, or whatever, all of the instances that are federated and have one subscriber in the relevant community get updated with the change.
When I read this thread, I'm actually reading a copy of the thread stored on my own instance, and my instance just tells lemmy.world when I leave a comment and it will update everyone else. While it isn't very storage efficient, it does even out the load since users on one instance only require a single update from the main instance for all of those users to interact with that content, rather than instances asking for copies of things every time a user on one instance needs it. It spreads out the load nicely and lets even underpowered hardware serve wider communities than it could otherwise.
The downside is you have to have the storage space to keep content for your user(s). Though, getting a lot of storage space isn't expensive at all, so I would say it's a minor concern. Lemmy uses little in terms of RAM and compute, those two factors are the biggest things that can up your cost really fast. A gigabyte of storage on a server can typically be gotten for a fraction of a penny.
I've coded most of my applications in that structure. It makes changing and testing things sane. Plus, if I need to make a large backend change, I can keep the abstractions compatible and have the rest of the app not notice.
Been happening. I suspect it's a UI bug from caching other posts, but I've seen it frequently.
Landlords HATE this one weird trick!
When I used the official Reddit app before I saw the light of RIF, I had push notifications. I didn't have them on RIF except when I opened it, and I found that to be a lot nicer on my psyche.
I have email notifications enabled on Lemmy right now, which turns into a push. But I don't really mind as much because the conversations here are nicer, and it's usually replies to me trying to be helpful, which are nice to see.