e0qdk

This is a composite I stitched together from 12 screenshots taken from episode 5 of Penguindrum. I pretty much completely rewrote the tool I used for my last composite to make this. My old program could only handle solving two images; the new version solves a graph of correspondences one pair at a time to attach as many images as it can to a pinned starting image. I spent all weekend writing this specific editor, and much of my free time over the last couple weeks has gone into my broader art tool project.

I haven't done much in the way of artistically changing the piece. Other than the final cropping (which I did in the GIMP), it's as true to the imagery from episode 5 as I could get it. Notably though, the lower portion of the image and the upper portion of the image (with the reapers) are not from one continuous shot in the episode; part of my motivation for stitching this was that I wanted to see how it all looked when put together. I was surprised to find that the top portion with the reapers was actually scaled differently than the lower portion. I've cropped it for the main post, but if you'd like to see what it looks like without the final crop, you can see that image here.

The "lovers" are clearly a parody of The Kiss by Klimt -- https://en.wikipedia.org/wiki/The_Kiss_(Klimt) -- but I have no idea what the heck is going on with the cherubs in the middle...

I wish communities could be grouped in some way.

You can do that on kbin now. We just got "Collections" that allow you to gather posts from multiple communities/magazines sort of like a multi-reddit. You can either publicly list them for others to explore or just keep them to yourself if you want. We've also had cross-post grouping for a while which helps reduce the annoyance of "posts four times in a row (or more)" a little bit by collapsing the threads into one block with multiple links and vote counters. It's really useful though if you want to come back to the discussion later and find the other thread(s) -- e.g. check out last week's regular anime discussion threads which got 17 comments on ani.social and 5 comments on lemmy.ml. Jumping back and forth is easy. Hopefully lemmy gets something like that too eventually!

Haven't used that particular library, but have written libraries that do similar sorts of things and have played with a few other similar libraries in C++ and Haskell. I've taken a quick glance at the documentation here, but since I don't know this library specifically apologizes in advance if I make a mistake.

For OneOrMore(Word(alphanums)) + OneOrMore(Char(printables)) it looks it matches as many alphanum Words as it can (whitespace sequences being an acceptable separator between tokens by default) and when it hits ( it cannot continue with that so tries to match the next expression in the sequence. (i.e. OneOrMore(Char(printables)))

The documentation says:

Char - a convenience form of Word that will match just a single character from a string of matching characters

Presumably, that means it will not group the characters together, which is why you get individual character matches after that point for all the remaining non-whitespace characters. (Your result also seems to imply there was a semicolon at the end of your input?)

For OneOrMore(Word(alphanums)) + OneOrMore(Char(string.punctuation)) it looks like it cannot match further than ( since 1 is not a punctuation character; so, you got the tokens for the parts of the string that matched. (If you chained the parser expression with something like + Word(alphanum) I'd expect you'd get another token [i.e. "1"] added onto the end of your result.) You may eventually want StringEnd/LineEnd or something like that -- I'd expect they'd fail the parser expression if there's unconsumed input (for error detection), but again, haven't used this specific library, so it may work different than I expect.

There appears to be a Combine class you can use to join string results together; that might be useful for future reference.

i was trying to parse a string with pyparsing so all the words were separated from the punctuation signs

Have not tested it (since I don't have a copy of the library installed anywhere and can't set up an environment for it easily right now) but perhaps something like OneOrMore(Word(alphanums)|Char(string.punctuation)) would be more like what you are looking for?

I haven't used OpenBSD specifically, but I have used a FreeBSD derivative on a NAS. I'd recommended reading the documentation for common commands; if you're coming from Linux the flags and behaviors may be different from what you're used to.

The attached picture says 133 qubits, so whatever that chip is (edit: Heron) it's not this thing.

IBM's post (that the article links) says:

Breaking the 1,000-qubit barrier with Condor

We have introduced IBM Condor, a 1,121 superconducting qubit quantum processor based on our cross-resonance gate technology. Condor pushes the limits of scale and yield in chip design with a 50% increase in qubit density, advances in qubit fabrication and laminate size, and includes over a mile of high-density cryogenic flex IO wiring within a single dilution refigerator.

So, it sounds like this is actually another fridge sized system.

It looks like this is the pre-print of the paper ("The Impact of Imperfect Timekeeping on Quantum Control") in the journal the article links: https://arxiv.org/abs/2301.10767

Possibly also relevant from some of the same researchers: Fundamental accuracy-resolution trade-off for timekeeping devices

Interesting. The code format doesn't work on Kbin.

Indent the lines of the code block with four spaces on each line. The backtick version is for short inline snippets. It's a Markdown thing that's not well communicated yet in the editor.

It's from Paradise Killer -- which is like a vaporwave themed Danganronpa (but with more platforming and less infuriating bullet minigames).

This is one of the backgrounds you can configure your in-game laptop to use.

We don't need to depend on federated downvotes to judge what does or does not belong on kbin. In fact, I think it's probably better if we don't. People are downvoting the bots here. I have yet to see an account with negative rep. on kbin that wasn't a spammer.

Regardless, rate-limiting incoming posts will limit the damage and annoyance to us.

I wonder if there needs to be some kind of "governance board," like the NATO or EU of the fediverse, where major instance admins meet and set agreed upon standards of instance behavior.

I'm not sure that would help with this particular issue -- and there's already a fair amount of bad relations between instances so I don't think a wider fediverse board is likely to succeed even if it could help somehow... I guess instance admins that do agree on general moderation principles could help co-admin each other's instances to cover better for when they're offline (maybe some of them already do?), but we shouldn't have to depend on remote admins being responsive to deal with an issue affecting our instance.

Some ideas for anti-spam measures that might help:

• block users who post flood -- e.g. if an account makes 10 posts a minute, it's a spammer
• block accounts that end up massively in the negative shortly after they start posting -- e.g. an account at -50 within 15 minutes of making its first post is probably a spammer (exact thresholds may need some tuning). Note that this is different from blocking new accounts that go into the negative since people can register accounts in advance of an attack and wait until later to cause disruption.
• block users who post repetitive comments/links excessively -- e.g. if the same link is in 10 comments/posts from the last hour or they've submitted the exact same comment a dozen times, the account is probably a spammer (again, thresholds may need tuning); that won't catch all the bots (one of them added a bunch of random words) but will catch some of them. More clever filtering could catch the other bots.
• block new posters who are reported many times by established accounts in good standing -- at least until an admin can check what is going on

Source: Penguindrum

I didn't. I wrote ＆ because it looks like the text actually says ＆ as far as I can tell -- not と.