irdc

As the title says, I'm looking for a Linux/macOS-compatible EPROM programmer. I'd like to be able to program parallel (E)EPROMs in the 27xxx range. The newer XGecu programmers seem to not be compatible with Linux/macOS, and the selection of TL866(II) clones is too overwhelming for me to be able to choose one.

Any suggestions?

I’ve recently switched from a self-built Lemmy without pict-rs to the standard docker image that has pict-rs included. However, I’m noticing that the amount of pictures pict-rs stores on my instance is quite high. Any ideas? Is Lemmy preemptively mirroring all images in all posts?

Sad that updating your Lemmy instance to 0.18.1 broke your post and comment scores? Here's a small SQL script to fix them:

 MERGE INTO "person_aggregates" AS "d"
 USING (SELECT "m"."id" AS "person_id"
             , coalesce("p"."post_count", 0) AS "post_count"
             , coalesce("p"."post_score", 0) AS "post_score"
             , coalesce("c"."comment_count", 0) AS "comment_count"
             , coalesce("c"."comment_score", 0) AS "comment_score"
          FROM "person" AS "m"
          LEFT JOIN (SELECT "p"."creator_id"
                          , count(distinct "p"."id") AS "post_count"
                          , sum("l"."score") AS "post_score"
                       FROM "post" AS "p"
                       LEFT JOIN "post_like" AS "l"
                         ON "l"."post_id" = "p"."id"
                      WHERE NOT "p"."removed"
                        AND NOT "p"."deleted"
                        AND "l"."person_id" <> "p"."creator_id"
                      GROUP BY "p"."creator_id") AS "p"
            ON "p"."creator_id" = "m"."id"
          LEFT JOIN (SELECT "c"."creator_id"
                          , count(distinct "c"."id") AS "comment_count"
                          , sum("l"."score") AS "comment_score"
                       FROM "comment" AS "c"
                       LEFT JOIN "comment_like" AS "l"
                         ON "l"."comment_id" = "c"."id"
                      WHERE NOT "c"."removed"
                        AND NOT "c"."deleted"
                        AND "l"."person_id" <> "c"."creator_id"
                      GROUP BY "c"."creator_id") AS "c"
            ON "c"."creator_id" = "m"."id"
         ORDER BY "m"."id") AS "s"
    ON "s"."person_id" = "d"."person_id"
  WHEN MATCHED AND ("d"."post_count" <> "s"."post_count" OR
                    "d"."post_score" <> "s"."post_score" OR
                    "d"."comment_count" <> "s"."comment_count" OR
                    "d"."comment_score" <> "s"."comment_score")
  THEN UPDATE
          SET "post_count" = "s"."post_count"
            , "post_score" = "s"."post_score"
            , "comment_count" = "s"."comment_count"
            , "comment_score" = "s"."comment_score";

As with all scripts that work directly on the PostgreSQL database: warranty void when connected, your kilometrage may vary, do not look into laser with remaining eye, etc.

Edit: don't count self-votes.

…now I pay more than €100 a year for my own Lemmy instance.

Joke’s on you, spez.

Hi all,

I’ve been observing and participating in this community for about a week now. I’m liking it so far, but one thing I’m really missing is a way to link to other Lemmy content in a way that’s instance-aware.

For example, if I were to want to link to !risa@startrek.website, I’d link to https://startrek.website/c/risa. But then I’d end up at a Lemmy instance where I don’t have an account; I’d really prefer to be redirected to https://derp.foo/c/risa@startrek.website.

So here’s my proposal: create a central Lemmy redirection service where people can set their instance (in a cookie). The idea would be that people can link to, say, https://example.com/c/risa@startrek.website, and be ensured us lemmings end up on an instance where we can actually post.

Linking to posts and comments should ideally be part of this as well but whould involve a little more work.