I waddled onto the beach and stole found a computer to use.

🍁⚕️ 💽

Note: I’m moderating a handful of communities in more of a caretaker role. If you want to take one on, send me a message and I’ll share more info :)

  • 377 Posts
  • 1.82K Comments
Joined 3 years ago
cake
Cake day: June 5th, 2023

help-circle


  • Can you edit the post to say that you suspect that this is what they are doing instead of stating it as a fact?

    I am also suspicious, but looking through the accounts the activity could still be a human using LemmySchedule to schedule the posts ahead of time. There aren’t that many posts each day, and I couldn’t easily map the posts to any existing subreddit or other source. Normally these bot accounts have a lot more posts, and that’s why they get blocked or banned.

    It could just be a user that is using potentially harmful strategies to get communities related to their interests off the ground





  • What would be the use case for cyborg insects, other than war and espionage? Are they smart enough for search and rescue?

    The fundamental operational range of cyborg insects, which are hybrid robots that combine a living insect with an electronic controller, is inherently restricted to the host’s natural environment. To extend their operational range, we developed a wearable diving suit for terrestrial insects. The suit integrates a miniaturised oxygen generation module with a flexible waterproof shell, enabling continuous oxygen supply and isolation from surrounding water. By fitting a cockroach, which is a terrestrial species, into this diving suit, we allowed it to survive and operate in oxygen-deprived environments such as underwater, transforming it into an amphibious cyborg robot capable of operation across land and water. The suit sustained respiration and locomotion for up to 3 h underwater, establishing amphibious cyborg insects that combine biological adaptability with engineered protection for prolonged exploration in extreme, confined environments.



  • Seems like the solution is: don’t do exams this way

    This year, the economist decided that both the midterm and the final exams for his course would be of the take-home, closed-book type (there is a certain tradition of this at Ivy League schools). “It’s a very nice kind of exam, because as you’re giving students practically unlimited time to complete it, it lets you make it harder than normal, to see how far they can go.” In this case, Serrano changed some of the model assumptions they had seen in class, and asked students to demonstrate whether certain statements were true or false under the new assumptions.


  • I use a browser extension that sends me to a reddit frontend on the off chance I come across a post while searching. It works pretty well

    Libredirect + the fastest instance

    From the admin side, I do understand what they are saying but I think there’s a better solution to it. We run the old frontend on our instance, and it gets hammered with bots and scrapers. So if we assume that old.reddit works the same way, then it would be attractive to scrapers. But instead of locking it down, I think they could set up something like Anubis or put it behind some other anti-bot measure.



  • From the admin side, we see the following

    • lots of accounts trying to register with the same LLM generated text, or nonsensical spam in the registration application. Those get blocked
    • some accounts that immediately make it obvious that they are a spam bot by posting unrelated advertise-y content as their first post. Those get banned quickly, and usually the home instance prunes the account within a day

    The recent “DM me” spammers and the accounts that post on !selfhosted@lemmy.world are a good example of the second category.

    It’s pretty rare for a bot to be active for much longer than that. Usually some eagle eyed user will spot it and report it up the chain.


  • Welcome!

    We have some guides / infographics for new users, which you might find helpful. These two pages in particular:

    https://fedecan.ca/en/guide/get-started

    https://fedecan.ca/en/guide/threadiverse/detailed-overview

    An instance is the site where you make an account. If we extend the analogy to email, then gmail.com is one instance while hotmail.com is another instance. If you make an account on Gmail, you can’t use that login on Hotmail but you can still see content from people on Hotmail.

    Lemmy, Piefed, Mbin, Mastodon, Pixelfed, etc. are all software. It’s hard to extend this analogy out, but imagine if Google released the code for Gmail freely so that anyone could easily set up an email website that had the same appearance and functionality as Gmail. That is what is happening here.

    So in the same way, lemmy.ca, lemmy.world, sh.itjust.works and many other Fediverse instances are running the “Lemmy” software and that’s why they look and feel very similar. Where they differ comes down to the people running a particular instance, since they will have different rules for what you can do. You can find that information in the sidebar.

    Now all of the Fediverse platforms use a common and agreed upon language to talk to each other. Because Lemmy, Piefed, and Mbin software all use this language and follow a similar format, you can easily share content between all of them. That is what the second guide page talks about. They all have communities, posts, and comments, and work in a similar way.

    Usually people make one account on a forum/threaded instance (Lemmy, Piefed, Mbin), and one account on a microblogging instance (Mastodon). This is because the format of microblogging (ex. Twitter) is pretty different from that of forums (ex. Reddit), although it is technically possible to cross post in between them.





  • Could this be solved by having two renderers, and only using the proprietary Adobe one needed?

    So what do you do when the pedantic gold standard of epubcheck says your book is fine, when it works without issue on Amazon Kindle, Apple Books, Thorium and everywhere else and yet Kobo says it’s “corrupted”?

    I dug into this matter and found out that Kobo uses RMSDK, “Reader Mobile Software Development Kit”, Adobe’s proprietary ebook rendering engine.

    Once the stylesheet was identified as the source of my woes, I could finally drill down to find which specific line was causing the issue. After creating a dozen more variations with different subsets of my stylesheet I eventually identified the culprit. It was this line:

    .copyright img {
        max-width: min(150px, 30vw);
    }
    

    Once I changed it to the more old fashioned max-width: 150px; ADE opened it just fine.

    But what is the problem here? The above code is perfectly valid CSS level 4, it’s just not supported by RMSDK, because its CSS parser is frozen in approximately 2013 — no flexbox, no grid, no math functions, no custom properties. Just good old float, bad font handling, and silent crashes when it sees anything it doesn’t recognize.

    It’s the year 2026. Thanks to the horrendous RMSDK which Kobo decided to use as their backbone for all book rendering (probably for DRM reasons), a single line of perfectly valid CSS turns a perfectly valid EPUB file into a “corrupted file” on Kobo and just drops the whole book. No clear error message, no fallback. Just a massive fail.