I'm trialling both with syncthing across multiple machines and so far no data loss but I'll make sure backups are in place!
1,887 karma · joined July 16, 2012
Aspiring mountaineer.
[ my public key: https://keybase.io/ejones; my proof: https://keybase.io/ejones/sigs/em0zaIvNe2TeZ3vgjRwX3qUC1zJEcJmUSPqaYuaVm-E ]
Founder of carbonremoved.com to make CO₂ removal accessible to everyone.
I'm trialling both with syncthing across multiple machines and so far no data loss but I'll make sure backups are in place!
For those looking for an open source alternative (or don't want to pay the Obsidian fees for professional usage) check out Logseq: https://logseq.com/
Personally if I'm building a full SPA I prefer Angular over React as I find the opinionated way takes a lot of the thinking and troubleshooting away. I've worked with large React codebases and without the opinionation they quickly devolve into spaghetti code with a multitude of libraries trying to solve the same problems just in slightly different ways.
I've tried NextJS but with each release they seem to add more complexity and the niceities that attracted me there in the first place get overshadowed by bugs and continously having to refactor because "there's a new, better way of doing things".
I'm hopeful that with the recent releases of Angular (performance; standalone components; signals being some of the main ones) will help increase popularity again but it may be that Reacts popularity keeps it on a positive spiral upward.
I really like the idea but I wish there were equivalents for Angular.
However if you want to write more logic you can also import Pocketbase as a library and extend it with hooks, custom endpoints etc. all written in Go.
Edit: Added more info about using Pocketbase with a JS SPA frontend.
Why not have a dedicated event bus (could be - but not limited to - kafka, NATS etc.) where remote systems connect to dedicated event queues? Push a message onto the queue which is picked up by the remote system.
Authentication is handled by the event bus which can also act as a storage for message (re)delivery. Partitioned by customer ID for separation of concerns etc.
Anything immediately obvious why this wouldn't be a preferred option or is it because HTTP is just easier to implement across systems?
In addition they also support optional content blocking[1] via blocklists, just set the desired TLS/HTTPS DNS server.
Long story short:
- These 'few companies' are part of the '100 companies produce 70% of emissions' statistic. This is true, but it's oil companies and governments on the list. Their emissions are driven by the demand by you - the consumer.
- Behavioral changes do matter. It normalizes (and then, in the futures, put's pressure for) sustainable behavior throughout society which is needed;
- Ebikes are great, more efficient (in terms of CO₂ emissions) than normal bikes.
- Please consider removing your flight emissions, then you'll truly appreciate the real cost of flying.Even if we covered all the possible area we could with trees we couldn't capture enough CO₂. And that ignores the fact that climate change increases the chances of wildfires.
Also worth noting that life cycle assessments take into account the gray emissions produced while sequestering CO₂ so the removal should be the net CO₂ removal (although not sure if that's the case in this article).
Regarding economics; there is plenty of olivine rock already available as a mining by-product. Disadvantages are that it takes up to 1000 years to fully sequester however this is logarithmic with a large portion of this achievable in the first century (why they mention 75 years in this article). This can be accelerated with further grinding to increase surface area.
I would imagine that regulations for net-zero will push for carbon removals to be sold similar to carbon credits have been (as net-zero can only be achieved with removals, not credits). These could either be sold as they are created annually or pre-purchased as the mineralization is a pretty sure thing to happen.
Whether this (as in CO₂ removal, not limited to enhanced rock weathering) evolves into a public service equivalent to garbage collection or a utility like water is yet to be seen.
Realistically if you have a candidate you want to hire but they are not happy with what the algorithm spits out either your baseline isn't correct for the current market situation (and therefore should be adjusted, affecting every employee), or it's not the right candidate.
The algorithm should be an accurate representation of what your company is willing to pay for an individual at a certain level.
If the candidate is not happy, fine. Can't have everything and they may be overvaluing their skillset. If the company is not happy, a single candidate should not get preferential treatment over the other employees.
I wonder why an 'algorithmic' approach to salaries is not more common.. To achieve this there must be a structured career ladder with standardised job descriptions and (most likely) a way to determine a maturity within the role itself, but then it's a case of having a base salary (often heavily influenced by where the employee is) and some multipliers. Out pops a number (or a tight range) and the employee can choose if they take it based on their valuation of their skills. No risk of gender bias and it takes away a lot of the pain of negotiating salaries felt by both management and subordinates.
Regularly reviewing the base numbers to adapt for inflation and market trends will ensure that both new and existing employees are treated fairly.
At my previous position (head of engineering at an old school sales house trying to become more engineering friendly) we had great success bringing in a structured approach to growth and a corresponding salary calculator. Unfortunately the salary numbers were reserved for management as it wasn't rolled out across the whole organisation but it inspired other, non-engineering, departments to adopt a similar pattern. My vision would be to have these figures open company-wide however I understand that in most medium-large companies this is a time-consuming process.
As someone starting a business today I want to ensure that salaries are open (definitely within the company but likely to the world) from the beginning. Employees should feel comfortable knowing that they are compensated fairly for both the work they do and in comparison to others.
If anybody is looking for some open inspiration about how this is done, check out Buffer[0] and PostHog[1] (Gitlab[2] have one too but the numbers are not open).
- [0] https://buffer.com/salary-calculator/software-engineer-ii/high
- [1] https://posthog.com/handbook/people/compensation
- [2] https://about.gitlab.com/handbook/total-rewards/compensation/compensation-calculator/Worth noting that most of these bots are 'good bots' (i.e. they will obey robots.txt). So you can avoid the nginx resource usage entirely by adding suitable robots.txt entries.
I think using nginx tests like this could have negative effects on showing OpenGraph metadata (including images).
If choosing this approach however I would probably respond with a 403 code to mark forbidden as bots are more likely to continue making attempts if they think the server would come back online.
Continuing the DACS example, they are not issuing 'carbon credits' that are verified by Verra or Gold Standard. There is no existing standard for verifying removals.
I would say the majority of the CDR industry is trying to distance themselves from the term 'credit' as it implies a 1:1 relationship however reductions and removals just can't be seen as the same.
However more often than not they are indeed "a scam". Credits have been around since the 70's and have had questionable impact on the growing climate crisis.
If I were a benevolent dictator of a nation, I would take the following approach:
- Start with the legal requirement for every business to understand their Scope-1 and Scope-2 emissions. Scope-3 will need to also be understood in the future to ensure no loopholes but that's much easier when the supply chain understands their scopes 1&2;
- Set a net-zero target for all businesses that requires overall emissions reductions and leverages carbon removal for any avoidable emissions;
- Treat emissions accounting the same way as financial accounting, requiring annual submission to the state and penalizing fraud/mis-representation;
- Offer tax incentives for carbon credits however set stricter standards (credits must have a certain amount additionality and/or be demonstrating help to reduce emissions of other businesses within this imginary nation);
- Carbon credits cannot be used to reach the net-zero targets set above;
- Future goals/incentives can encourage businesses to
The overall aim is to highlight the hidden costs of unsustainable practices, effecitvely eliminating the green premium that currently exists for more sustainable products/services. Companies should then prefer cleaner practices and suppliers to keep their own costs down which accelerates the fly wheel towards a sustainable future.Now of course there are issues (e.g. the supply of CDR is small and expensive or the availability of clean energy) with this approach, however nations can help encourage development here (e.g. with the IRA) as well as private investors. Then of course there is the consumer society to contend with who wants lots of cheap produce but that's why the "dictator" part...
"carbon credits" are the most common, cheap, questionable credits from verifiers such as Verra and Gold Standard.
"CDR" is "carbon dioxide removal" which actively sucks and stores CO2 from the atmosphere. This is an emerging space pioneered in the private markets by companies such as Stripe, Microsoft and Shopify and the Frontier fund.
This article mentions "CDR credits" (and is on a website "carboncredits.com") and the partner Aspiration is slim on the details on their website.
As far as I can gather, Meta has purchased 7M of traditional, nature (i.e. planting trees) "carbon credits" and the role of Aspiration is to use "satellite imagery", "AI" and measurements to monitor the progress of this growth.
It is worth noting that Meta is also a participant in the Frontier CDR fund that is helping stimulate the negative emissions market.
My two cents on this: I think nature based solutions have an important role to play in restoring ecosystems and sequestering carbon. However I'm skeptical of the need to invest so much in the monitoring & verification of the vegetation growth. It feels this is mostly for companies to feel they are getting something for their money rather than trusting organisations to help nature. Instead it would be a better use to turn these technological monitoring solutions on to finding deforestation and ecological damage to limit that.
It was a refreshing approach rather than tracking down logic scattered between models, views, managers etc.
For very simple projects it can add a bit of bloat/boilerplate but as complexity grows it's great to have reusable selectors & service functions to use.
Removals often have a LCA that takes into account any emissions produced during the process and sells active CO₂ removal.
It looks like this offers more of a web approach without the need for a local install so it can be a bit more collaborative.
Also - and this is personal preference - the GNUCash UI feels quite dated.
Curious about the carbon positive aspect of this though? Where to the emissions come from? Are the trees your planting for fuel or something else?
Second - it was on our original roadmap to try and bring in a standard for removals however as a for-profit this was generally received poorly. We fully support some form of indepedent third party validation for carbon removal that addresses the flaws in the existing credits system but I'm afraid this isn't our primary priority at the moment. Perhaps we could form a non-profit sister to address this in the future though...