(ok i see, you’re using the term CPU colloquially to refer to the processor. i know you obviously know the difference & that’s what you meant - i just mention the distinction for others who may not be aware.)

ultimately op may not require exact monitoring, since they compared it to standard system monitors etc, which are ofc approximate as well. so the tools as listed by Eager Eagle in this comment may be sufficient for the general use described by op?

eg. these, screenshots looks pretty close to what i imagined op meant

now onto your very cool idea of substantially improving the temporal resolution of measuring memory bandwidth…you’ve got me very interested with your idea :)

my inital sense is counting completed L3/4 cache misses sourced from DRAM and similar events might be alot easier - though as you point out that will inevitably accumulate event counts within a given time interval rather than an individual event.

i understand the role of parity bits in ECC memory, but i didn’t quite understand how & which ECC fields you would access, and how/where you would store those results with improved temporal resolution compared to event counts?

would love to hear what your setup would look like? :) which ECC-specific masks would you monitor? where/how would you store/process such high resolution results without impacting the measurement itself?

CPU and Memory use clock speed regulated by voltage to pass data back and forth with no gates between

could you please explain what you mean by no gates?

Reading up on RDP

Microsoft requires RDP implementers to obtain a patent license

there it is. good info to dig up jrgd, well done! shame we had to scroll so far in the thread to find these actual proper, highly relevant details.

well, everyone has to pick their battles, and perhaps RHEL just couldn’t fight this one out.

but imo i’d much rather see VNC get some upgrades under RHEL than continue the ever increasing microsoft-ization of linux

i’m trying to understand your exact needs, but i’m honestly surprised cookie auto delete can’t do it.

could you explain exactly what you’re trying to accomplish? and the wall you hit with cookie auto delete to do it?

deleted by creator

edit: nvm i re-read what you wrote

i agree it does mostly fulfill the criteria for libre software. perhaps not in every way to the same spirit as other projects, but that is indeed a separate discussion.

h̶o̶w̶ ̶m̶a̶n̶y̶ ̶c̶o̶m̶m̶u̶n̶i̶t̶i̶e̶s̶ ̶a̶r̶e̶ ̶d̶o̶i̶n̶g̶ ̶t̶h̶a̶t̶ ̶r̶i̶g̶h̶t̶ ̶n̶o̶w̶?̶ ̶i̶ ̶s̶u̶s̶p̶e̶c̶t̶ ̶y̶o̶u̶ ̶m̶a̶y̶ ̶b̶e̶ ̶d̶r̶a̶s̶t̶i̶c̶a̶l̶l̶y̶ ̶u̶n̶d̶e̶r̶s̶t̶a̶t̶i̶n̶g̶ ̶t̶h̶e̶ ̶b̶a̶r̶r̶i̶e̶r̶s̶ ̶f̶o̶r̶ ̶t̶h̶a̶t̶.̶ ̶b̶u̶t̶ ̶w̶o̶u̶l̶d̶ ̶b̶e̶ ̶d̶e̶l̶i̶g̶h̶t̶e̶d̶ ̶t̶o̶ ̶b̶e̶ ̶p̶r̶o̶v̶e̶n̶ ̶w̶r̶o̶n̶g̶.̶.̶.̶

Thanks for the reference, from there I found the very impressive original Nature paper “A RISC-V 32-bit microprocessor based on two-dimensional semiconductors” fantastic stuff!!

From the paper, that’s almost a 40x improvement on comparable logic integration!

Some notes from the paper:

• Transistor channel length is 3 um
• Clock speed is 1 kHz

Typically this is where people like to shit on the design “cos muh GHz” etc, but tbf not only will people doubtless work on improving the clock speeds etc, but there’s plenty of applications where computation time or complexity isn’t so demanding, so i’m just excited by any breakthrough in these areas.

if this is a full RISCV implementation in 2D materials this is a genuinely impressive breakthrough!!

afaict the topic of the article seems to be focusing on trust as in privacy and confidentiality

for the discussion i think we can extend trust as in also trusting the ethics and motivation of the company producing the “AI”

imo what this overlooks is that a community or privately made “AI” running entirely offline has the capacity to tick those boxes rather differently.

trusting it to be effective is perhaps an entirely different discussion however

feeling like you’ve been listened to can be therapeutic.

actionable advice is an entirely different matter ofc.

Or they’re just adding improvements to the software they heavily rely on.

which they can do in private any time they wish, without any of the fanfare.

if they actually believe in opensource let them opensource windows 7 ¹, or idk the 1/4 of a century old windows 2k

instead we get the fanare as they pat themselves on the back for opensourcing MS-DOS 4.0 early last year (not even 8.0, which is 24 years old btw, 4.0 which came out in 1986).

38 years ago…

MS-fucking-DOS, from 38 years ago, THAT’S how much they give a shit about opensource mate.

all we get is a poor pantomime which actually only illustrates just how stupid they truly think we are to believe the charade.

does any of that mean they’re 100% have to be actively shipping “bad code” in this project, not by any means. does it mean microsoft will never make a useful contribution to linux, not by any means. what it does mean is they’re increasing their sphere of influence over the project. and they have absolutely no incentive to help anyone but themselves, in fact the opposite.

as everyone knows (it’s not some deep secret the tech heads on lemmy somehow didn’t hear about) microsoft is highly dependent on linux for major revenue streams. anything a monolith depends on which they don’t control represents a risk. they’d be negligent if they didn’t try to exert control over it. and that’s for any organisation in their position. then factor in their widespread outspoken agenda against opensource, embrace, extend, extinguish and the vastly lacking longterm evidence to match their claims of <3 opensource.

they’re welcome to prove us all wrong, but that isn’t even on the horizon currently.

¹ yes yes they claim they can’t because “licensing”, which is mostly but not entirely fucking flimsy, but ok devils advocate: release the rest, but nah.

yes they lost the battle, now they’re most likely aiming to win the war.

A lot of Microsoft-oriented developers still don’t understand the free software movement, and have been trying to twist it into something they can comprehend since it started four decades ago.

ah fair enough. i think that was the initial confusion from myself and perhaps the other user in this discussion. i didn’t realise your use cases.

it’s always a fun topic to discuss and got me thinking about some new ideas :)

afaik mmW is FR2

5G FR1 is sub x-band microwave

cool, sounds like you have most of the principles down.

what i didn’t yet see articulated with chat-e2ee is how the actual code itself verifies itself to the user in the browser? it sounds to me like it assumes the server which serves the code is ‘trusted’, while the theoretically different server(s) which transmits the messages can be ‘untrusted’.

out of interest, do you actually mean no login, or do you mean no email-verified login?

i’m trying to understand your exact scenario.

but in general, the problem is where do you get your original key, or original hash to verify from? if they are both coming from the server, along with the code which processes them, then if the server is compromised, so are you.

thankfully browsers give alot of crypto API lately (as discussed in your link)

but you still need at minimum a secure key, a hash and trusted code to verify the code the server serves you. there are ofc solutions to this problem, but if the server is unstrusted, you absolutely can’t get it from them, which means you have to get it from somewhere else (that you trust).

-GIMP is freeware.

did you source that from the GIMP documentation? because it very much appears you didn’t. (please link to the direct quote if i’m wrong).

in contrast my quote comes directly from page 4 of their own PDF User Manual which very clearly states:

The GIMP is not freeware

personally i’ll go with what GIMP says in their own manual. you’re welcome to believe whatever thing you wish - enjoy.

edit: it just occurred to me you may not be a native english speaker, in which case i apologise. “typically not” means it usually doesn’t happen.

For anyone who’s wondering (from the GIMP manual)

The GIMP is not freeware

GIMP er ikkje såkalla “freeware”

El GIMP no es freeware

GIMP non è freeware

GIMP n’est pas un freeware

Thanks for the distinctions and links to the other good discussions you’ve started!

For the invasive bits that are included, it’s easy enough for GrapheneOS to look over the incremental updates in Android and remove the bits that they don’t like.

That’s my approximate take as well, but it wasn’t quite what I was getting at.

What I meant is, to ask ourselves why is that the case? A LOT of it is because google wills it to be so.

Not only in terms of keeping it open, but also in terms of making it easy or difficult - it’s almost entirely up to google how easy or hard it’s going to be. Right now we’re all reasonably assuming they have no current serious incentives to change their mind. After all, why would they? The miniscule % of users who go to the effort of installing privacy enhanced versions of chromium (or android based os), are a tiny drop in the ocean compared to the vast majority of users running vanilla and probably never even heard of privacy enhanced versions.