Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Yeah.....I've had to do a LOT of work client-side in Tesseract to give Lemmy half the features Piefed has. Eventually I'm gonna start targeting Piefed, but there's some under the hood stuff I'm waiting to be resolved before I embark on that voyage. Mainly, I've heard that the main Piefed experience and the API are not 1:1 and not everything is exposed in the API. :(
It's great to see you still posting on the Threadiverse! Okay so you've been doing it for awhile I guess but I've been sick myself so not staying up with things, anyway it's still great to see!! ๐
You may want to think about it from the ground up: a lot of the need for Tesseract was due to things like the strict authoritian stance of the tankie devs - e.g. not providing a means to truly block all users from an instance, or not showing alternative image text, or not embedding video playbacks - forcing you to find creative solutions to that problem (note PieFed does all of those things mentioned, usually not as comprehensively implemented as well as Tesseract does it but at least to some degree, e.g. Peer tube and YouTube videos can embedd but not Loops ones). Maybe now Tesseract would not have to be an entire alternative UI front-end - especially when the development pace of PieFed is so rapid in comparison to Lemmy that would increase your difficulty of keeping up - but instead rather a "theme", combined with changes to the underlying codebase that would affect all of the users of PieFed instead of only some of them? These devs I believe would be much more friendly and receptive to your ideas:-).
Although I am not a developer like you so too far away from the problem to see it anywhere close to clearly like you will, as you get into it, but wanted to throw out that oddball idea from left field in case it helps jar your thinking along creative lines. Remember to do six impossible things before breakfast each day!
collapsed inline media
But most important of all, if I can add, would be for you to enjoy it!!!
Good points.
I don't have a full plan yet (just the general idea of a plan), but when I start the journey to Piefed, it'll probably be from the ground up or very close to that. I already need to update the codebase from Svelte 4 to Svelte 5 which is a pretty big job due to the fundamental and breaking changes between those two versions.
The components that make up Tesseract (posts, comments, sidebars, everything) are also all heavily tied to Lemmy's type definitions. To support Piefed, I'd have to de-couple the components in the code from Lemmy's type def and add in an abstraction layer (both for future-proofing and to make it possible to support both if I wanted to).