- Soap box
- Ballot box
- Jury box
- Bullet box
- ??? <- you are here
Phantom_Engineer
Bullshit. Nobody, or at least very few people, expected Reddit to revert the changes. A protest can be successful even if it doesn't lead to immediate change. I was here on Lemmy long before the API nonsense happened over at Reddit, and the difference over here is night and day. Lemmy has been around for awhile, but until these last few months it couldn't hold a candle to Reddit in terms of content or activity. Maybe it still can't, but now it has enough users to be viable. Reddit might go on like nothing happened, but in the background a competitor has been born.
Isn't this what all you lemmy-worlders got mad at Beehaw for doing? I don't think it's unreasonable to ask for a small statement from people as an anti-spam measure (a sort of advanced captcha), though of course the big problem there is reviewing all the applications in a timely manner. Still, I think there's room for more and less exclusive instances. The tools are there for instance owners to protect their instances however they choose.
Oh yeah, definitely not. FOSS combined with federation means that even if the main instance and dev team are toast, someone else could pick up where they left off and run with it. Lemmy doesn't necessarily need Lemmy.ml to function, which you couldn't say about voat (or Reddit, for that matter.)
Long term, the Fediverse is the way forward, but social media has staying power even if it dimishes from what it was. It will ages before the Fediverse replaces centralized social media, but I think it will slowly happen.
I'm not aware of any third party app trying to make the API pricing work. RIF and Red Reader are shutting down as well.
You can't lose money forever, not as a business. What's great about the Fediverse is that it makes social media something that can be done as a hobbyist project. Money is nice, but the hobbyist isn't necessarily out to make money.
Look into technical writing. I took it in college but I'm sure you can find free resources online about it. In short, good technical writing is:
Of course, that's easier said than done. It makes sense to make a rough outline of what you want to write before you write it. It's also good to look over what you've written afterwards. If you keep these basic principles in mind while planning, writing, and revising, you can make your writing more effective.