Tootfinder

Opt-in global Mastodon full text search. Join the index!

@pre@boing.world
2025-11-22 15:23:38
Content warning: re: bitcoin conference report

Bit root is explaining why there will only be 21 million bitcoin.
Block rewards every ten minutes halving every for years is an infinite sum tending to that 21m supply. In fact a few sats less due to rounding errors.
She explains why bit shift in the code is the same as halving due to the way binary number representation works.
The code stops shifting at 64 halvings , despite the fact the reward will be zero after 32. This is since c leaves 64 bits shifted off a 64 bit number as undefined.
But could the code just be changed? No. The source code maintainers could try, but node runners would refuse the update, it being against their financial interests to do so. Even if some nodes did do, you on your own node can resist.
When people created forks with more supply, the market sent it's price to zero.
#bitfest #bitcoin

@andres4ny@social.ridetrans.it
2025-11-22 19:50:50

Wow. I've dealt with various toxic personalities in software development, but a good portion of the time those toxic personalities were at least extremely knowledgeable in their (often, very limited) domain.
AI, however, seems to be enabling toxic personalities *who are completely clueless*. Impressive!
github…

quoted text: "Your approach of submitting very large relatively-low-effort PRs creates a very real risk of bringing the Pull-Request system to a halt, especially given that, in my personal experience, reviewing AI-written code is more taxing that reviewing human-written code."

response: "I do not intend to submit any more PRs of this kind. This was a proof of concept and an attempt to push AI as far as it would go. I believe that it has succeeded brilliantly! Also, *I would not call this a l…
quoted text: "we have in fact known this for years and the difficulty is to find a way to do it that maintainers agree comes at a reasonable maintenance burden)."

response: "I’m not a compiler developer by trade, although I’ve done all sorts of development over the years. I’m approaching this strictly as a user, perhaps a power user. I used to look at my needs and wants, and sulk because they were not addressed.

Damn, I can’t debug OCaml on my Mac because there’s no DWARF info.

Oh, wow…
quoted text: "I think that it is a case of different-to-the-point-of-being-incompatible software development processes (rather than a given process being fundamentally right or wrong), and I think that the uncertainty here is in part caused by our lack, on the upstream side, of a clear policy for what we expect regarding AI-assisted code contributions."

response: "That is something I’ve been pondering myself. I tried approaching several projects this way, trying to take care of things that b…
@frankstohl@mastodon.social
2025-10-25 15:50:26

Guter Web-Client für Mastodon #bcs18 elk.zone/m.webtoo.ls/public/lo

@ruth_mottram@fediscience.org
2025-10-18 15:55:48

And that's a wrap - the newly refreshed laptop has been handed over to teen with most of the packages functional. Thanks for following along on this @… installation journey with me and thanks to all #linux maintainers, forum contributors and FOSS advocates around keeping the system running.
👏 WE REALLY APPRECIATE YOU!👏
The final judgement won't be clear until Monday when the first log in at school happens but hopefully it will be successful, or the IT support is going to have to deal with some very salty comments (from me).
16/16
FIN

@mgorny@social.treehouse.systems
2025-10-23 16:55:56

Another post on #Quansight PBC blog: "BLAS/LAPACK #packaging"
#BLAS and #LAPACK are the standard libraries for linear algebra. The original implementation, often called Netlib LAPACK, developed since the 1980s, nowadays serves primarily as the origin of the standard interface, the reference implementation and a conformance test suite. The end users usually use optimized implementations of the same interfaces. The choice ranges from generically tuned libraries such as OpenBLAS and BLIS, through libraries focused on specific hardware such as Intel® oneMKL, Arm Performance Libraries or the Accelerate framework on macOS, to ATLAS that aims to automatically optimize for a specific system.
The diversity of available libraries, developed in parallel with the standard interfaces, along with vendor-specific extensions and further downstream changes, adds quite a bit of complexity around using these libraries in software, and distributing such software afterwards. This problem entangles implementation authors, consumer software authors, build system maintainers and distribution maintainers. Software authors generally wish to distribute their packages built against a generically optimized BLAS/LAPACK implementation. Advanced users often wish to be able to use a different implementation, more suited to their particular needs. Distributions wish to be able to consistently build software against their system libraries, and ideally provide users the ability to switch between different implementations. Then, build systems need to provide the scaffolding for all of that.
I have recently taken up the work to provide such a scaffolding for the Meson build system; to add support for BLAS and LAPACK dependencies to Meson. While working on it, I had to learn a lot about BLAS/LAPACK packaging: not only how the different implementations differ from one another, but also what is changed by their respective downstream packaging. In this blog post, I would like to organize and share what I have learned.
"""
#CondaForge #Debian #Fedora #Gentoo

@cyrevolt@mastodon.social
2025-09-26 08:33:41

Really nice interview:
github.blog/open-source/mainta
I chose Ele…

@arXiv_csCR_bot@mastoxiv.page
2025-10-07 08:45:02

Shrinking the Kernel Attack Surface Through Static and Dynamic Syscall Limitation
Dongyang Zhan (Harbin Institute of Technology), Zhaofeng Yu (Harbin Institute of Technology), Xiangzhan Yu (Harbin Institute of Technology), Hongli Zhang (Harbin Institute of Technology), Lin Ye (Harbin Institute of Technology)
arxiv.org/abs/2510.0372…

@khalidabuhakmeh@mastodon.social
2025-12-02 13:15:43

For folks forking IdentityServer. It's not "just code". There are decades of understanding specs, working with security teams around the world, ongoing support, and doing all those things continually.
When it comes to security, staying behind, or even worse, standing still, is the worst option.
From a maintainers perspective, think of doing all of the above for FREE to save your employer money for the "atta boys". In the meantime wasting the most precious …

@karlauerbach@sfba.social
2025-12-03 23:32:24

Once again I wonder "Do the authors/maintainers of LibreOffice actually use it?"
For example, I am here on MacOs (Tahoe) and the buttons in LibreWriter to control Bold, Italic, etc are effectively same-color-on-same-color-background, in other words, unreadable. The only time they are actually visible is when the "Dark" theme is used.
Almost every time I use LibreOffice I am reminded why people pay actual $$ for products like Word/Office365.

@adulau@infosec.exchange
2025-12-09 09:12:37

GCVE-BCP-02 Published - Version 1.3 (2025-12-09)

We’re pleased to announce the publication of GCVE-BCP-02 – Practical Guide to Vulnerability Handling and Disclosure, now available in its version 1.3.
This Best Current Practice document provides actionable guidance for organisations, researchers, and GCVE Numbering Authorities (GNAs) on managing and disclosing vulnerabilities effectively, both within the GCVE ecosystem and beyond

@thomasfuchs@hachyderm.io
2025-10-06 04:09:48

Community-driven alternative to rubygems.org just dropped: #tuby #gems