sylware

Regulation on small tech interop is exactly for guys like you.

Open source is not enough: _LEAN_ open source is a strong requirement today... and that includes syntax complexity of any used computer languages.

The scammers are now doing open source vendor/dev lock-in via massive size and complexity... while there are small and stable in time alternatives able to do a good enough job. Those guys are not all malicious, many are just brain washed and some suffer from a mental disorder: accute Rube Goldberg Machine syndrome.

Spam does not work with email addresses using IP literals.

twitch.tv has new HLS streamers which break ffmpeg HLS.

Use lynx, links or netsurf. Or vibe code your noscript/basic HTML web engine?

I think DMARC is missing email address with IPv[46] literals support. As being self-hosted, without paying the DNS mob, I am still blocked to send email to gmail.com because such email addresses do throw out of whack gogol code.

Email addresses with IPv[46] literals are intrinsincly stronger than SPF. If in the envelope or any of the 'from' headers (if my memory does not fail me, there are few more headers to scan), the IPv[46] literal does not match the actual and real IP of the SMTP server, the email is dropped, not even going into any spam folder.

Conspiracy mode: they know and are careful not to support that, in order to create a walled garden of internet messaging for them and their friends.

Weird.

I download RSS from gogol: youtube channel information. Why, because the real evil of gogol and its friends: the whatwg cartel. Their web engines are technical abominations they pushed down the throat of the whole planet, because they actually control all (including the SDK then the computer language). How? They break on purpose interop with small tech web engines, aka noscript/basic HTML.

What's really annoying are major authorities unable to regulate that, namely force interop with small tech (network protocols/file formats)... like they know but are careful not to do anything with a significant impact. Well, In my EU country, this is decided at the top level: prime minister and president and that's it: this is a sorta proof that matter is actually really important. Everything started to go wrong from my EU country gov of 2015/2016 since they 'forgot'(ooopsie!) small tech web engines in the 'master document'.

There is still hope, once small tech is added again to this 'master document' (web engines, currated subset of network protocols and file formats), interop with small tech web engines (most are EU) will have to be added, in 3 years.

Well, in theory, with proper UTF-8 support you don't need to filter out anything.

Unsupported unicode code points are just rendered using a place holder.

fasmg[12] is much more powerful than gas or nasm(~yasm): it is not a classic pre-processor. With CALM, it is basically a language able to implement assemblers supporting various binary file formats.

The pre-processor of an assembler is specific to that very assembler.

For instance, with a C pre-processor, I have a very lean C pre-processor dialect which allows me to assemble simple x86_64 code with... fasmg[12] or nasm(probably yasm) or gas(intel syntax).

A big project which was bitten by specific pre-processor abuse: ffmpeg with nasm (but it is still much less toxic than to start to be hard dependent on advanced and specific C compiler extensions... look a the failure from linux on that matter).

I am more curious about how they would cleanly manage hierarchical labels (usually called "namespaces"), register naming, and stack management with deep register spilling, description of the register state on the various entries from the various dominators of a code block.

I am doing all that with a basic C pre-processor in my assembly source code. But the more I think about this, the more I think I should write my own pre-processor, which "should" be much simpler than a C pre-processor in the end and would do a cleaner job since taylored for those usages (the "annoying" thing is the arithmetics expression evaluation).

I would write this pre-processor in assembly, namely design a binary specification (that to be ready for other ISA implementations).

Then, they are the really important things: for all micro-architectures, how to be friendly to conditional branch predicition, how to handle BTB entries layout in a cache line, show how important the "cache line" is ubiquitous, etc.

I remember clearly one of the TheHeavyThing developers telling me than with a basic and naive hand compilation of gzip, he was beating the best compilers, at that time, by a consistent 10/15%. Let me remind people here of something: nobody is supposed to be able to beat a compiler on deep and hairy compilation units. If it is the case, something is wrong in that compiler.

My projects are gone from microsoft github.com. Not because I decided to move away, but mostly because github.com is now blocking noscript/basic HTML browsers for most of its basic functions, then it was actually them who did boot me away.

Small Tech Discrimination.

It is never really for "One". If it is open source and published, It may be use by others... not to mention coding AI ML (Machine Learing), then for many.

I have written so much software for one... I cannot recall everything. I use some of it daily:

- I have my custom elf(glibc)/linux distro

- I use my own ffmpeg based x11 media player (will have an update for wayland).

- Since the "geniuses" at gogol blocked all accounts not using whatwg cartel web engines and blocked all self-hosted SMTP servers (I do not pay the DNS mob, then IP literals, which is stronger than SPF) to exchange with gmail.com users (now prisoners), I have my very own simple noscript/basic HTML servers (messaging, file transfer, openstreetmap browsing, etc). Unfortunately, most are C written from linux instead of assembly (at least, I removed most of the time the libc dependency with direct syscall programming). IPv6 is making everything internet software muuuuuuch easier to implement: I am lurking at an IPv6 only, super idiotic and real time voice/video/text/file transfer protocol, probably based on SIP (the main issue are randomly generated IPv6 addresses from mobile internet, which may require a mini-server for IPv6 address exchange, BAAAAAAAD!).

- Ofc, I still have my own minimal SMTP server (and a SMTP client to send emails), because there are still honnest people on internet. mutt forever.

- I am trying to build a RCS for linux, aka a Reduced Command Set with near direct hardwiring to linux syscalls. I lose comfort, but knowing that I removed giga tons of bloat feels so much satisfying it is worth it by light years. I will have to code my own command shell one day.

I still have C code since I currently need portability on IP-LOCKED ISAs (arm and x86-64). But I wish for RISC-V to be a success, namely as a modern, very often hitting the 'sweet spot' in technical design compromises, NON-IP-LOCKED ISA. I am writting much software in RISC-V assembly now... which I run on x86-64 with a small interpreter (written in x86-64 assembly)... trying to fix the bloat and kludge from corpo-like open source software (including the SDK).

Right now, I am writting my own wayland compositor using that framework. I was not expecting window management to be a bazillion of little things to do everywhere. And even if a wayland compositor is several orders of magnitude smaller and leaner than a x11 server, it ain't that a small project (ofc, I implemented myself the wayland wire protocol, no external libs here).

In my 'trying to fix the bloat and kludge' from corpo-like open source, I force myself to use my own exe/dynamic lib format for modern hardware (so lean, a simple RFC will be enough, and no more loader bloat/kludge). But I am scared at the abominations which are all the requirements of classic computer languages to run: I would like a mesa vulkan driver, but there is still c++ (super BAD) in there which makes porting to an alternative dynamic lib format a living hell, non trivial C won't be that easy neither (for instance the abomination of the ISO __thread keyword, amazing bright minds there). Taking perspective from that, I wonder why anybody sane would add on top of that a big runtime requirement??

And what people doing that have to keep in mind: IRL can put a violent stop to all of this.

Switch back gcc to plain and simple C, or support a c++ to plain and simple C transpiler, which would be written in plain and simple C (I think some people did revive cfront with AI based coding). Even microsoft rust has its C transpiler.

Is Sabine H. on the case?

With EU manufactured chips?

Priorities...

noscript/basic HTML? That would be awesome actually, don't forget the web engines from the whatwg cartel are abominations.

There are videos on youtube on the previous deep FBI/services hardware tech scheme.

In this context, grapheneos looks like more just 'And Another Time...'.

In the end, it does not matter: we all know here that "information system security" is a fantasy, it does not exist. When somebody does pretend the opposite: this person wants to scam you or sell you something.

Let me add a bit more:

The part which in missed all the time is the control of the glibc ABI version. Either you link with an "old" glibc, or you go 'Right Way(TM)', documentation is on binutils web site (noscript/basic HTML) : https://sourceware.org/binutils/docs/ld/VERSION.html

Must include glibc internal symbols.

I would use the "readelf" command to audit the binaries for broad elf(glibc)/linux distro support (like stock unity has been). Namely DT_NEED entries, symbol/shared lib version requirement (at the end of readelf output), etc.

An additional note: in the case of a complex set of ELF64 binaries, don't forget that ELF DT_RPATH is deprecated in favor of ELF DT_RUNPATH (see man page of ld.so). To force DT_RPATH into DT_RUNPATH, you must use the follower binutils ld option: '--enable-new-dtags' (using the compiler driver, that would be '-Wl,--enable-new-dtags'. Carefull, you'll see that in ld.so man page, DT_RPATH and DT_RUNPATH do not behave the same way. You should use dynamic loading for your private shared libs using the $ORIGIN keyword anyway.

Ofc, dynamic loading (libdl/dlopen/dlsym/dlclose) is mandatory for system interface shared libs, and for core video games: libX11 set or xcb set of client X11 libs, libasound (wayland code is statically linked with its libxkbcommon for xkb keymap handling). Basically, The DT_NEED entries of your set of ELF64 binaries must reference only common glibc libs (and if you don't dynamically load them, your private ones with proper DT_RUNPATH).

If AI does become ubiquitous, you will have those with access to super hardware in datacenters to have a fast dev loop for prompts on gigantic models (aka $$$), and those for who it will takes ages to run even one simple prompt, or at best will get low result quality due to the usage of 'quantized' and/or small models.

Me, I would be in the second population: currently, access to performant inference hardware in datacenter is gated with whatwg cartel web engines (a shame).

That said, if AI does become ubiquitous, hardcore regulation on its access will happen, but when I look at the web from my administration in my EU country... slaves of Big Tech (the bad americans who the good americans fail to regulate... and I don't blame them, it is so hard).

Don't forget to build 'correct' ELF64 binaries for broad elf(glibc)/linux distro support (-static-libgcc -static-libstdc++, and tight glibc ABI version control with binutils VERSION scripts).

At least those build options should be default.

This grapheneOS may be another scheme from the 'deep FBI'/'services' to get intel on the very, VERY, nasty (terrorists, human traffickers, drug cartels, child stuff, etc). If I recall properly, they did that in the past (it seemed to have worked amazingly).

If so, "normal" police would not have the "keys". This would be "the compromise".

I don't recall exactly which one has javascript mandatory (namely is gated with 'whatwg cartel' web engines): this very codeberg or sourcehut?

I did watch your vid: it is for quantized deepseek models. I would look for full weight inference for maximum quality.

For instance, do we have similar benchmarks on the latest frontier open weight KIMI model at several tera-weights (I would be interested at coding prompts)?

"anti-trust" in many EU countries, is made of "competition authorities", namely dominant corporations on some significant "markets" get strong rules forced upon them that to allow to exist any reasonable real-life alternatives.

Here, Big Tech must interop with Small Tech. A common malicious behavior from Big Tech is to inflate by tons the required complexity and size of their 'tech' in order to make it out of reach by small competitors. This is one of the roles of market regulation. It seems they are now using 'security' (something which is only best-effort, it actually does not exist) to scare people to go to alternatives (how deep the rabbit hole goes here... mmmmh...)

In my EU country, we have a very good internet, thanks to _HARDCORE_ regulation which allowed small alternatives to be bootstrapped and to exist and grow. It is a bit different for gogol which is trying to create a 'very walled garden' like the "rotten fruit" company with this 101 malicious behavior on the long run: strong interop with 'Small Tech' at the beginning, slowly (~decade+) but surely this interop is broken to favor the 'Big Tech' from their cartel.

It is really complex: devil hides in the 'technical' details, it is case by case over some kind of continous spectrum. Here, it boiles down to the complexity/size of protocols, file formats with their stability in time: if you regulate here, "Small Tech" becomes a real-life alternative.

And don't be a fool at believing they are not talking to each other and play fair...

I don't know if having a real-time ML/inference model (brain simulation with realtime input/output) is even remotely possible for a significantly big size.

Let alone those models be 'stable'.

Anybody did transpile it to C with the microsoft rust to C transpiler?

google:

1 - restore interop with noscript/basic HTML browsers, stop favoring your 'whatwg cartel' web engine.

2 - gmail: restore interop with self-hosted SMTP servers without DNS (filtering on the IPv[46] literal from email address, this is stronger than SPF).

And there is probably more to add.

I'll watch this video once I am on my yt-dlp rig. Hopefully, those are 1T-2T params models.

If "AI" becomes ubiquitous, it may end up pushed out of the 'standard economy' and made sorta an 'utility' (to speak using US words). Because, you will have those able to pay for performant AI... and the other ones. To mitigate that, running locally at decent (but still slow) speed, frontier models, may become critical.

I say that: I have never fooled around with AI since they are gated with 'whatwg cartel' web engines.

Clearly something you need to keep an eye on. And "everything pushing RISC-V forward is a good thing".

The trick is with current tension between the US and Spain: hopefully intel won't "be told" to pull out from this project, because I don't thingk TSMC has the production capacity to accomodate such project decently (and RISC-V is a US initiative!!). (I am talking latest silicon process, because without it, even an amazing micro-architecture will be dragged down).