Yeah I read the original announcement. I know it was a team effort. But still, this is your sever and your responsibility.
Yeah I read the original announcement. I know it was a team effort. But still, this is your sever and your responsibility.
Could be the instance with the raving tankies that was defederated.
Besides the actual developers of lemmy, none has done more for the lemmiverse than the maintainers of lemmy.word. When the Reddit shitstorm started and other leading servers shut down user registration, you guys held the ship steady and didn’t flinch from the sudden flood of new users. Discovering new bottle-necks in lemmy code, helping to resolve them and deploying hot fixes. All in super fast reaction time. About “lemmy.world shouldn’t be largest server” crap - it’s good for lemmy that one server is the easy entry point to lemmy. This is where the “mainstream” communities could/should be and new users will have an easier landing. Having dedicated servers with their own communities (like start trek, piracy, etc) is great but it’s not mandatory for all communities.
A design that scales. Forwarding every like, post and comment to all federated servers will not scale well.
Mastodon exists. It’s pretty good. Using 2 apps is fine.
I write down everything I built so for plus future plans in OneNote. This kind of defeats the purpose of self hosting but I want to keep a written copy complete off site in case if a complete loss. Plus I like OneNote. It’s actually a well designed product. Scripts, docker compose files and such are in GitHub.
That really depends on how you treat the media you download. Is it just a temp buffer that you delete after watching or is it a collection you grow and curate over time.
Wow that’s a great idea
In retrospect, I’m really glad all of this shit with Reddit happened and lemmy became a thing in my life. Was bummed initially when Apollo died, but now despite needed polish in lemmy apps, the experience here is much much better and I would never go back.
For app data, Borg as backup/restore software. Backup data is then stored on Hetzner as an offsite backup - super easy and cheap to setup. Also add healthchecks.io to get notified if a backup failed.
Edit: Backup docker compose files and other scripts (without API keys!!!) with git to GitHub.
It’s literally takes 2 clicks to tunnel via a VPN
That sounds like an excellent solution for web based apps, but what about services like Plex or Nextcloud that use their own client side apps?
The easiest option ATM would be for an app to combine both communities into one synthetic feed
The easiest option ATM would be for an app to combine both communities into one synthetic feed
It feels like it is possible to have a conversation here. In Reddit I felt like my comments were getting buried
Those are good points. Don’t implement ActivityPub and avoid the problem all together.
I’d recommend Debian Linux. It’s free, stable, has all the software you’ll need with long term support, ton of online resources and communities to learn from. You can start with or without UI.
OP is correct. We have very little to to gain and everything to lose.
Yeah that’s a possibility. They could do something like “ohh too bad Killer Feature X is looking so badly on Mastodon. On Threads it will look so much better”. Essentially using fedi as a crappy demo for Threads. That sounds like a typical business plan to me.
I’m itching so hard to block both.