Let me give an example. I am currently working on the InnuneDo stack. Some of the projects in that stack such as (currently on hold) aiow3 will be HIVE geared projects that I develop on codeberg, on my

Just an idea: It might possibly sometimes be less overhead if you could allow people to claim ownership of accounts on repo hosting sites like codeberg.org, framagit.org, bitbucket.org, github.com, the

TLDR version: For much of what subsciption/metered frontier models are used for, a workflow using templates and self hosted frozen-version open weight models works better. Small low power devices like

Repeated spam comments not appreciated.

Thanks for the feedback, updated my script. Fixed the HFSCORE, added a hours behind metric and now weighing top 21 accounts stronger for their price feed. #!/usr/bin/env python3 import json import datetime

Great initiative. I had been thinking of something similar for the future as a proof of concept bot for the web3 stack I'm (slowly) working on, but ended up deciding on a port of existing bot code for

As someone who has been using both chatbots and code assistance on a daily basis, I am strongly convinced that chat bots are still much and much more stupid than the average human. But they are stupid

5: Reverse the idea that by default constants have no authority and make a modifier like inert that tells the compiler the constant has no authority. Vote with a 1% vote if you think this is the best option.

4: Change the language to allow for rvalue modifiers and mark the string itself as hazardous. Vote with a 1% vote if you think this is the best option.

3: Somewhat ambiguously, ad an (lvalue) modifier hazardous like the other two uses of hazardous already in the language. Vote with a 1% vote if you think this is the best option.

2: Add an (lvalue) modifier like sensitive to indicate the constant contains sensitive data. Vote with a 1% vote if you think this is the best option

1: Leave the language as it is, no changes, don't incentify bad coding Vote with a 1% vote if you think this is the best option

Thanks so much for this comment, It's the first comment

Thanks so much for this comment, It's the first comment I've gotten on any of my posts in this series and I was starting to wonder if anybody cared about my efforts to make this Domain Specific Language

What is more important for a Web 3.0 Python library? Being widely usable for as many chains as possible, or being ethical in what chains you do and don't support (Blurt, Steem, Tron, etc) ???

In my experience a real "ofshore team" is a nightmare, and hiring an intermediate company messes up the loyalty of the team members. You are a customer of their boss, not their boss, and they

Hmm, Signature Flexibility looks like it might be very relevant for me. Is this just to allow redundant ECDSA signatures, or could this allow adding signatures of other types? I'm looking into piggybacking

Don't!

I think the mass tagging you just did illustrate perfectly why we do need downvotes.

This is the first time I've noticed this project. I'll soon be looking at your repo to see if there is anything to learn from it. I'm interested to learn what made you choose to fork BEEM rather than starting