Hello. Hopefully we’re in deep enough in the comments for meta-chat not to be too annoying for others. Re: hotlinking from fandom sites - a search around the web suggests that other sites struggle with it too, because it looks like the ‘fandom’ people try to prevent it, and send a blank image whenever they detect it.
I don’t know how Lemmy gets away with it. I tried re-arranging elements the same way that Lemmy does, and it didn’t work. However, I have found that if you replace the word ‘static’ in the URL, with the word ‘vignette’, then that does work. This is the kind of thing that can be automated, so it can be fixed in a future commit.
Demo below (in spoiler tags to try to reduce the clutter for others):
demo
Edit: I’ve also been adding an API to PieFed and testing it out with a fork of Lemmy’s Thunder app - using this seems to solve both problems: it can render the image without shenanigans, and it provides a preview too (I doubt preview functionality will be added to the main raw website if it requires significant amounts of JavaScript, 'cos we’re trying to avoid that).
Omg that is beautiful! Yes as you say that particular style of image was really hard to get working as Lemmy likewise struggled with it - perhaps you arrived at the same or similar solution, but even if yours is a totally different solution that’s awesome that you’ve already cracked it!:-)
I’ve been trying to keep a list of things I am experiencing, though some of it were things that I encountered on a smaller Lemmy instance as well, like delays in federation - e.g. I pulled in this post https://piefed.social/post/295422 but it shows (to me) as having zero comments, when in reality it should have 18. Though I am guessing that there is a quite good chance that it may catch up in the next day or two. I also tried to “leave” and then re-“join” some communities, in case that may help trigger the federation action to pull from the original host.
Hey I have a question that you may enjoy, and if not then that’s okay to tell me too:-). On a Mac desktop using Chrome, I cannot simply do the left-swipe to use the “back button” to return to a previous page. That works on Lemmy, but not PieFed. Although moving the mouse way up to the actual Back button works, as does keyboard shortcuts (command-leftarrow). And the same for right-swipe / Forward button. I am not sure if I am even using the correct terminology there but I hope that helps:-). It seems so silly, but since it is something that I may do tens of times each hour, possibly multiple times per minute at peak, I find that it really slows down the navigation. Is that something that others have mentioned and/or that could perhaps be fixed, or is this something too deeply ingrained in how the UI works? Making for a “smoother experience” seems like it would be a good thing if possible though.
And either way, I hope this conversation is interesting to you:-).
Re: that post of on “ye power trippin’ bastards”, those comments will never come through. I’d guess that you pulled that post after the comments had been made, so they won’t federate out again, because they only do that when they’re originally created (or updated). Leaving and Joining won’t make any difference. There’s an argument that we should fetch a comment if we receive an upvote for it, but Rimu wasn’t too keen on it last time it was raised.
Re: swiping with Mac. I had no idea that was possible tbh, but I just tried it on my old MacBook Air, and it turns out that the two-finger swiping works in Safari, on PieFed as well as any other sites. This suggests that it’s a problem with Chrome, but I wouldn’t know where to look for a fix (it’s not the kind of functionality that websites have much involvement in - they don’t need to do anything to enable it, and would struggle to disable it, beyond the usual ‘back-button’ capture that some dodgy sites do, but PieFed doesn’t).
So aside from waiting for code changes, and pointing out some issues whenever I see them, do you have suggestions for things to do in the meantime?
One seems to be: don’t pull in posts manually like that - b/c for one thing, doing it that way means that the comments will never come. Then again, waiting for automated federation syncing seems unlikely to work either. Basically old posts are a lost cause at this point, without admin assistance? Also, I did not notice this at first, but the 3 posts that were already in that community prior to me pulling in the other 2 posts 2 days ago likewise have zero comments in them. Though newer - but not older - voting seems to be taking place, yet starting from a zeroed mark (at the time of the pull?) rather than the proper count on the original instance. e.g. the one by Blaze has 2 (is there a way to view this broken down by up & down separately?) rather than 43, and the dunk_tank one has zero rather than 13, and none of the other posts in that entire community show up. Also the ones that I pulled in have altered counts as well - e.g. the BonesOfTheMoon one now has -2, when the original instance displays -12.
To me this seems an argument to abolish the entire pulling in posts manually feature altogether, until and unless it is changed to pull it in “properly”, i.e. with all comments and vote counts intact. Otherwise, this is at minimum highly confusing to people and realistically it is even “misinformation”, is it not? e.g., in a hypothetical scenario, a post could have +1000 upvotes, but then someone pulls it in, and it receives 5 downvotes, making the total vote count as “-4” (since it would go through zero I would presume?), which would represent a fully qualitative rather than merely quantitative change in the presentation of such a post. +1000 minus 5 is a totally different “type” of change (barely noticable) than 0 minus 5 (finalizing at outright disliked, yet mostly ignored).
It would be better to have nothing at all than to present things in a confusing manner such as this. Ofc, this is not unique to PieFed - I see similar struggles on my own posts between StarTrek.website and Discuss.Online and Lemmy.World, with variations of vote counts and even number of contents - though the difference is that Lemmy eventually catches up, while it seems that you are saying that PieFed never will?
If space is the limiting issue, then delete everything after a cutoff like 6 months or a year. If network bandwidth is the issue then… I dunno about that, but that’s the task that must be worked out. Perhaps Lemmy’s upcoming update to 0.19.6 offering batch updates rather than sending each individual one alone will help? This isn’t a minor issue imho - this is the kind of stuff that will turn people away. Although if it is on the books to be worked on at a later time that’s understandable.
Thank you very much for the suggestion about Safari - I never use that browser, but that’s good to know. Fwiw, I also notice the same behavior on Firefox as on Chrome. And on Android Firefox I can go back just fine. So it’s not specific to Chrome, and I doubt it is fully specific to Mac though that could be the major one affected.
Btw Lemmy captures the back button properly when you have started to write a comment and it asks you if you are sure that you want to leave and thereby lose that. PieFed I suspect isn’t doing quite that but there may be something along the lines of where the focus is placed in order to provide the keyboard shortcuts, or something I dunno. I know basic syntax of HTML, CSS, and a tiny bit of JavaScript, plus Java, C++ and many other languages, but who can keep up with the modern web these days - it’s a shitstorm of everything affecting everything else, and even the browsers themselves seem to DGAF to make things “just work” anymore, even on Windows but all the more so everywhere else.:-(
One thing I would argue should be changed is that when making a reply, the Comment box should automatically receive focus. Eventually the entire process of making a comment should be made in-line so as not to disrupt the browsing experience, but that’s a small change that should be easy to make and would help. I will keep a list of small things like that in case such suggestions could help:-).
Re: votes and comments for old content - you’ve noticed the same problems on PieFed as on smaller Lemmy instances, because they have the same root cause: we can only get what Lemmy will give us.
The ‘retrieve remote post’ function was originally written for PeerTube integration. If you fetch a post from there, you can then query the ‘favorites’ outbox to get voting info, and the ‘replies’ outbox to get comments. You can’t do that with Lemmy - it considers voting data to be private, and it doesn’t provide a ‘replies’ outbox. The only outbox that Lemmy provides is for posts, that provides the text for the most recent 50 posts, but nothing else (FWIW, the posts outbox for PieFed communities includes the replies along with each post, but - again - not the votes).
When a PieFed or other Lemmy instance first becomes aware a community that’s hosted on a remote Lemmy instance, it processes the posts outbox. The ‘retrieve remote post’ function is there for if you want a post that’s older than the ones provided in the outbox, or if someone before you discovered that community but didn’t subscribe (the remote community won’t send anything to piefed.social if no-one there is subscribed to it, so we can end up with a situation where we have the old posts but not the newer ones).
For votes: the hypothetical scenario of a post having +1000 on its home instance, but -4 on a remote one, is a real possibility, but that’s a bigger problem than just PieFed. Using ActivityPub, Lemmy doesn’t provide a post score, and even if it did (or you grabbed it using their API), it doesn’t say where the votes have come from. You need to know this, because otherwise you’ve no idea what a future vote will mean (is a ‘downvote’ reversing a previous downvote, or is it a new downvote?). There’s an inconsistency in PieFed, whereby a post retrieved from an outbox starts at +0, but a manually retrieved one starts at +1, but it doesn’t really matter that much, because they’re both as wrong as the other (we’ve no idea whether the OP kept the automatically assigned upvote that they got with a new post).
For comments: old ones are a lost cause (even for admins). Lemmy is a bit better at backfilling these - if it receives a vote for a missing comment, it’ll fetch it. I’d imagine though there’s a complexity limit to this (it’ll get a comment if it’s in reply to comment or a post it already has, but it’s not going to recursively climb up the parent tree to resolve everything if it doesn’t already have it). Also, it depends on votes coming through - lemmy.ml probably has about 3 years of comments that lemmy.world will never get, because nobody is going to vote on them. Again, it’s a bigger problem than just PieFed.
For UI stuff: I’m not the best person to talk to - I’ve only just found out that you can swipe about on a Mac desktop, and that’s because you’ve told me. The main websites of PieFed instances are deliberately old-skool (mostly just HTML and CSS) - this is what a chuck of the Fediverse says they want, but also what a chunk trips up on, because they’ve been spoiled by the conveniences provided by more modern web interfaces. That’s not to say that the problems you’ve mentioned are insurmountable, it’s just that they are best posted as an Issue on codeberg or in a community like !piefed_meta@piefed.social, where folks who’ve much more web development experience than me will see them.
That’s very interesting, thank you for taking the time to explain!
Votes: yes I’ve noticed that a good deal of what I see has +1 vote added to it - including your comment here. In one case it was so deep and delivered within seconds before I saw it that it convinces me that it is due to a systemic bug. Also when I return to a page after making a comment, sometimes I see replies that I could swear that I had upvoted, but it does not show the green indicator for that, and it allows me to vote again. Fwiw, I have “vote privately” set to OFF.
Separately for voting, I would hope to see both up and downvotes displayed - I often have replies at “1”, and I have to go to the source Lemmy to get the information as to whether it is truly just unvoted on entirely or more likely it was a balance of +1 and -1, sometimes +2 and -2, and more rarely but definitely happens that sometimes it’s +3 and -3. Or other similar scenarios like +7 and -5, for a certain award-winning video I shared but that people did not universally seem to enjoy. The downvotes are still “information” and present a form of “active engagement” that merely showing the total score hides away.
Old posts: if I could suggest something, maybe it would be better to only “view” an older post - so like retrieve it only into a temporary location, and then discard later - without trying to retain it and present it to users as if it were really there. Perhaps that would increase consistency and therefore build more trust in the system, when information is not there sometimes and not there other times, but consistently absent always prior to a certain date and then afterwards always there and up to date. Though that seems to go beyond Lemmy’s functionality, and yet being better is the point:-).
Anyway, I hope this was interesting and it may help me work out the language on some of these issues before I post them in piefed_meta, so it’s definitely interesting and helpful for me:-).
Now to press the “Comment” button and hope that I don’t accidentally hit the Leave button instead, thereby discarding all that I typed as well as kicking me out of this community, as I did earlier today somewhere, whoopsie!:-)
You can see the upvotes vs downvotes if you hover your cursor over the score. The old layout displayed both, but there’s pros and cons to combined vs. separate vote info. Videos pretty much always attract a disproportionate amount of downvotes, btw - it’s just one of those Lemmy things.
I don’t know how technically viable a temporary-only retrieval of a post would be. If you look at any given post across multiple instances, every one has its “own truth” for one reason or another, and it’s just something that I’ve started to accept comes with the territory.
Oh that’s neat! Can I see the downvotes on a mobile? Long press or … doesn’t seem to do anything and I’m out of ideas to try.
The difference between PieFed’s approach and Lemmy’s, especially after the upcoming 0.19.6, is that Lemmy seems to catch up eventually, whereas PieFed never will no matter how much time passes - is that correct?
So if what is desired is a “search for existing post”, that function would go better into the search box, while if what is desired is “import existing post”, yet that is impossible then perhaps simply not offer that rather than confuse people by offering a halfway measure, thereby leaving only the “find non-existing post”, which now that I think about it, especially since it needs an external URL to trigger it, is that really even something that anyone would want? i.e. if the goal is to “view” it, and someone must go to Lemmy in order to do so, then so be it (it is the same on smaller, newer Lemmy instances too), but since it cannot be imported (properly/fully), then don’t? Well, it’s a thought anyway!:-)
Hello. Hopefully we’re in deep enough in the comments for meta-chat not to be too annoying for others. Re: hotlinking from fandom sites - a search around the web suggests that other sites struggle with it too, because it looks like the ‘fandom’ people try to prevent it, and send a blank image whenever they detect it.
I don’t know how Lemmy gets away with it. I tried re-arranging elements the same way that Lemmy does, and it didn’t work. However, I have found that if you replace the word ‘static’ in the URL, with the word ‘vignette’, then that does work. This is the kind of thing that can be automated, so it can be fixed in a future commit.
Demo below (in spoiler tags to try to reduce the clutter for others):
demo
Edit: I’ve also been adding an API to PieFed and testing it out with a fork of Lemmy’s Thunder app - using this seems to solve both problems: it can render the image without shenanigans, and it provides a preview too (I doubt preview functionality will be added to the main raw website if it requires significant amounts of JavaScript, 'cos we’re trying to avoid that).
Omg that is beautiful! Yes as you say that particular style of image was really hard to get working as Lemmy likewise struggled with it - perhaps you arrived at the same or similar solution, but even if yours is a totally different solution that’s awesome that you’ve already cracked it!:-)
I’ve been trying to keep a list of things I am experiencing, though some of it were things that I encountered on a smaller Lemmy instance as well, like delays in federation - e.g. I pulled in this post https://piefed.social/post/295422 but it shows (to me) as having zero comments, when in reality it should have 18. Though I am guessing that there is a quite good chance that it may catch up in the next day or two. I also tried to “leave” and then re-“join” some communities, in case that may help trigger the federation action to pull from the original host.
Hey I have a question that you may enjoy, and if not then that’s okay to tell me too:-). On a Mac desktop using Chrome, I cannot simply do the left-swipe to use the “back button” to return to a previous page. That works on Lemmy, but not PieFed. Although moving the mouse way up to the actual Back button works, as does keyboard shortcuts (command-leftarrow). And the same for right-swipe / Forward button. I am not sure if I am even using the correct terminology there but I hope that helps:-). It seems so silly, but since it is something that I may do tens of times each hour, possibly multiple times per minute at peak, I find that it really slows down the navigation. Is that something that others have mentioned and/or that could perhaps be fixed, or is this something too deeply ingrained in how the UI works? Making for a “smoother experience” seems like it would be a good thing if possible though.
And either way, I hope this conversation is interesting to you:-).
Re: that post of on “ye power trippin’ bastards”, those comments will never come through. I’d guess that you pulled that post after the comments had been made, so they won’t federate out again, because they only do that when they’re originally created (or updated). Leaving and Joining won’t make any difference. There’s an argument that we should fetch a comment if we receive an upvote for it, but Rimu wasn’t too keen on it last time it was raised.
Re: swiping with Mac. I had no idea that was possible tbh, but I just tried it on my old MacBook Air, and it turns out that the two-finger swiping works in Safari, on PieFed as well as any other sites. This suggests that it’s a problem with Chrome, but I wouldn’t know where to look for a fix (it’s not the kind of functionality that websites have much involvement in - they don’t need to do anything to enable it, and would struggle to disable it, beyond the usual ‘back-button’ capture that some dodgy sites do, but PieFed doesn’t).
So aside from waiting for code changes, and pointing out some issues whenever I see them, do you have suggestions for things to do in the meantime?
One seems to be: don’t pull in posts manually like that - b/c for one thing, doing it that way means that the comments will never come. Then again, waiting for automated federation syncing seems unlikely to work either. Basically old posts are a lost cause at this point, without admin assistance? Also, I did not notice this at first, but the 3 posts that were already in that community prior to me pulling in the other 2 posts 2 days ago likewise have zero comments in them. Though newer - but not older - voting seems to be taking place, yet starting from a zeroed mark (at the time of the pull?) rather than the proper count on the original instance. e.g. the one by Blaze has 2 (is there a way to view this broken down by up & down separately?) rather than 43, and the dunk_tank one has zero rather than 13, and none of the other posts in that entire community show up. Also the ones that I pulled in have altered counts as well - e.g. the BonesOfTheMoon one now has -2, when the original instance displays -12.
To me this seems an argument to abolish the entire pulling in posts manually feature altogether, until and unless it is changed to pull it in “properly”, i.e. with all comments and vote counts intact. Otherwise, this is at minimum highly confusing to people and realistically it is even “misinformation”, is it not? e.g., in a hypothetical scenario, a post could have +1000 upvotes, but then someone pulls it in, and it receives 5 downvotes, making the total vote count as “-4” (since it would go through zero I would presume?), which would represent a fully qualitative rather than merely quantitative change in the presentation of such a post. +1000 minus 5 is a totally different “type” of change (barely noticable) than 0 minus 5 (finalizing at outright disliked, yet mostly ignored).
It would be better to have nothing at all than to present things in a confusing manner such as this. Ofc, this is not unique to PieFed - I see similar struggles on my own posts between StarTrek.website and Discuss.Online and Lemmy.World, with variations of vote counts and even number of contents - though the difference is that Lemmy eventually catches up, while it seems that you are saying that PieFed never will?
If space is the limiting issue, then delete everything after a cutoff like 6 months or a year. If network bandwidth is the issue then… I dunno about that, but that’s the task that must be worked out. Perhaps Lemmy’s upcoming update to 0.19.6 offering batch updates rather than sending each individual one alone will help? This isn’t a minor issue imho - this is the kind of stuff that will turn people away. Although if it is on the books to be worked on at a later time that’s understandable.
Thank you very much for the suggestion about Safari - I never use that browser, but that’s good to know. Fwiw, I also notice the same behavior on Firefox as on Chrome. And on Android Firefox I can go back just fine. So it’s not specific to Chrome, and I doubt it is fully specific to Mac though that could be the major one affected.
Btw Lemmy captures the back button properly when you have started to write a comment and it asks you if you are sure that you want to leave and thereby lose that. PieFed I suspect isn’t doing quite that but there may be something along the lines of where the focus is placed in order to provide the keyboard shortcuts, or something I dunno. I know basic syntax of HTML, CSS, and a tiny bit of JavaScript, plus Java, C++ and many other languages, but who can keep up with the modern web these days - it’s a shitstorm of everything affecting everything else, and even the browsers themselves seem to DGAF to make things “just work” anymore, even on Windows but all the more so everywhere else.:-(
One thing I would argue should be changed is that when making a reply, the Comment box should automatically receive focus. Eventually the entire process of making a comment should be made in-line so as not to disrupt the browsing experience, but that’s a small change that should be easy to make and would help. I will keep a list of small things like that in case such suggestions could help:-).
Re: votes and comments for old content - you’ve noticed the same problems on PieFed as on smaller Lemmy instances, because they have the same root cause: we can only get what Lemmy will give us.
The ‘retrieve remote post’ function was originally written for PeerTube integration. If you fetch a post from there, you can then query the ‘favorites’ outbox to get voting info, and the ‘replies’ outbox to get comments. You can’t do that with Lemmy - it considers voting data to be private, and it doesn’t provide a ‘replies’ outbox. The only outbox that Lemmy provides is for posts, that provides the text for the most recent 50 posts, but nothing else (FWIW, the posts outbox for PieFed communities includes the replies along with each post, but - again - not the votes).
When a PieFed or other Lemmy instance first becomes aware a community that’s hosted on a remote Lemmy instance, it processes the posts outbox. The ‘retrieve remote post’ function is there for if you want a post that’s older than the ones provided in the outbox, or if someone before you discovered that community but didn’t subscribe (the remote community won’t send anything to piefed.social if no-one there is subscribed to it, so we can end up with a situation where we have the old posts but not the newer ones).
For votes: the hypothetical scenario of a post having +1000 on its home instance, but -4 on a remote one, is a real possibility, but that’s a bigger problem than just PieFed. Using ActivityPub, Lemmy doesn’t provide a post score, and even if it did (or you grabbed it using their API), it doesn’t say where the votes have come from. You need to know this, because otherwise you’ve no idea what a future vote will mean (is a ‘downvote’ reversing a previous downvote, or is it a new downvote?). There’s an inconsistency in PieFed, whereby a post retrieved from an outbox starts at +0, but a manually retrieved one starts at +1, but it doesn’t really matter that much, because they’re both as wrong as the other (we’ve no idea whether the OP kept the automatically assigned upvote that they got with a new post).
For comments: old ones are a lost cause (even for admins). Lemmy is a bit better at backfilling these - if it receives a vote for a missing comment, it’ll fetch it. I’d imagine though there’s a complexity limit to this (it’ll get a comment if it’s in reply to comment or a post it already has, but it’s not going to recursively climb up the parent tree to resolve everything if it doesn’t already have it). Also, it depends on votes coming through - lemmy.ml probably has about 3 years of comments that lemmy.world will never get, because nobody is going to vote on them. Again, it’s a bigger problem than just PieFed.
For UI stuff: I’m not the best person to talk to - I’ve only just found out that you can swipe about on a Mac desktop, and that’s because you’ve told me. The main websites of PieFed instances are deliberately old-skool (mostly just HTML and CSS) - this is what a chuck of the Fediverse says they want, but also what a chunk trips up on, because they’ve been spoiled by the conveniences provided by more modern web interfaces. That’s not to say that the problems you’ve mentioned are insurmountable, it’s just that they are best posted as an Issue on codeberg or in a community like !piefed_meta@piefed.social, where folks who’ve much more web development experience than me will see them.
That’s very interesting, thank you for taking the time to explain!
Votes: yes I’ve noticed that a good deal of what I see has +1 vote added to it - including your comment here. In one case it was so deep and delivered within seconds before I saw it that it convinces me that it is due to a systemic bug. Also when I return to a page after making a comment, sometimes I see replies that I could swear that I had upvoted, but it does not show the green indicator for that, and it allows me to vote again. Fwiw, I have “vote privately” set to OFF.
Separately for voting, I would hope to see both up and downvotes displayed - I often have replies at “1”, and I have to go to the source Lemmy to get the information as to whether it is truly just unvoted on entirely or more likely it was a balance of +1 and -1, sometimes +2 and -2, and more rarely but definitely happens that sometimes it’s +3 and -3. Or other similar scenarios like +7 and -5, for a certain award-winning video I shared but that people did not universally seem to enjoy. The downvotes are still “information” and present a form of “active engagement” that merely showing the total score hides away.
Old posts: if I could suggest something, maybe it would be better to only “view” an older post - so like retrieve it only into a temporary location, and then discard later - without trying to retain it and present it to users as if it were really there. Perhaps that would increase consistency and therefore build more trust in the system, when information is not there sometimes and not there other times, but consistently absent always prior to a certain date and then afterwards always there and up to date. Though that seems to go beyond Lemmy’s functionality, and yet being better is the point:-).
Anyway, I hope this was interesting and it may help me work out the language on some of these issues before I post them in piefed_meta, so it’s definitely interesting and helpful for me:-).
Now to press the “Comment” button and hope that I don’t accidentally hit the Leave button instead, thereby discarding all that I typed as well as kicking me out of this community, as I did earlier today somewhere, whoopsie!:-)
You can see the upvotes vs downvotes if you hover your cursor over the score. The old layout displayed both, but there’s pros and cons to combined vs. separate vote info. Videos pretty much always attract a disproportionate amount of downvotes, btw - it’s just one of those Lemmy things.
I don’t know how technically viable a temporary-only retrieval of a post would be. If you look at any given post across multiple instances, every one has its “own truth” for one reason or another, and it’s just something that I’ve started to accept comes with the territory.
Oh that’s neat! Can I see the downvotes on a mobile? Long press or … doesn’t seem to do anything and I’m out of ideas to try.
The difference between PieFed’s approach and Lemmy’s, especially after the upcoming 0.19.6, is that Lemmy seems to catch up eventually, whereas PieFed never will no matter how much time passes - is that correct?
So if what is desired is a “search for existing post”, that function would go better into the search box, while if what is desired is “import existing post”, yet that is impossible then perhaps simply not offer that rather than confuse people by offering a halfway measure, thereby leaving only the “find non-existing post”, which now that I think about it, especially since it needs an external URL to trigger it, is that really even something that anyone would want? i.e. if the goal is to “view” it, and someone must go to Lemmy in order to do so, then so be it (it is the same on smaller, newer Lemmy instances too), but since it cannot be imported (properly/fully), then don’t? Well, it’s a thought anyway!:-)
What’s happening with 0.19.6 ?