aka freamon

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

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

  • 2 Posts
  • 104 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.







  • Neat. It took me a while to realise what was going on: the post on Lemmy and the blogpost are two separate entities. The Lemmy post is a link to the blogpost, and the blogpost uses the post_id to fetch the comments (so I guess this means you have to make the blogpost, make the Lemmy post, and then go back and edit the blogpost with the correct id?)

    The script is inspectable on the blog - I can see it does:
    const url = 'https://lemmy.ml/api/v3/comment/listpost_id=21617067&limit=100&max_depth=8&sort=Top&type_=All';

    So I suppose there’s an inbuilt limit for comment depth and number of replies, but if you start down the road of working on that, you’ll eventually find that you’ve re-invented a front-end, and there’s no end to it.

    What the duckquill guys are doing is a bit fudgy, in that they’re getting another website to do the federation legwork for them, but the results are pleasing enough.



  • There’s a lot of drama in that Issue, and then, at the very end:

    Thanks for sharing your concerns here. We have been progressing use of our SDK in more use cases for our clients. However, our goal is to make sure that the SDK is used in a way that maintains GPL compatibility.

    the SDK and the client are two separate programs
    code for each program is in separate repositories
    the fact that the two programs communicate using standard protocols does not mean they are one program for purposes of GPLv3

    Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.


  • To my mind, the ideal would be that if you, as the person who wants to share some ‘open-source’ news, chose one community that you think is ‘best’ (based on what instance it’s on, if the mods are real people and are active, participation levels, whatever you think really). And we, as subscribers, would do the same. This way, the ‘good’ communities would thrive, and the ‘bad’ ones would wither away. What happens at the minute, is that there’s 8 communities for open source, and there’ll always will be, because they aren’t in competition with one another.

    (this is mostly just a general point about cross-posting behaviour, it’s not meant as a dig at you personally).