After I wake up from sleep, the screen stays black. I can get the Steam Menu working, and a "restart steam" fixes it. But all of the other options (Library, Settings, Home, Downloads etc) get me a black screen.

I switched to the Steam Beta channel, but no luck so far.

I sized up from 8->9 and now regretting it.

Just published: https://captnemo.in/superhexagon/, source

Now I feel like porting hateris

I was among the folks asking for Gemini. Thanks a ton! Finally gives me the push to deploy my website to Gemini as well. Downloaded.

The Dragon Prince creator was a writer on Avatar. I have a feeling it is the same animation studio.

You can look at OpenHexagon for inspiration as well.

A little harder maybe. 🤔

I can put down some recordings, but it sounds amazing.

I’d rather this get ported by actual game dev professionals.

I plan to publish the code without the assets as an educational project for me. I really hope Terry commissions an official port - this deserves to be on the Playdate Catalog.

Still working on a blog post, but this was a reverse-engineered port of Super Hexagon to the Playdate. It preserves all of the original game logic, hence you see the same credit screen, and the exact same levels and patterns.

Ever since I've got mine Playdate, I've wanted to play this - SuperHexagon feels like the perfect game for it. The harder levels are actually very hard with a crank control, but it is quite fun.

Looking at the API response schema, the list of products, and the data itself, fairy sure it is a wrapper on top of endoflife.date

Disclaimer: I started the endoflife.date project.

I'm a security professional, and I've been looking into the responses of all the package managers around similar supply chain attacks. This blog is a good source if you're interested.

tl;dr: Every AUR helper should give us hooks with package metadata, git-dir, and the built package at PreClone, PreBuild, and PreInstall stages.

The two most interesting ideas in this space, that I'd like to see AUR adapt to are:

1. Dependency Cooldowns

There are two ways to implement a cooldown - either your local package manager refuses to install a newer version of the package till X-days have passed from the release. This is somewhat feasible in AUR since the AUR API returns a LastModified timestamp, which I think is the server timestamp of the last push. If this is the commit timestamp, it doesn't work.

The other way is how homebrew does it in their core repo - all NPM and PIP packages must wait 1 day before a bump PR can be filed and merged. This isn't really feasible in AUR since people do want the bleeding edge, and I think community maintainers should be free to pick their cadence.

I'm optimistic about the first approach, but it would need some niceties added to the AUR helper to support exceptions etc.

2. Filter Lists

Composer (the PHP package manager) supports setting a third-party filter-list, which is queried on every install action. It contains a list of packages you don't wanna install (known malware etc). You can pick whose list you wanna follow. Some folks are interested in doing LLM-assisted security scans on AUR PKGBUILDs, this would be a nice way to publish that information.

3. Conflicts (FUN!)

Since makepkg supports packages, we can steal another idea from the PHP folks and instead of the AUR-scanning scripts that are being built, create a meta-package that conflicts with anything you think is malware. https://github.com/Roave/SecurityAdvisories is the simple implementation. This has a problem that your meta package needs to always be the latest version (so you must always update it), and it can itself turn malicious (since packages can execute arbitary code).

This was a cool idea when we didn't have filter-lists, and we can adapt to this as a stop-gap, but it isn't a long-term solution.

4. Hooks

Ultimately, the above 3 ideas boil down to the same thing: When you're deciding to build a specific commit from AUR, check it in some form (timestamp, or against a list). And Arch gives us some niceties in the form of hooks to enable such behaviour. Unfortunately, pacman hooks run at install time, and makepkg does not support any hooks. So it is down to the AUR helpers to implement hooks. Or maybe I should write a makepkg wrapper that helpers can delegate to. But if you have a hook in your helper that runs at PreClone, PostClone, PreBuild, PostBuild, you can write a script that takes any of the above ideas and implement them however you like. You could even implement future-looking ideas, such as doing a malware scan on the final package.

I've been very busy this month at work, but if you're interested in the above ideas, do reply.

Edit: paru already supports a PreBuild hook. Who here promises to maintain a malware threat feed for AUR packages that I can use? yay added a new UpgradeSelect hook where you can do something similar.

Just to save a click:

DDoS Attacks on various Arch Linux sites

We're currently being attacked and trying to fix the problem until then degraded service is expected for both sites.

Affected Services:

• aur.archlinux.org

• bbs.archlinux.org

• wiki.archlinux.org

Posted 16 May. 10GMT (~3h before this comment).

The one at Torstrase is at 201-250 reviews removed. And the lines are very very long.

I upgraded this system from F41 -> F42 -> F43 in a quick span, and it happened on all of those. Setup is Asahi Fedora Remix, M2 Air 8GB, currently running KDE 6.6.3 at Kernel 6.18. I'm trying to recreate.

I'm fairly sure this will happen again on my setup with the upcoming F44 upgrade. I've backed up my config, and will update on the upstream bug report (saw your comment about having to drop this).

+1. Loans from large financial institutions in India with multiple witnesses and stamped agreements take years to decades to enforce. What hope would a digitally signed agreement have?

A lot of online companies do tripartite agreements (such as in P2P lending), you can build this today cheaply without touching any money movement but I doubt there is a large market for it. 

Happens on every Fedora major upgrade for me on Asahi. 

git packages do a git pull/fetch on an existing clone. So they already have most of the source, and thus git will do its fancy delta-calculation and only transmit the stuff you don't already have. The build and install processes are smart and cached in most cases, but this depends heavily on the package itself and will vary a lot - the checksum (or skipping it) doesn't have anything to with it.

When you connect your Gmail account to Fold only your relevant transaction emails are pulled to your device and processed locally, from there, data from transaction emails like amount, merchant, and time is sent to our servers for storage and enrichment. Our servers don’t get a whiff of your email address or any other emails in your inbox.

Other companies are trying and succeeding at educating their customers: https://fold.money/blog/what-we-have-been-up-to

You ought to be eligible for Microgrants. Maybe look at https://thejeshgn.com/projects/nagarathna-memorial-grant/