I’m a #SoftwareDeveloper from #Switzerland. My languages are #Java, #CSharp, #Javascript, German, English, and #SwissGerman. I’m in the process of #LearningJapanese.

I like to make custom #UserScripts and #UserStyles to personalize my experience on the web. In terms of #Gaming, currently I’m mainly interested in #VintageStory and #HonkaiStarRail. I’m a big fan of #Modding.
I also watch #Anime and read #Manga.

#fedi22 (for fediverse.info)

  • 0 Posts
  • 266 Comments
Joined 2 years ago
cake
Cake day: March 11th, 2024

help-circle
  • To me personally, “woke” means living in the real world.

    A lot of people nowadays reject reality and prefer to live in a world of falsehood. They desire a simpler world, so they refuse to acknowledge the complexities of the world.

    Woke people don’t do that. They engage with reality, not fiction. Which is what makes them a danger to those that do prefer to escape to a simpler fictional world. Hence them denying and opposing woke. It’s a defensive reaction to a perceived threat to their alternate worldview.
    Or at least that’s how I see it.


  • One reason I haven’t seen mentioned yet is practicability.

    Yes, people have the tools. But how do you get that tool to where you need it?

    In the US I believe you can just carry weapons for whatever reason you want. That’s not quite the case in Switzerland. If you’ve got a gun for military service, for example, you’re only allowed to carry it from and to military service or the shooting range. You can’t just go to a school with it. Same applies to other purposes. You can only carry a gun for the specific purpose you have your permit for. You can’t just take it to a school or mall.

    Plus, the people who have guns at home usually only have the guns, no ammo, iirc.





  • but would Codeberg’s policies allow doing such thing ?

    In its terms of use, Codeberg explicitly outlines under what license terms it provides code hosted on it:

    • the right to use the content for any purpose, including both commercial and non-commercial purposes
    • the right to make unlimited copies of the content and redistribute those copies to others, with or without charge
    • the right to examine the content and determine how it works and/or how it was made
    • the right to make their own modifications to the content, to use the content with those modifications privately
    • and the right to redistribute copies of the content which include their own modifications, with or without charge

    You are not allowed to upload code which you do not have permission to publish under these terms. Which means you can’t just arbitrarily relicense code you got from Github, and you also can’t upload Github projects with a more restrictive license, such as non-commercial ones.







  • Your outbox is factually empty. I assume this is because Lemmy doesn’t see a reason to populate it. You can’t follow Lemmy users, so there’s no reason for another platform to want to directly fetch your past posts.

    Other instances of course know your posts because you send them to them when you submit them. They don’t need to ask the outbox. And your own instance doesn’t need to ask an outbox either, it can just ask the database directly.

    But these tools probably aren’t instances, they just fetch your outbox directly. So since the outbox is empty, and you never send them anything, they have no posts of yours.


  • If any Lemmy devs look here, Mbin adds the image to the attachments array and uses a custom property (source) to add the url directly to the post instead of url (in addition to the entry in the attachments array which Mbin adds too). I don’t know how you’re getting the url, but I assume one of those two is the issue. Both can be fixed by the Mbin devs imo, but if the attachment array contents are the issue, I do recommend making Lemmy more robust there as the problem won’t end with Mbin in the future. Other projects might also add additional objects to that array.



  • Different cultures, probably. Different echo chambers. Different age brackets?

    Like, I have the same experience. Online I see people either being neutral or super negative about it, but IRL everyone seems positive about it. But I’m comparing english-speaking social media sites that are unpopular in my country to people in my daily life who barely speak any English. Clearly there’s a huge distance there already without opinions on AI in the picture. It’s also worth noting that in subreddits in my native language or about my country I have yet to see the same negativity, making it imo clear that in my case it’s a difference of where people are from.


  • Infinite Scrolling is an anti-pattern meant to get you addicted, that’s probably why the Lemmy devs didn’t include it. You might want to look into alternate frontends for Lemmy. I have no experience with them, but they might have the feature.

    I’m using Mbin, where Infinite Scrolling is an optional setting that is turned off by default but can be turned on even logged out via the sidebar. So if this is a feature you need, and no alternative Lemmy frontend provides it, consider switching to Mbin.


  • No, what I meant was, I tried to investigate why it doesn’t work, by doing the request myself. Webfinger is the endpoint used by instances to resolve a name@domain.tld address to an actual URL. And when I tried requesting that, I got a 403 Forbidden error from Cloudflare. Still getting the same result (both manually and on the instance, there’s still nothing there too).

    Looking into it further, it seems Cloudflare presented me with a Javascript challenge. Which won’t work without a browser. That’s why it didn’t work for my manual attempts, but federation would trip up there too unless the server was running Electron. Which makes no sense for a backend.

    I’m not sure if this is why it didn’t work for the instance I’m using of course. It working for you suggests not everyone gets the challenge. But it is a likely reason it doesn’t work for some of us. In the first place, this kind of anti automated access protection makes no sense on endpoints specifically meant to be accessed in an automated manner.