I’m in the same boat as you, with decades of projects I want to be able to open.
However, OP mentioned Reaper, which has a native Linux version! So as long as they’re not using a load of VSTs, and the ones they do play nicely with Linux, it could work out for them
The only way is to give it a go and find out though
That thumbnail lol
No. 5 was a fun mental image
Cheers for the response, I appreciate it!
I’m curious about the plugins as obviously I’m not gonna be familiar with the notepad++ plugin ecosystem now—what’s special about the ones you listed?
Assuming edit EOL is just changing the line termination characters, all editors have that don’t they? Or does this not do what I think?
Intrigued about VSCode being slow for text manipulation too—I remember this being a big reason I dropped notepad++ for sublime and IMO VSCode and sublime more or less have parity on that front, particularly with vim bindings
I just don’t get the love for notepad++
I started using it as my main back in 2006ish, I then switched to sublime text about 2011, then about 5-6 years ago to VSCode. All the time using vim for any in-terminal quick edits.
Notepad++ is easily my least favourite editor of the lot, by several miles, it just seems so rigid and clunky without even going into how it’s windows only. Every editor I’ve used since has been a huge improvement over the one prior IMO
If this actually rings true, there’s something pretty wrong in your team.
Stand up should be a quick and uncontroversial meeting talking about what you’ve done, what you’ll do and anything you need help with, plus maybe a couple of minutes of small talk before you start.
The comfortable one is unfortunately an ultimate feature that we don’t get in our plan
I still don’t know why this architecture went for a Double XOR as the NOP, I guess they were just flexing that the reference chip design could do both in a single cycle
Lagunitas is pretty banging tho
No need to get aggravated, I completely grasp it, you’ve possibly misunderstood or not entirely read my comment if that’s your takeaway.
I’m not talking about server code specifically, I’m going through the stages between the source code repo(s) and what your browser ends up receiving when you request a site.
NodeJS is relevant here because it’s what runs nearly all major JS bundlers (webpack, vite, etc), which are what produces the code that ultimately runs in the browser for most websites you use. Essentially in a mathematical sense, the full set of dependencies for that process are a part of the input to the function that outputs the JS bundle(s).
I’m not really sure what you mean with that last part, really, anyone hosting something on the internet has to care about that stuff, not just businesses. GDPR can target individuals just as easily as for-profit companies, it’s about the safety of the data, not who has it—I’m assuming you would not want to go personally bankrupt due to a deliberate neglect of security? Similarly, if you have a website that doesn’t hit the performance NFRs that search engines set, no one will ever find it in search results because it’ll be down on page 100. You will not be visiting websites which don’t care about this stuff.
Either way, all of that is wider reasoning for the main point which we’re getting away from a bit, so I’ll try to summarise as best I can:
Basically unless you intend your idea to only work on entirely open source websites (which comprise a tiny percentage of the web), you’re going to have to contend with these JS bundles, which as I’ve gone into, is basically an insurmountable task due to not having the complete set of inputs.
If you do only intend it to work with those completely open source websites, then crack on, I guess. There’s still what looks to me like a crazy amount of things to figure out in order to create a filter that won’t be able to work with nearly all web traffic, but if that’s still worth it to you, then don’t let me convince you otherwise.
Edit: typo
First I don’t even grasp what a “service owner” is.
The people who build & run the software & servers that serve the website, who amongst other things have an interest in keeping the service available, secure, performant, etc.
Particularly with laws like GDPR, these services owners are motivated to be as secure as practically possible otherwise they could receive a bankrupting fine should they end up leaking someone’s data. You’ll never be able to convince anyone to lower the security of their threat model for that reason alone, before anything else.
there are already a bunch of app (web, android) that are open-source and secured.
The code published and the code running on a server cannot be treated as equivalent for several reasons, but here’s two big ones:
Firstly, there’s the similar issue as with compiled binaries in other languages: it’s tough (or impossible) to verify that the code published is the same code that’s running. Secondly the bundled and minified versions of websites are rarely published anyway, at most you get the constituent code and a dependency list for something completely open source. This is the bit I referred to before as trying to untoast bread, the browser gets a bundle that can’t practically be reversed back into that list of parts and dependencies in a general purpose way. You’d need the whole picture to be able to do any kind of filtering here.
who is the attacker here?
The only possible attacker is not the website itself (though it’s a lot more limited if the site implements CSP & SRI, as mentioned in my other comment). XSS is a whole category of attacks which leverage an otherwise trusted site to do something malicious, this is one of the main reasons you would run something like noscript.
There have also been several instances in recent years of people contributing to (or outright taking over) previously trusted open source projects and sneaking in something malicious. This then gets executed and/or bundled during development in anything that uses it and updates to the compromised version before people find the vulnerability.
Finally there are network level attacks which thankfully are a lot less common these days due to HTTPS adoption (and to be a broken record, CSP & SRI), but if you happen to use public WiFi, there’s a whole heap of ways a malicious actor can mess with what your browser ultimately loads.
Maybe I have missed your point, but based on how I’ve understood what you’ve described I think you may have also missed mine, I was more pointing out how the practicalities prevent such a tool from being possible from a few perspectives. I lead with security just because that would be the deal breaker for many service owners, it’s simply infosec best practice to not leak the information such a tool would require.
Your filtering idea would require cooperation from those service owners to change what they’re currently doing, right?
Perhaps I’ve completely got the wrong end of the stick with what you’re suggesting though, happy to be corrected
Publishing lock files of running services would be a big security risk for the service owner as it gives an easily parsable way for an attacker to check if your bundle includes any package versions with vulnerabilities.
You then also have tools like snyk used by many big organisations which has the ability to patch dependencies before the actual dependency published the patch themselves. This would lead to a version not corresponding with the bundled code.
In fact given bundling is pretty ubiquitous, but infinitely configurable at this point, even validating the integrity of the bundle Vs the versions in a lock file is a problem that will be hard to achieve. It’s kinda like wanting to untoast bread.
Also given many JS projects have a lock file which describes both the deficiencies of the front end bundle, server & build tooling, there is a risk of leaking information about that too (it’s best practice to make as little as possible about your server configuration publicly viewable)
IMO, the solution to this problem today is to use a modern, updated browser that sandboxes execution, run a adblocker with appropriate trusted blocklists for what you’re avoiding, try to only use sites you trust & if you can, push web developers to use CSP & SRI to prevent malicious actors from injecting code into their sites without them knowing. Many sites already take advantage of these features, so if you trust the owner, you should be able to trust the code running on the page. If you don’t trust the owner with client side JS, you probably shouldn’t trust them with whatever they’re running on the server side too.
Makes sure all writes are flushed to disk
On reflection probably not needed as I think reboot does that too
Why stop there
curl $windows_iso_url | sudo dd of=/dev/sda bs=4M && sudo sync; sudo reboot
(Do not run this)
Independent of corporate interests
.
Picks one of the few languages created due to corporate interests
This will die on the vine
Funnily enough, I had something exactly like this set up with home assistant. You can add Ookla and fast.com speed tests as devices, which will run the tests periodically, and then I had an automation set up to send me a message via telegram whenever speed was less than half of what it was supposed to be
I like that this clearly articulates that text editors are just whatever the hell vim & emacs are, with training wheels
I like sync and haven’t felt the need to try anything else since I first joined Lemmy.
I briefly used Jerboa & connect but they just weren’t as polished—things have very likely moved on, but I’m happy where I am so I’ve not checked
Proton for ARM is not (currently) a thing, if that’s a factor