Professional C# .NET developer, React and TypeScript hobbyist, proud Linux user, Godot enthusiast!
They provide decent defaults for all the not-so-straightforward configurations, and they provide a web UI to configure the rest. That’s the sole reason I would recommend it to get one’s feet wet without having to work too much.
If one is committed to do things “the right way” they could switch to Nginx and “proper” self-hosting later.
Yeah, I’m afraid you have to use a reverse proxy to host multiple subdomains. The CloudFlare daemon is the reverse proxy.
I would say this would be the proper way to do it (at least as a sysadmin), but since it’s OP’s first time I would simplify it to:
Let CloudFlare handle the certificates, DDoS protection, etc… Link if you’d like to give this setup a try.
[…] re‑engineered flash physics by replacing silicon channels with two‑dimensional Dirac graphene and exploiting its ballistic charge transport.
By tuning the “Gaussian length” of the channel, the team achieved two‑dimensional super‑injection, which is an effectively limitless charge surge into the storage layer that bypasses the classical injection bottleneck.
That’s some seriously technical jargon.
ChatGPT seems to be able to explain, not sure how accurate it is though.
Flash memory traditionally uses silicon channels to move charges (electrons) into a storage layer. These researchers changed that by replacing silicon with Dirac graphene. Graphene is a single layer of carbon atoms arranged in a honeycomb structure. It’s called a Dirac material because its electrons behave like massless particles, moving extremely fast and with very little resistance.
This leads to ballistic transport: electrons move without scattering, like a bullet in a vacuum. This is far more efficient than silicon, where electrons bump into atoms and lose energy.
Tuning the “Gaussian length" likely refers to modifying the shape or spread of the electric field or potential in the channel (possibly shaped like a Gaussian curve, i.e., a bell curve). By adjusting this, they control how charge flows.
Achieved two-dimensional super-injection means they were able to push a large amount of charge very efficiently from the graphene channel into the memory storage layer, and in a 2D way (across the flat graphene surface), rather than through a narrow point.
Effectively limitless charge surge: normally, in flash memory, there’s a bottleneck where only so much charge can be injected due to energy losses and scattering. But with graphene’s ballistic transport and this super-injection method, that bottleneck is gone—or drastically reduced—enabling faster and more efficient memory writing.
Then what’s even is the point of this license? There will always be a third party distributing unofficial binaries.
And if this license forbade third parties to redistribute binaries, then it would no longer really be FOSS.
Fair enough, but then it’s the same thing as open-sourcing the code but not providing support nor binaries.
I mean, personally I also prefer it to FUTO’s proprietary license, that’s for sure. But I’m one of the few privileged users who can build from source.
If this license doesn’t impose any extra restrictions on the code (and as you say, anyone can fork and provide prebuilt binaries), then this would just increase the risk of spreading malware, with no real benefits for the original developers.
In my opinion, if you want to monetize your software without going proprietary, all you have to do is provide the users a convenient way to get it. There are some paid FOSS apps on Google Play, as well as some paid FOSS games on Steam. You don’t want to distribute binaries? Fine, okay, that’s alright and I respect your choice. You don’t want to provide support to non-paying users? Fine, that’s very reasonable in my opinion. But…
…do you want to impose extra restrictions on your code? Fine to me, but then you are no longer doing open source, don’t try to pretend you are. And if you are not imposing any restrictions on the code then you are imho just going to hurt small users. We shouldn’t fight small users imho, we should fight the big corporations exploiting FOSS code for their proprietary businesses. But if there are no extra restrictions on the code, then big corporations wouldn’t care.
That’s my opinion.
I’m not a lawyer, but this doesn’t seem to be compatible with (A)GPL licenses.
I would say this is going to harm small users more than big corporations. As a small user I might be unable to build from sources myself, so I would have to pay. But as a big corporation building from source would be something I can certainly do trivially, then I wouldn’t be subject to the restrictions imposed by this license.
Imho, if someone wants to force their users to pay, then they are not doing open source. Please let’s not try to pretend we are by adopting a OSI-approved license and slapping extra restrictions on top of it.
Just go AGPL for datacenter-oriented softwares, or GPL for drivers and embeddable code, or a proprietary license such as FUTO’s for end-user software.
All repositories related to emulation and Nintendo, some of which I backed up on a self-hosted Forgejo instance.
Also, everything that you use and doesn’t have more than 2 or 3 maintainers.
No no, this is actually open source. Not just the ISA, but also the silicon.
Well… that would make sense. But it’s much much easier to just do it preemptively. The browser API to check how much memory is available are quite limited afaik. Also if there are too many elements the browser will have to do more work when interacting with the page (i.e. on every rendered frame), thus wasting slightly more power and in a extreme cases even lagging.
For what it’s worth, I, as a web developer, have done it too in a couple occasions (in my case it was absolutely necessary when working with a 10K × 10K table, way above what a browser is designed to handle).
Actually that might not have been done to deliberately disrupt your flow. Culling elements that are outside of the viewport is a technique used to reduce the amount of memory the browser consumes.
In my experience, a great portion of competitive multiplayer games work. Although I have to admit that I mostly play games meant to be played among friends rather than against strangers.
If you are not talking about Steam, which comes with Proton out of the box, I’d recommend to give Legendary a try. It’s basically the same thing, but with non-Steam games. And it’s very user-friendly, like Steam.
I use DDG for the privacy as well, but personally I think it works better than Google in my field (software development). The only issue I personally have with DDG is that it lags behind Google in terms of updates, I notice when searching for something that came out or happened only recently.
This is a screenshot from uBlock Origin, an ad-blocker for browsers. Red means that something is in a block list. There is a lot of red, which means this website uses a lot of stuff that tracks the user or serves ads.
That being said, I’ve seen much worse.
Are you sure about that? That would be surprising for me, as I had never before heard about Electron running on mobile.
A quick dive in Element Android’s dependencies didn’t reveal any mentions of Electron, but perhaps it’s referenced in some other way.
Signal desktop client is actually Electron based. And AFAIK, Electron doesn’t run on Android, only on the desktop.
A less salty way to put it would be that the chart is missing two labels: “Original prompt” and “Poisoned prompt”.
Here’s my config for reference, which works for me:
name: forgejo services: forgejo: image: codeberg.org/forgejo/forgejo:12 environment: - USER_UID=1000 - USER_GID=1000 restart: always volumes: - ./data:/data - /etc/timezone:/etc/timezone:ro - /etc/localtime:/etc/localtime:ro ports: #- 80:3000 - 2222:22 networks: - nginx networks: nginx: name: nginx external: trueIf you can share your error message we might be able to better pinpoint the issue.
EDIT: I searched a bit and now I understand better what you are trying to do. I didn’t know about this “SSH shim” idea. This is not what I have done on my setup, sorry.