How is the micro blogging part of sublinks gonna work out ? Is it similar to mbin? if so how would lemmy app be compatible with it ?
How is the micro blogging part of sublinks gonna work out ? Is it similar to mbin? if so how would lemmy app be compatible with it ?
Also are you guys/gals also add anymore federated services support in the future like pixelfed or frendica ?
You're viewing a single thread.
There is talk of having post types. This would allow for further fediverse integrations to function better.
To answer your questions:
- 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.
- Yes, we're building our federation service to include as many services as possible.
Ah thanks
Are there any apps being developed for Sublinks?
Not that I'm aware of. We will support all Lemmy apps when we launch though.
Lemmy apps will be compatible thanks to the Lemmy API
I’m confused now, the post above says that there will be initial compatibility but after that (presumably as sublinks evolves) Lemmy apps will have to display as best they can.
That's indeed it: initial compatibility which might change as SL evolves
That was my reason for asking about sublinks apps.
I know that devs like web interfaces but the truth is you need apps if anything social is going to become established.
It’s a sad fact in the fediverse that routinely apps or even front end GUI aren’t compatible. There’s only so many times this can happen (or instances shut down or not be maintained) before it all becomes a bit much.
So I think relying on Lemmy apps is a mistake.
It's really to early too know any of this.
Depending on the community (instance admin included) reception of Sublinks, several scenarios can happen
- a lot of major instances switch to Sublinks
- only a few instances switch to it
As Sublinks will be compatible with Lemmy apps at that time, there will be a time where both will coexist as options to use with the apps. Application developpers will probably cater to the most population solution, whatever that is. Ultimately, Lemmy and Sublinks won't probably be fully compatible anymore, and apps will need to choose.
It's actually kind of already the case with Mbin, which doesn't have as many clients as Lemmy, while still allowing users to interact with the Lemmy communities.
Yes, my point is that an App or apps should be part of the design from the outset (see Pixelfed) Good planning rather than chance and potentially messing / confusing people.
The site will be a PWA. Not an app but something for people to use on mobile that could possibly be distributed on app stores
Seems like a good idea, a la Voyager
Aren’t there problems with authentication that cause security concerns when using a PWA?
Which is why the native apps are preferred for Voyager.
I mean if you don't secure it sure. The same goes for any site though and can be mitigated by having decent security. There was the thing a bit ago with Apple trying to discontinue PWAs in the EU due to the ruling that PWAs on apple devices shouldnt need to only be able to rely on webkit (their browser engine) which is why the voyager creator said to move over to native but them discontinuing PWAs got walked back