I read somewhere that they plan to have a paid level without commercials. Which is shitty.

That shouldn’t be a problem to add. The application will be event-driven and that’s the core of what is needed to fire push notifications.

I think there should be a separate community for it though.

Which communities do you follow? Perhaps there are more alive ones on different instances?

Mostly the v0.2 release which has a major focus on moderation enhancements. Some things might be delayed, removed, or added to releases due to the feedback.

Not that I’m aware of. We will support all Lemmy apps when we launch though.

I know, I tried to make it sound friendly and not anti-Lemmy.

No, it will help our development be more focused on the highest-impact items. It should allow for a more organized and targeted release timeline.

There is talk of having post types. This would allow for further fediverse integrations to function better.

To answer your questions:

1. Sublinks isn’t a copy of Lemmy. There used to be a greater focus on multiple post types, but now it’s not a main feature to work on. Sublinks is an alternative to Lemmy that adheres to the Lemmy API to capture the client base for that API. Sublinks has its API for its front-end and any apps being developed for Sublinks.

Being long-term compatible with Lemmy isn’t a priority either. We set our first milestone to be parity with the Lemmy API contracts to allow for apps to work from the start. As we grow our footprint Lemmy would have to display it the best they can. We don’t plan to add support for Sublinks into other applications.

2. Yes, we’re building our federation service to include as many services as possible.

I agree. It’s not a contest, we are in this together.