max-m

How was your day?

ListenBrainz is still experiencing massive server load from an increase in listen submissions related to the BTS fan exodus from last.fm and they are now being hit by another influx of AI scrapers.

LB radio and the popularity endpoints have been temporarily disabled, to reduce server load.

Dorfromantik is a very nice game that can be played as a solo or co-op game. It was released in multiple languages: https://boardgamegeek.com/boardgame/370591/dorfromantik-the-...

The basic rules aren't hard to learn and official digital versions of the rulebook and addendums with some clarifications are available (at least) in English and German.

If none of the official releases are in your language of choice, translating them shouldn't take too long. During the campaign, should you decide to play it, you unlock some cards with text on them which explains the unlock conditions and the elements they add to the game. An example of those cards can be seen in the addendum on pages 2 and 5. There aren't too many of them, so it's quite feasible to translate them.

For the English version, have a look here:

https://pegasusna.com/Dorfromantik-The-Boardgame/PNA51240.US...

Rule book: https://pegasusna.com/NetiMedia/download?mediaId=018e5c292cd...

Addendums: https://pegasusna.com/NetiMedia/download?mediaId=018e5c29466...

They have been “upgrading” old videos to shorts for more than a year. As far as I know it once started with videos with a runtime of at most 30 seconds. At some point that was increased to 3 minutes. I think they do this to square and portrait videos, maybe the check is as simple as “height >= width and duration <= 3 minutes”?

https://www.facebook.com/groups/Nachtfotografie/posts/264063... Here is the original photo description in German. See also my other comment in this thread. But the tl;dr is that this was a stack of 153 four-second exposures with some gaps in the timelime when the camera took its time to save between exposures.

My time to shine! I've spent yesterday morning to track the photo down and answer this question. The APOD description is lacking. Yes, this was an exaggerated stack of 153 four-second exposures (the rejection map of the satellite trails was added on top of the image), and the gaps happened when the camera took its time to save between two exposures.

Here is a link to the original photo and it's description (German) by Uli Fehr: https://www.facebook.com/groups/Nachtfotografie/posts/264063...

I think the question was: Who gets the payout? The bet is: There will be a ceasefire. There was a ceasefire, but it was allegedly broken almost immediately after. So does that count as ceasefire or not? There are arguments for both sides, so you could also say it's a tie and neither party gets the cut and the bets will be refunded.

The names of the benchmark runners. https://doesjitgobrrr.com/about

To the community it was unhackable, until very recently. It's security measures held up so long that it appeared to be unshakable. There were no obvious flaws. In hindsight it was hackable, but keep in mind how long it took. This console has long been obsoleted.

A couple of years ago the bot situation in casual Team Fortress 2 was so bad that it wasn't uncommon to land in a game where the majority of at least one of the teams was a group of cooperating bots. In those matches you have the possibility to start a kick-vote on your team mates, and those bots would immediately vote “no” if you tried to vote on any of them and because they were the majority of the team these votes always failed. And if these batch were in your enemy team all you could do was to ask the remaining, hopefully real, players on the enemy team to try to kick them. It was especially annoying when you tried to play certain game modes these bots weren't programmed to handle, they had no idea of the objective and the match would stall indefinitely, forcing you to queue for a different match. And if I remember correctly these bots were pretty much headshotting everything they got in sight. Something the server can easily detect. But VAC for example acts intentionally slow, so cheaters don't get immediate feedback.

Out of curiosity I did a quick internet search and a couple of months ago a new wave of bots has emerged. Those bots also join as majority group but never fully join the game, they simply take up slots in a team, preventing others from joining. Makes you wonder why the server isn't timing them out.

In case the embedded SoundCloud player refuses to show up, here's a direct link: https://soundcloud.com/the-british-library/first-recording-o...

Here's my more-or-less decade old “image to braille converter”: https://max-m.github.io/misc/braille/index.html

The source code is unminified and unobfuscated.

Another somewhat similar toy is https://max-m.github.io/InstaECB/index.html :)

On my old phone (Nokia 8) the random header image takes a while to process and afterwards the content pops up. On my Pixel 8 it's basically instant. Both times tested in Firefox.

At this point I can't even tell reality from satire anymore.

"dang" is liked by HN! :D

Something similar happened to me once. I still don't know what exactly happened, but in Dropbox some files were deleted, I still had my local copy, but then Dropbox synced the file deletions and I didn't notice. Only when it was too late did I notice that files were gone and their support was unable to help. I think I managed to recover some files with one of the NTFS "undelete" tools, but that was probably the day I started to treat "the cloud" differently. Nowadays I don't even know what's still in my Dropbox ...

The Blog was hugged to death, but https://archive.is/1FrpD got through.

I really enjoy board game adaptation of Dorfromantik. Its a rather relaxing co-op game. There's also a "Duel" version of the game were two players (or teams) compete by playing with the same sequence of tiles. :)

Pages like TEZ or the "Awesome XYZ" list repositories that have become rather popular on Github are perfectly fine. Those are great hubs to get a grasp of what's available. Sometimes they are a little out of date, but if you're interested enough you'll find the up-to-date information by yourself :)

But these parasitic pages that pretend to be official (project) pages should be purged. :/ For now they might link to original releases, but they could very well switch to malicious downloads from one second to the next after having gained enough "trust" and traffic.

And that *unofficial* bsnes site reflects poorly on the emulation community because they actively promote downloads of game ROMs hosted (practically) on their website because they control the Github repository the games are uploaded to.

The bsnes emulator has a similar problem. The official "website" is the Github repository at https://github.com/bsnes-emu/bsnes/ but some unknown entity has snagged bsnes.org and is now also publicly linking to SNES ROMs they host on Github (Github doesn't care, you can report those repositories as much as you want. If you're not a rights holder they won't do anything).

From that article, that's the original Hamming windows with a_0 = 0.54 and a_1 = 0.46.

> Setting a_0 to approximately 0.54, or more precisely 25/46, produces the Hamming window, proposed by Richard W. Hamming. That choice places a zero-crossing at frequency 5π/(N − 1), which cancels the first sidelobe of the Hann window, giving it a height of about one-fifth that of the Hann window. The Hamming window is often called the Hamming blip when used for pulse shaping.

You are probably thinking of SameBoy :)

I'm one of those freaks who use Unity to this day. :) In the beginning Unity was rough, but the last version was actually quite comfortable to use.

At the moment I'm daily driving Ubuntu 20.04 with root on ZFS, but I'm debating really hard whether I should distro hop or not. I dislike Canonical's insistence on "snap", their advertisements in "apt" output, ... But on the other hand Ubuntu gave me mostly a "it just works" experience on my desktop for multiple years. For a while I ran Arch on another system and had quite the opposite experience. Upstream broke dependencies at least twice for example, so a lengthy session of "how the heck do I fix this" ensued.