Default avatar
YsYe7Rg5O$JeULRiNnJehvlYjlGrxX5xY_tQgpe5NsP9
npub18eyn...cvu7
After such a downer regarding Bisq 1 on NixOS, I want to mention something positive. I started a new Nix flake to bring amazing support for Squeak, Cuis, and Pharo Smalltalk to NixOS. By amazing, I mean a level of seemlessness that is unmatched by any other operating system. The idea is to provide tooling and bundles to make it mind-blowingly easy to install and use different Smalltalk implementations and images, all at the same time. For example, if you have a Smalltalk image, you can open it right from your file browser: image Right now I only have a "bundle" for Cuis 7, but soon it will be possible to install various versions of Cuis, Squeak, and Pharo Smalltalk, all at the same time without conflicts. You can also launch a "bundle" using an app launcher or menu, which will then produce this Zenity prompt: image Creating a new Smalltalk image is damn fast because the image is already in the Nix store. Just choose a directory, or create a new one, and before you can blink your eyes the Smalltalk image will appear before you, executing with an appropriate Smalltalk virtual machine, ready to go. Gone are the days of fumbling around, downloaded VMs and images, extracting them, .... boring. Well, that's the idea. The project is still in it's infancy, but you can play with it here: If you have the Nix package manager, and Nix flakes enabled, you can just do this: nix run github:emmanuelrosa/smalltalk-nix#cuis-7_0 Before you know it, you'll have Cuis Smalltalk 7.0 right in front of you. #nixos #nix #smalltalk
I recently mentioned that Bisq 1 is now marked as broken on Nixpkgs because OpenJDK 11 was removed. I came up with a solution to get us by until Bisq 2 is feature-complete. The basic idea is this: 1. Create a NixOS-friendly AppImage of Bisq 1. 2. Keep a copy of the AppImage in a safe place. 3. Either use the AppImage, or use a bisq-desktop package with a pinned Nixpkgs, so that you can still access OpenJDK 11. All of the above can be done with the Nix flake Note: It's very likely that NixOS users using Bisq will soon discover that it can't be built anymore. Since NixOS doesn't track its users (how dare they!), this build failure is actually the best method we have to communiate that action needs to be taken. I've been emailed in the past by people using Bisq on NixOS, so I'm sure I'll here from them soon :) I plan to remove the Bisq 1 package from Nixpkgs after the November stable release. I did not expect to have to do this so soon, but here we are. #nixos #nix #bisq
If you run Bisq (@Bisq) version 1 on NixOS (or use the Nix package), I have some bad news. Bisq 1 relies on an outdated version of OpenJFX, and this version was just removed from Nixpkgs. This makes the Bisq Nix package (in Nixpkgs) broken; It won't build. See I'm working on a stop-gap solution, but you may want to refrain from updating Nixpkgs master or unstable until you hear back from me. #bisq #nixos
A new version of Bisq2 came out with some nice features, namely Lightning support and QR code scanning. But regarding the later... The QR code scanning is a separate bundled Java app with a bunch of binary code. To be precise, there are 76 shared libraries which would have to be patchelf-ed to get QR code scanning to work on NixOS. Either that, or I'll have to run the webcam app in a container. Either way, that's still 76 libraries for which I'd have to identify dependencies, find their matching packages in Nixpkgs, and hope for the best. Not to mention the amount of churn I'd have to put my new-ish SSD through to build, build, and rebuild, until it works. I had plenty of difficulty getting QR code scanning to work on Sparrow, and that was child's play compared to what I'm looking at with Bisq2. About 4 years ago when I packaged Bisq1 I destroyed my SSD in the process, so I'm mindful about these things. So, you know what I'm thinking... I have no plans to fix Bisq2 QR code scanning. Sorry, but either it will remain broken or another brave soul can take a stab at it. image
Every time I think I'm done coding my Sierra Chart chart-scrolling study, I come up with a way to improve it. But I think it's done now: image You basically enter an "alert formula" which produces an on/off state; non-zero = ON, 0 = OFF. The study then provides chart menu options to scroll the chart to the next/previous occurence of the ON state. The example shown in the screenshot uses a formula which produces an ON state when the two moving averages cross; The formula just uses Sierra Chart's CROSSOVER() function. But the formula could be something more elaborate. For example... 3 consecutive higher-highs above the 20-period EMA. Whatever it is doesn't matter as long as it produces non-zero and zero values. The study can fast-forward right through the chart, one mouse-click at a time, showing every single instance wherein the formula produces an ON/TRUE condition :)
Here's a goofy thought: Given a "God candle" is a big-ass bullish candle in the Bitcoin spot market, doesn't that mean that a big-ass bearish candle should be named a "Satan candle"? I know, it's stupid. But I needed the laugh to get our damn parasitic USG out of my mind.