This guide is to improve the KDE Plasma experience on X11. It particularly applies to those using the modesetting driver (mainly Intel graphics cards)
This is a crucial step. XLibre and xorg-git contain the "TearFree" feature for modesetting, which is not available in the standard releases. If you use a driver other than modesetting, check that the TearFree option exists for your driver.
Installation depends on the distribution you use. On Arch Linux and derivatives:
Xorg-git:
| change-id = "ignore" | |
| [llvm] | |
| targets = "X86;RISCV" | |
| optimize = true | |
| download-ci-llvm = false | |
| link-shared = false | |
| [build] | |
| target = ["riscv64gc-unknown-linux-musl"] |
In the pursue to make an impactful app that uses Gemma 3n model, recently published by Google, I have been looking for available implementations for using Gemma 3n on local consumer devices, such as your regular iPhone and Android phones, maybe macOS and even Windows-based laptops.
Gemma 3n is a multi-modal model that can process text, images, and audio. See overview https://ai.google.dev/gemma/docs/gemma-3n
This is a very beginning of hackathon, so the open-source implementations available today are limited to those that google pushed to the public just days before the release. The vest survey so far was published on Hugging Face, see https://huggingface.co/blog/gemma3n
It says "Gemma 3n fully available in the open-source ecosystem", but definition of "fully" is blurry as the multi-modal context is very complicated topic and the designs of some ecosystem toolings are not even ready to accept such "multi" context to begin with. Le
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>Starship Shards</title> | |
| <!-- Original code https://x.com/XorDev/status/1880344887033569682 --> | |
| <!-- https://x.com/xlab_gg Asked Claude 3.5 to convert it to GLSL ES --> | |
| <!-- Attribute original code to @XorDev if you reuse this code --> | |
| <!-- Jan 17, 2025 --> |
Examples of bootstraping Cosmos networks:
$ CHAIN_ID=888 DENOM=inj ./test/cosmos/multinode.sh injectived
$ CHAIN_ID=somm DENOM=samoleans STAKE_DENOM=stake SCALE_FACTOR=000000 ./test/cosmos/multinode.sh sommelier
Full list of the supported ENV variables:
CHAIN_ID- specifies Cosmos Chain ID, likecosmos-1
| executing transaction | |
| transaction: { | |
| "Salt": 1587842612, | |
| "ExpirationTimeSeconds": 1588447418, | |
| "GasPrice": 6000000000, | |
| "SignerAddress": "0x6ecbe1db9ef729cbe972c83fb886247691fb6beb", | |
| "Data": null | |
| } | |
| transaction data: "0x9694a402000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000003e00000000000000000000000000000000000000000000000000000000000000420000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000200000000000000000000000005409ed021d9299bf6814279a6a1411a7e866a63100000000000000000000000000000000000000000000000000000000000000000000000000000000000000005409ed021d9299bf6814279a6a1411a7e866a6310000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001158e460913d000000000000000000000000000000000000000000000000000001bc16d674ec8000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| pragma solidity ^0.5.1; | |
| interface TokenRecipient { | |
| function receiveApproval(address _from, uint256 _value, address _token, bytes calldata _extraData) external; | |
| } | |
| contract ERC20Interface { | |
| function totalSupply() public view returns (uint256); |
| const CryptoJS = require("crypto-js"); | |
| const EC = require('elliptic').ec; | |
| const secp256k1 = new EC('secp256k1'); | |
| function publicKeyToAddress(pubKey) { | |
| let address = CryptoJS.RIPEMD160(pubKey).toString(); | |
| return address; | |
| } | |
| function privateKeyToPublicKey(privKey) { |
Atlant announces 1.0.0-rc2 node release
This is a bugfix release that resolves node performance issues and adds new supported platforms.
The major bug that is closed within this release was about internal state DB growth. For our key-value store we use a 3rd-party component called BadgerDB (https://github.com/dgraph-io/badger/) and at the moment of our initial release it had a flaw, that wasn't properly documented. Since our release they improved that part in their codebase and added guidelines in the documentation, we followed these guidelines and now the issue is closed.
The issue with DB growth had the most effect on our testnet nodes, some of them became unresponsive and failed to sync with new clients. We strongly recommend anyone who tested the node to update the executable and restart the sync.