The documentation itself is so full of implementation details that, as someone who is interested in the concept of this, I'm scared off even trying to setup and use this
The project would be much more approachable if there was a simple native installer. My parents could also benefit from this but there's no way they would ever even understand how to install this, much less troubleshoot docker things.
You might want Recoll[1]. Similar if less powerful capabilities, cross-platform, open source, has Windows and macOS installers.
Still an overly complex FOSS user interface for a tech-unsavvy target with lots of digging around to configure it (OCR setup, for instance[2]), but at least you don't need to know what Docker is to install it.
It's a bit rich calling it insane just because it's not immediately approachable for you. Not every project is aiming for mass-adoption and if you want to lower the barriers, that's on you to make happen.
Consider pitching in time/money there (if welcome) instead of complaining when not everything is served to you on a silver platter.
A sqlite backend would be another thing that could reduce the complexity for a minimal OoB setup, I guess.
Truth the told, I wouldn't find it unfair to call the architecture/setup "insane". This is not one. If you've done any meaningful self-hosting in the past decade, it's as straightforward as it can be.
Self-hosting services usually entails more technical knowledge than just installing an app and I don't think a document management system would necessarily work well as a native application. For starters, there's the backup issue and you wouldn't want non-technical people to store important documents that only live on a local drive. Remote web access is also a very useful feature for when travelling and that wouldn't be easy to setup for a local install.
I've been using it for over a year and am very happy with it, though I intend on moving it from my home Pi docker swarm onto a free Oracle cloud instance to improve the performance and uptime (I've got my Pis auto updating and rebooting, so services get shunted around fairly often).
The project would be much more approachable if there was a simple native installer
Actually the very first example on https://docs.paperless-ngx.com/setup lists an interactive installer which asks the user some question and eventually arrives at a working docker-compose setup.
If you ask me, this is already pretty user friendly. Although I agree that if your needs are more involved, there is some reading you'll have to do.
I am currently in the process of migrating from mayan-edms to paperless-ngx and it feels pretty approachable to me if you know your way around docker (compose).
I wasn't particularly overweight before but I attribute about ~10lbs of weight loss this year to realizing that:
- When at a dinner with family or friends, I never _have_ to finish something. Most of the time the host will be happy to package my leftovers to take back home when asked. That last part makes it clear that I like and appreciate the food even through I didn't finish it in the moment.
- If I buy food at a restaurant, I don't have an obligation to finish it to get my moneys worth. And again, I can just save it for another meal if I want.
- I don't have to eat snacks just because the host put them on a table at a party.
For some reason our brains think that just because food is _there_ we need to eat it, but that's generally not true.
I don’t actually think temperance and logic like this moves the needle significantly for obese people. When you’re obese you need to lose 50, 70, 100+ lbs, not 10. You’re looking at fundamentally changing relationship with food at multiple levels to the point where it’s unrecognizable. I don’t think small changes in habit like this are in the same ballpark as what obese people need to become a normal weight, in the same way that I don’t think taking the stairs instead of the elevator is in the same ballpark as someone who wants to become a professional athlete.
> When you’re obese you need to lose 50, 70, 100+ lbs, not 10.
You have to lose 10 at some point. The way you're putting it, it looks like losing weight would be some kind of drastic sprint with a finish line. I don't think it can happen that way. You have to lose weight and continuing changing your habit to lose 10 more, and the others 10 after, until it stabilises at healthy weight, then you start your healthy life, but it's not a finish line, the effort continues by fighting unhealthy habit for the rest of your life.
I don't think anyone is suggesting that the same tricks will work for everyone. I've never been chronically obese so I wouldn't know what goes on in someone's mind at that point.
However I do know that it moved the needle significantly in _my_ life by changing my relationship with food so it's valuable to me. Losing the extra ~10 to 20 lbs of weight people gain in adulthood is something that people do struggle with even if it's not as dramatic as someone fighting obesity.
I've seen a handful people close to me go from 100lb+ overweight to a more comfortable 10 to 20 (or 50). And I think what GP described is a fundamental change to the relationship with food: You're (consciously at first) changing the definition of what needs to be consumed vs what is being consumed without need. They've all from what I've observed gone through this change.
They said that when you're really big, the first 10 lbs is the easiest to lose, and can come from taking stairs and changing snack habits. It's the last 10 lbs that requires the diligent workouts and very strict diets.
Indeed, walking punches way over expectations for keeping weight off. You have to do a good hour of a walk, but an hour walking is probably better than a rushed workout of similar time.
Good on you! Something I preach to my children is that success comes from showing up every day to do a little and not from a sudden burst of a lot. Well done.
I turn 50 this year and have committed to doing 50,000 pushups before 2024. It sounds like a lot, but after the first month, doing 200-300 a day isn't really that difficult (when broken up into smaller sets). Honestly, it's a LOT more of a mental challenge than a physical challenge.
Sunk cost fallacy. You aren't getting that $7.50 back. The question should actually be "do I want to, for no reason at all, feel like shit for the rest of the evening?"
(This assumes you aren't deriving any pleasure or utility from eating that last 25%. If you are, then that's one side of the cost/benefit analysis. But the initial cost of the food is irrelevant not matter what.)
Yeah. I suppose sunk cost fallacy here would be "I should eat it all to avoid wasting money." I guess you're sort of actually psychologizing OUT of that. It's still a bit fallacious, since the correct cost of the decision to not eat is actually $0, not $7.50, but I guess lying to yourself about that could be a useful mental trick.
Indeed. I doubt anyone ever got fat by eating food they didn't like.
The issue becomes all the worse when food is designed to make you want to keep on eating. Bonus points for it giving you that sort of hunger-like feeling 2 hours after your meal.
I realize everyone has different dietary needs, so I'm not saying this is for everyone, but it's very, very rare for me to finish a meal at a restaurant in one sitting. I used to, but leaving and feeling stuffed got old.
I've found if I stop early, it turns out it was only my brain that wanted more food. Physically, I've had enough and am satisfied. I just need to give my brain time to catch up to my body.
Additionally, I drink a lot of water with my meals. This helps prevent overeating.
Lastly, it's always great to get two meals (dinner and tomorrow's lunch) from one restaurant dinner.
And in general it's easier to have the snacks simply not be there, than to try to resist eating them. The habit of having random food and snacks lying around the house for 'just in case' is not a good one if you care about your health or weight. Unless of course you are actually required to eat frequently due to medical conditions.
- The return type makes it clear it can return an error
- The return value is typed in a way that makes it clear what the ownership is
Throw in a language like Rust that gives guarantees about thread safety and now the only thing left is if the API is stable or not. Which I would argue doesn't matter much at all since people will still end up depending on it regardless of the comment saying "This API might not be stable"
And the best part? My definition will never get outdated. If the assumptions change, the definition will also need to change (well, except for maybe the name)
You are absolutely right, and one should prefer languages that can give such guarantees wherever possible.
But often one doesn't have a choice. People still write software in inferior languages such as Javascript or Python, where you cannot even be sure about a return or parameter data type.
Typing this using the extension. I like it, through I think one of the reasons I like browsing HN is that the website is intentionally very simple / I don't have to think around navigation at all (everything is very linear, I click something I get a page reload with the thing I'm expecting). This adds just a bit more cognitive load around navigating.
I'll keep using it for a bit to give it a fair shot however since I can imagine the split pane being super useful in certain cases.
Same thoughts here. I think it's great that people can make extensions and apps for new and varied experiences, but the current HN is dang near perfect IMHO. Simple, intuitive, fast, does what you expect it to do. Nothing less nothing more. It's reached its final form for me. Everything else is fan fiction.
One thing I noticed is that pressing `edit` does not let me edit anymore. It just opens my post on the left pane (and still isn't in edit mode) so my only option to add this feedback is to reply to myself :)
You don't 'see' the problems unless you know what to look for. One sign is that the spinner in the top left corner doesn't end. Check the console for errors too.
The primary issue is that the DOM parsing fails due to changes in the HTML structure and the extension throws NPE's.
I've been collecting thoughts on the next generation extension to make for HN. Hopefully when I have a bit more time (in the middle of a giant home remodel), I'll find some time to implement it. One core thought that I really enjoy about this extension is that it doesn't really change the UI/UX at all, it just refines it. I think that is important.
If you can never assume that any 2 concepts are distinct from each other, how do you model your database? I'd be curious how you would model the example you stated as a relational database that mimics how humans think
Could this be in the opposite direction, where the richer you are, the less you need to work?