oarsinsync

Check AliExpress. Much cheaper for N100s.

Portability is secondary for me. For me, the primary reason for keeping content in plain text is disaster recovery.

When my systems are down, when my applications aren’t working, if my documentation is also inaccessible, this makes things a lot harder.

If my documentation is primarily in plain text / markdown, it’s really easy to be able to read those docs again, even when everything else has fallen over.

  ./configure —-prefix=/home/user/appname
  make
  make install

https://github.com/Linbreux/wikmd

I can’t remember why I switched from gollum to wikmd. I suspect installed size might be why.

Agreed. Also consider that shared hosting packages are very much providers scraping the bottom of the barrel for some marginal extra revenue. Shared hosting customers are not the highest priority of customers, unless your entire business is based around shared hosting (in which case, you are likely operating as amateur hour anyway)

It's pretty detrimental to relationships when one side pre-declares their rules and policies, and then arbitrarily decides to ignore them.

I'd say they have a lot of incentive to behave in whatever way their published policies state, regardless of the impact to users of the cctld.

(I don't know what the policies are)

Does Google search become a paid subscription product in your vision of separation of search vs ads?

I suspect the point of this article isn’t meant to be a Linux 101 guide, but rather, specifically about their learnings with how to go about colocating a linux server.

> But perhaps I want too much, the title does include the word "terrible," after all.

To be fair, it’s not actually a particularly good guide to how to go about getting your first colo server setup either, which aligns with their title about it being terrible.

The Mac is the exception in their current product lineup: every other platform is heavily locked down, and the user’s behaviour heavily restricted.

I strongly believe the Mac is heading in the same direction. See the progression from run what you want, to optional signing of binaries, to right click to run unsigned things, to disable a setting to be able to run unsigned binaries; or “worse”, the way spctl and csrutil no longer function after deploying Sequoia.

Unfortunately, Diarium also reduces image quality significantly, even with their ‘higher quality’ setting. My Day One diary export is 90% larger than the data store Diarium syncs to webdav, the loss of fidelity is especially obvious when looking at screenshots.

For the tax to be equally effective on rich as poor, the tax might need to be means tested. A £100 tax disproportionately affects poor people over rich people.

I was definitely hurting for a while for lack of this (and iMessage) on Windows. While I haven’t gotten over iMessage (and use a KVM with my iPad to resolve that), the additional friction for payments has actually been a boon for my bank account.

The more friction we feel with payments, the fewer payments we make. Cash is higher friction than cards. Manual card input is higher friction than password manager autocomplete. Autocomplete is higher friction than apple pay. I haven’t found anything lower friction than apple pay.

By switching back to password manager autocomplete (which is unreliable at best), I’ve found my spending has gone down, because the cost of friction in payment is higher than the value of the item.

(I clearly also have too much disposable income, but that’s a whole other tangent)

Until you decide to optimise for resources, and do crazy things like “one postgres instance, one influxdb instance” instead of “one instance per microservice”, and then you get back into hell pretty quick.

Winds me up how massive tiny applications become, and how my choices are to throw money (RAM) at the problem, or money (time) at the problem. I wonder when someone will do the math and prove that developer laziness is having a substantial drag on global efficiency. The aggregate cost bourn by users has to be orders of magnitude larger than the cost savings made by developers at this point.

I’m unaware of any open source license that prevents an author from walking away, ever? GPLv3 has no warranty or liability?

I guess you meant something with “and more”, but that sounds like a mismatch of expectations of what a user of open source might want, vs what is required of an author of open source?

I then booted into a new fresh clean debian environment, mounted my disks, and:

  cd /opt/docker/configs; for i in *; do cd $i; docker-compose up -d; cd ..; done

Sure, I have a new set of problems, but they feel smaller.

Thank you!

If I’m understanding this correctly:

1. You buy 1MW of solar power in location X, and don’t use it.

2. You sell 1MW of emissions producing power in location X, that someone else uses

3. You buy 1MW of emissions producing power in location Y, and use that.

Net result: 2MW of emissions producing power used, 0MW of solar power used, and a claim of net-0MW of emissions produced?

Yes, it’s a “clever hack”, but accounting sleight of hands are just that. Most charitably magic, less charitably outright falsehoods.

> IMO it's a fair and good hack: When you open a new site and use that hack to buy power for the new site, the corresponding new power generation is solar. It's just solar with two additional accounting hops

I don’t understand how you got to this outcome from the first position. Can you help me understand what steps I missed for this to actually have good outcomes resulting in solar power actually being used?

I’d love to be wrong and for this to actually be actually good outcomes combined with clever accounting - those are absolutely the most satisfying solutions, both to design and read about (for me personally, anyway): where clever people are coming up with creative solutions to solve bureaucratic bullshit, while also achieving good outcomes.

EDIT: Child comment has helped me spot the error in my comprehension leading to incorrect math: “ What you do is buy 1GW of solar in Kansas, sell that same power as fossil power in Kansas” - I didn’t read ‘same power’ properly in my first read. I’ve left my comment as-is despite it now being completely wrong as a result of that, and glad to have been wrong

This isn’t fair to yourself, or anyone else reading this and feeling the same way.

There’s a difference between good parenting, bad parenting, and abusive parenting. Just because your parents weren’t abusive, doesn’t mean they were good at instilling all the useful and/or important values in you.

Also, there’s a difference between blaming your parents for who you are, blaming yourself for who you are, and accepting that things have happened, learning from them, and using it as the basis for growth.

Consider how old you are today. Consider what age your parents were during your formative years. The closer you get to being the same age your parents were, the easier I think it gets to recognise that your parents might have been much like you are: imperfect beings trying whatever resembled their best on any given day.

Ultimately, try to be kind to be kind to yourself, but also be accountable to yourself. Kind accountability tends to work better than blunt brute harshness (just like you catch more flies with honey…)

The mainstream media outlets dont really change hands often. The vast majority of people are already subject to the whims and biases of said media organisations. More information being available is unlikely to change that. We already can't parse the amount of information available today.

You can access crontab, /etc/rc.local, init scripts, and add custom paths to be included in openwrt managed backups and restores.

It's reasonably flexible in enabling power users, rather than working against you.

In Comments

Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.

Comments should get more thoughtful and substantive, not less, as a topic gets more divisive.

Please don't fulminate. Please don't sneer, including at the rest of the community.

Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.