My wife and I picked out her ring together. She has to wear it all the time. I think she should have say in the matter. Ask your partner to help you pick one out.
Yes, almost all team members are contributing code, designs, feature requests, etc. I called out @Rooki@lemmy.world specifically because he's been a major contributor. One of the admins is actively recruiting people to help contribute to Sublinks, this is how we got so much support so quickly. It's a very close collaboration. I owe a lot of thanks to the Lemmy.World team.
Yes, there is going to be a tool that exports from Lemmy via a direct database connection and adds to Sublinks via the API. Sublinks is heavily event driven by design. We'll want some events to trigger during import.
It's basically a fork of Lemmy. But rather than forking, we're rewriting the entire tech stack to something easier to support and enhance. You can see the full roadmap here: https://github.com/orgs/sublinks/projects/1
That’s the goal, yes.
The LW admins have helped contribute to Sublinks. They've given me full support and access to all resources to help grow it. They've been extremely helpful.
We are creating a Sublinks specific API that is much more optimized than the Lemmy one. Our front-end will be using that. Also, we'll have tons more features that the Lemmy core doesn't support.
The front-end is coming later. It’s fully compatible with Lemmy’s API so the demo site currently uses the Lemmy front-end.
Thanks a lot! There are currently 13 contributors; it's coming together very quickly. I'm super excited.
The front-end is coming later. It's fully compatible with Lemmy's API so the demo site currently uses the Lemmy front-end.
As winter continues, I think more and more about how nice it was to sit outside, drink coffee, and take pictures of birds that came by.
This is one of my favorite ones.
We now have a Pixelfed instance. Check it out!
Social.Photo. Signup is open!
A few Subreddits were planning to come over at the end of the month that didn't work out. Their members revolted and threatened to replace the mods. So they stayed over there. It would have been over 200k people if they all came over, even if not all members came. I thought I was under planning at the time.
I was reaching out to Reddit mods, trying to convenience them to join my instance. It almost worked, haha.
But in the end, I had to scale down while still maintaining something snappy. The DB is already over 15G, and I want to use a managed db. It's too large to put on smaller instances.
I hosted social.photo, which was a Pixelfed instance.
I had an uptick in users when I started to consider shutting down the site. It was the reason, ultimately, I decided to shut down as soon as possible. The software is awful, and I don’t want to deal with the issues multiplied by growth.
I decided to announce a shutdown by posting and hoping people see it because you can’t make an announcement to users on Pixelfed out of the box. I know there is an admin interface for it, but it doesn’t work.
Afterward, many of my new users told me they came from other instances that shut down.
This trend could be a blip as users create new accounts to migrate as they did before from their previous accounts. I know there is a user interface for this, but it doesn’t work.
Or it could be the terrible spam filter that blocks real users and allows bots. So, real users aren’t there to report bots. This is compounded by an uptick in new hype instances. These are sometimes poorly moderated instances full of bots awaiting returning interest from their owners to get cleaned up or closed.
Or it’s real!