aka freamon

Codeberg: https://codeberg.org/freamon?tab=activity

Anything from https://lemmon.website is me too.

  • 5 Posts
  • 127 Comments
Joined 7 months ago
cake
Cake day: March 27th, 2024

help-circle

  • How does Piefed handle image attachments, btw?

    For comments: not at all. If a Mastodon user tried to do what I did, with the inline image, nothing would show.

    We could do what I think you’ve done, and regex the details of the attachment into ! [] () Markdown and add it to the text. There’s also a DB relationship between comments and images that isn’t used, but could be, I suppose.

    I’ve never actually seen a Mastodon user try to add an image to something that ended up as a Lemmy comment, tbh, so it’s not something I’ve thought too much about.


  • I just tried with Masto - maybe there’s different versions, but it didn’t work with the one I tried.

    Screenshot:

    It’s probably for the best that this PR doesn’t also convert inline Markdown into an attachment to send out for Mastodon’s benefit, because then there would be the danger of apps that understand both showing two images. It’d be better if Mastodon did the translation when receiving stuff, but Mastodon doesn’t seem as good as MBIN when it comes to co-operating with Lemmy.

    (edit: how that screenshot shows on MBIN is a bit disappointing though - at least looking at on the web)





  • Interesting. Funnily enough, my comments are coming through to Lemmy as ‘Undermined’ too (just a PieFed bug, easily fixed), so the fact that you saw it (as well as the comments by the others I mentioned) means it’s not a language thing. That’s good, in a way, because it should be physically impossible to actually de-select it.

    So, sorry - at least we can rule one thing out, but I don’t have any more suggestions.


  • That community only accepts posts in ‘undermined’ language, so if you aren’t seeing anything from there, but you can when you log out (to simulate everyone else’s view of it), then it’s probably a user setting that prevents you from seeing stuff from that language. If you go to the ‘collapse’ community and posts by ‘Midnight’ are missing, then it’ll be that (similarly there’s a comment here from ‘originallucifer’ - if you haven’t seen it, it’s 'cos of the language thing).



  • That comment chain demonstrates a real appeal of Reddit. Even for something like a post-episode TV discussion, a critical mass of people means that not only can you have the discussion in the first place, but there might be some extra info from someone who worked on the set, or attended an audience taping.

    You can click to see the rest of the comments to see plenty wrong with Reddit too, but it’s not like there’s any particular drive to prevent the elements of Reddit culture that I find annoying from coming to Lemmy too.

    I’d be surprised if there’s ever a critical mass of people on a federated app though. If there is, it’s more likely to be on something with the proper funding, that hides the details from regular users (e.g
    it’ll be BlueSky, not Mastodon). On Reddit, Lemmy has a reputation for being too complicated, for the mundane reason that is. Too much stuff that should happen doesn’t, and the answer to why are the stuff that ‘normies’ don’t want to hear (LW and PD instances are both a bit unstable atm), or they’re so unintuitive that that they’ll need answering forever (e.g everything around discussion languages, instance blocks, newly-discovered communities , etc etc).

    I’ve just seen a user accidentally submit the same post to the same community multiple times (the worst I’ve seen is 4 times). Preventing that is some real ‘web dev 101’ shit. Federated apps can be an interesting hobby for inexperienced devs (like me), and mildly diverting for anyone who wants to use them as a user, but a critical mass of users?! Forget about it.





  • The vote count for comments is something I’ll work on next. The idea is that if you have a high reputation (your stuff if upvoted more than downvoted), then you get an extra one (your comments start at 2, because it’s one from you, and one bonus one). But you’re not the first person to question it, and find it counter-intuitive. So I’ll probably change it so that a high reputation effects the internal score (which is used for ranking) but not the visible upvotes.

    p.s. Lemmy’s changes re: batching are to fix its own problems with queues over long geographical distances. It’s unrelated to backfilling content from other instances: that’ll stay the same - every instance on every software platform will have some stuff missing compared to where it’s originally hosted (if it’s not because the content pre-dates the federation, it’ll be because of de-federation, or bans, or timeouts, or some activitypub mystery (someone was asking the other day about why a post from feddit.org hadn’t made it to lemmy.world and there was no real satisfactory answer to my mind)).




  • 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.


  • 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).


  • 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).