aka freamon@lemmy.world, freamon@feddit.nl, and any username from lemmon.website

This account is currently parked, and I’m using https://piefed.social/u/andrew_s

  • 8 Posts
  • 56 Comments
Joined 1 year ago
cake
Cake day: July 17th, 2023

help-circle
  • Lemmy doesn’t seem to get much recognition in the wider Fediverse - it tends to get bundled as part of ‘other apps’. Mastodon is much bigger, so better integration with Lemmy probably gets deprioritised below their own issues and feature requests (e.g. I was reading today that Markdown support is often requested, but the base version still doesn’t have it)



  • It’s partly an issue of keys. Every fediverse actor has a private key and a public key. When my instance sends this to fediverse@lemmy.world, it’s signed by my private key, and lemmy.world uses my public key to verify it. When fediverse@lemmy.world sends this comment out, it uses it’s own private key to sign it. It can’t just re-transmit my comment, because it doesn’t have my private key. All it can do is Announce that I’ve made the comment (and sign the Announce).

    Mastodon treats Announces as Boosts, so every post/comment is interpreted as a thing that fediverse@lemmy.world has boosted, so you get all these un-connected posts appearing. I think it’s mostly up to Mastodon to remedy.

    It works better if a Mastodon actor posts into a Lemmy community, then you get the mix like you imagine. e.g.: https://mastodon.world/@Flash/112095241193510662 (this particular post was crowbarred into Lemmy via !tails@lemmon.website, but it would be the same if the author had done it.)


  • freamon@endlesstalk.orgtoLemmy@lemmy.mlHow to download account data?
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    8 months ago

    No settings page (as far as I’m aware), but you can use the API to get everything (posts, comments, etc):

    step 1: get login token -

    curl --request POST \
         --url https://lemmy.ml/api/v3/user/login \
         --header 'accept: application/json' \
         --header 'content-type: application/json' \
         --data '
    {
      "username_or_email": "2br02b",
      "password": "YOUR-PASSWORD"
    }
    '
    

    step 2: use login token (big long string starting with ‘ey’) to get data -

    curl --request GET \
         --url 'https://lemmy.ml/api/v3/user?username=2br02b&page=1' \
         --header 'accept: application/json' \
         --header 'authorization: Bearer YOUR-JWT'
    

    Increment page number until you have everything. source: https://lemmy.readme.io/reference/get_user













  • freamon@endlesstalk.orgtoFediverse@lemmy.worldThe perfect Lemmy app?
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    8 months ago

    I think it’s because spoiler tags in lemmy have been custom-made for some reason, whereas all the other stuff is standard markdown. Voyager is a web app, so it can maybe only render whatever the engine it relies on can render.

    Edit: Turns out I’m 2 for 2 on making incorrect statements in this comment.


  • I’ve compiled lemmy a few times - it’s fairly straightforward. I’ve tried to compile kbin before, but gave up bored and pissed off with the instructions - they seem endless, and like a big list of ‘edit this file’ (with no indication for whether you’re adding or updating info), ‘now edit this file’, ‘now go back and edit the first file again’. I know mbin isn’t kbin, but the instructions are the same.

    I was trying because someone from there subscribed to a community I made just using ActivityPub, but nothing I’ve sent there has actually appeared. If you send the wrong stuff to lemmy, it errors. It’s not always the most useful message, but it’s at least a ‘400 Bad Request’, not the ‘200 OK {}’ you get back from kbin. What does it want? Does it not like ‘Create/Page’? Is there a problem with the content? I don’t know, because I can’t [be bothered to] compile it, and the tech specs for these 'bins lead to a 404.



  • I changed the link to nbcnews rather than businessinsider - I tested it but the paywall on there is sneaky.

    The full memo is:


    Dear Vice Team,

    As we navigate the ever-evolving business landscape, we need to adapt and best align our strategies to be more competitive in the long term. After careful consideration and discussion with the board, we have decided to make some fundamental changes to our strategic vision at Vice.

    We create and produce outstanding original content true to the Vice brand. However, it is no longer cost-effective for us to distribute our digital content the way we have done previously.

    Moving forward, we will look to partner with established media companies to distribute our digital content, including news, on their global platforms, as we fully transition to a studio model. As part of this shift, we will no longer publish content on vice.com, instead putting more emphasis on our social channels as we accelerate our discussions with partners to take our content to where it will be viewed most broadly.

    Separately, Refinery 29 will continue to operate as a standalone diversified digital publishing business, creating engaging, social first content. As you know, we are in advanced discussions to sell this business, and we are continuing with that process. We expect to announce more on that in the coming weeks.

    With this strategic shift comes the need to realign our resources and streamline our overall operations at Vice. Regrettably, this means that we will be reducing our workforce, eliminating several hundred positions. This decision was not made lightly, and I understand the significant impact it will have on those affected. Employees who will be affected will notified about next steps early next week, consistent with local laws and practices.

    I know that saying goodbye to our valued colleagues is difficult and feels overwhelming, but this is the best path forward for Vice as we position the company for long-term creative and financial success. Our financial partners are supportive and have agreed to invest in this operating model going forward. We will emerge stronger and more resilient as we embark on this new phase of our journey.

    Thank you for your continued dedication to Vice and support during this time of transition.

    Together, I am confident that we will overcome any challenges and achieve our shared goals.

    Bruce