You could find out about the way we do it at https://github.com/madnificent/docker-ember but I would not if I were you.
The real risk, today at least, does not seem utterly huge. Jumping in this rabbit hole of containers is another topic in itself. I suggest continuing your learning as you do now and maybe revisit this later. You will learn faster that way.
Feel free to check what we did on the link above and ask questions later or whenever you feel ready for this topic.
You shouldn’t eat candy given to you by strangers. If you’re in a large group and someone knows the candy, maybe. Code is food for your computer. Be wary. Our large Open Source group of friends has learned about many kinds of candy and shouts loudly when some in the group becomes ill. You don’t want to become ill. Some risk exists, but with a large group it is generally ok. Don’t install packages as root, don’t install what you don’t need.
I run my frontend builds through Docker (also during development). By isolating access to the host system to the files/folders necessary for development I’ve shielded off the majority of current realistic attacks I’ve seen as NPM based exploits. I’m certain the approach can be replicated for other frameworks, but we use Ember and docker-ember. I doubt it runs as smoothly on a non-Linux OS.
I had to read the overview and it looks nice. It reads like IPFS without some of the challenging cruft. Well written!
IPFS seemingly works small scale but not large scale. What makes tenfingers handle millions of files and petabytes of data better than IPFS? Perhaps that is not the goal. In what way do you think the tech scales? Why will discovery of the node which has the data be short?
I want to ask for benchmarks but you can’t do a full benchmark without loads of resources.
I’m not actively looking but please do share references! Other people may read this and they may want to know too. Perhaps I’ll jump back in the rabbit hole at some point too 😁
Exactly. The Semantic Web is broader than Solid but Solid is great for personal apps.
Say you buy a smartphone. The specifications of the smartphone likely belong elsewhere than in a Solid Personal Online Datastore, but they can be pulled in from semantic data on the product website. Your own proof of purchase is a great candidate for a Solid POD, as is the trace of any repairs made to it.
These technologies are great to cross the barriers between applications. If we’d embrace this, it would be trivial to find the screen protector matching your exact smartphone because we’d have an identifier to discover its type and specifications. Heck, any product search would be easier if you could combine sources and compare with what you already have.
The sharing tech exists. Building apps works also. Interpreting the information without building a dedicated interface seems lacking for laymen.
IPFS would replace Content Delivery Networks in present day.
It would also allow you to host software and other content from your own network again without the constraints modern Internet Service Providers pose on you to limit your self-hosting capabilities.
If applications are built for it, it could serve as live storage for your applications too.
We ran ipf-search. In one of the experiments we could show that a distributed search index on ipfs-search, accessible through JavaScript is likely feasible with the necessary research. Parts of the index would automatically be hosted by clients who used the index thus creating a fairly resilient system.
Too bad IPFS couldn’t get over the technical hurdles of limiting connection setup time. We could get a fast (ElasticSearch based) index running and hosted over common web technologies, but fetching content from IPFS directly was generally rather slow.
The semantic web and social linked data. We could have applications share data without depending on big tech, but rather based on application standards.
It can be used today and gains traction but I wouldn’t mind it going faster. Especially the interoperable personal app space could use some love and attention.
I write my notes in org-mode. It’s supported in many editors in a basic form, letting you add code snippets etc in an unobtrusive way. Using a well thought out format helps you in the long run.
I use this in Emacs, through which it lets me refer to emails, execute code snippets, attach related files, fetch content on/from remote servers, send off the debug session as an html email, … Support will depend on your editor but even as raw text it works.
I don’t use something specific to make non-code repeatable as you suggest here, but you could embed a test language in an org code block.
The syntax is straight-forward and exports to multiple external formats exist (eg: html).
https://github.com/mu-semtech/sparql-parser contains an EBNF parser for SPARQL, an LL(1) language. You might be able to borrow code, not sure how well it translates to scheme. GitHub asked me to log in to see the gist so I’d have to have a peek later.
sparql-ast folder contains the relevant bits regarding the parsing.
Depends on how much the old banger is driven. The tipping point is much earlier than I expected.
https://www.youtube.com/watch?v=6RhtiPefVzM
I’d love to drive the old bangers more though. The rumbling sounds and the hope it’ll keep up as the engine gets pushed beyond reasonable limits before the inevitable gear change. The whistling turbo as you reach its zone and the gently ticking valves of a cold engine. But turns out gas guzzling fun was never going to be a lasting treat in our habitat. As I write this, our neighbourhood has a reasonable chance of getting flooded because of the strange weather lately, and I am glad I’ve grown to appreciate the lovely hum of our electric minibus.
We need to travel less and enjoy it longer. Much much less. Every region is different. Our region has good public transport if you accept cycling for 30 minutes. Traveling 100km for work daily is bad for the environment. So we mostly need a culture change here. And people who lack the funds seem to care even more for cars here so we need cheap electric cool econoboxes with too, I guess.
Kubernetetes is crazy complex when comparing to docker-compose. It is built to solve scaling problems us self-hosters don’t have.
First learn a few docker commands, set some environment variables, mount some volumes, publish a port. Then learn docker-compose.
Tutorials are plenty, if those from docker.com still exist they’re likely still sufficient.
With that explanation I am still not clear whether the statistic on percentage of recycled batteries was car batteries, the battery industry as a whole, li-ion batteries, rechargeable batteries, … I am honestly interested in which statistics you are referring to. Especially the evolution of recycling of car batteries and the regions where recycling and collection occurs.
It seems you are adding uncertainty and doubt on the topic of battery recycling which I’m not sure is grounded. We are well past the point in our environment where we can live our current lifestyle in the way we live it today. We have to adapt to a different lifestyle and make strategic bets. It seems clear that we should stop pumping up oil and electric cars may help there. I’m looking for research that indicates that current car batteries are waiting in stockpiles to be recycled but no plants exist to recycle them.
As far as I can tell, there are not even enough bad battery packs around to suit the diy hackers to reuse them for home energy storage and with some luck your research points me to where I can find them.
Are you talking about Li-ion batteries in general, or car batteries?
I don’t think there are many car batteries to be recycled yet. Only the Leaf’s batteries degraded sufficiently to warrant replacement and even those seem to be used with shorter range. Tesla batteries with faults get refurbished IIUC. The ev conversion market likes to use second hand packs and prices are strong because there are too few.
I have read that recycling is feasible and realistic but did not bother to check. Can you point to the research that says it is hard and that the batreries will serve no future use as is?
The sentiment I hear around me is that you have been lied to.
We have kept the lights on, like many of you asked, and we are looking forward to welcoming a new humorous generation.
Sure, it is not going to be under the same conditions. Things have moved around when you left. Empty voids have been filled. Regardless, I’d love for us to see the propaganda of the time for what it was, propaganda and lies, and to bring the actors and platforms responsible for willingly spreading lies to their knees.
Together we stand stronger in a strong Europe, and reuniting is a sign of Europe’s resilience to external influences.
My whole work environment is tightly integrated ensuring I can use the same tools nearly everywhere. Things like keybindings (deleting a sentence, spellchecking a region, multiple cursors), macro’s (ad-hoc repetitive command sequences), the consistent mostly text-based visual look & feel. All of this lowers the cognitive load.
Comparing to an IDE, Emacs is more of a hyper-configurable integrated work environment. In my case, my code editor (Emacs), my knowledge base (org-roam), my tasks manager (ad-hoc on top of org-mode), my email client (mu4e), my tiling window manager (exwm), interaction with git (magit) and git issues and PRs (forge) as well as some other tools are controlled from Emacs. I call them ‘my’ because they’re sometimes slightly modified to scratch my own itches. I could integrate my calendar but Google’s webdav APIs seemed flaky at the time and FireFox only gets some consistent keybindings.
Just a few more years and Emacs will turn 50 years old. You never know what the future will bring but there’s a reasonable chance I will not have to throw away what I have learned so far.
Some examples of this integration:
M-x develop-projectname command that boots up the application, arranges my windows with the right folders open, backend and frontends started, and a place for FireFox (not integrated, only uses some of the same keybindings)If you want to come to the dark side and like VIm’s keybindings, you may want to use Emacs’s evil-mode and keep them. It might just be the best of both worlds.
I am waiting for federation to land. Would love to give it a spin and see how smooth that works across instances.
Looks good to me.
docker-ember largely automates such a setup with specific mounts for linking node modules from other folders, being able to bind to localhost for when you run the backend on your own machine, and exposing ports for livereload. May include other secret sauce. Some of that is closely tied to EmberJS.
I’m a fan of using tools you understand. What you show here is comprehensible and sufficient for now👌