Hacker Newsnew | past | comments | ask | show | jobs | submit | mpitt's commentslogin

"Phi: A Voyage from the Brain to the Soul" by Giulio Tononi

Having just finished "On the move", Oliver Sacks' autobiography.


Interesting, from the doc[1]: "Because of various issues Invidious must be restarted often, at least once a day, ideally every hour."

[1] https://docs.invidious.io/installation/#post-install-configu...

I guess it's related to this issue, a memory leak (or probably multiple): https://github.com/iv-org/invidious/issues/1438

Also interesting that the issue is almost 3 years old and mentions even older reports.


Getting invidious to run was a gigantic pain for me. It definitely consumed all my RAM and crashed my system at least once.


It was definitely a pain in the ass before the official docker image. Have you tried that?


Thank you! I'll try the Docker image.


No problem. And I meant to mention the Docker Compose config they have here [0]. This is what I use to self-host on my Raspberry Pi, and it works great. Just make sure to add a cron job that restarts the container every hour to get around the memory leak issue (my cron job is literally /bin/docker restart <container_name>)

[0] https://docs.invidious.io/installation/#docker


As long as you aren’t hosting a public instance, the docker config in their docs should work fine. As for RAM consumption, I have set limits, so not sure if it’s actually happening.


You mean when compiling? It's normal.

There are recommendations about the memory needed for compiling.

If you do not have enough RAM just use the docker image which is already precompiled.


Odd, I have the docker image running on a cheap 4gb VPS and it's been rock solid so far (set it up about a week ago).


I don't observe this. Invidious was super easy to setup (docker-compose.yml) and I never restart. Has worked flawlessly since 2 years.


Huh, could be that the doc is outdated then. Thanks for the info, maybe I'll give it a try after all!


I verified and I did not see a drop in memory consumption after `docker compose down`. Added this to the issue you mentioned.


(2021)


Same idea: 0 calories does not mean 0 calories https://youtu.be/EN6COaYLS_A


Big "one study says" energy in most of the points here. I also think it would be more honest to write the percentage of people who chose neither of the chocolates in the same size as the other numbers.


Yep, the chocolate part almost made me stop reading the whole article. I mean, I'm happy they note the number of "not interested" at all, but they don't loose a word about it, that's a bit narrow in focus.

Also, a bit more context about the setup would be nice. Paying 13 or 14 cent is a (comparably) huge overhead when you are just walking along a walkway, with getting your purse out, seek card or coins etc. - or just take the one that is free for grabs.

On a more general note, I don't think that free stuff makes us irrational. It's just something we don't learn to deal with. When you are used to free stuff, dealing with it is pretty rational, as in looking for hidden costs, moral obligations, is it a data grab, etc. For example, when 62% of ppl refuse to take free choc because they sense they will get stupid questions in return or asked for their name and adress.


That sounds great in theory, but what happens if your dev/ops ratio is something like 15/1? How do you put an ops person in every team? I think it's the right answer but it seems impossible to put in practice.


An alternative is that all or some of the devs share the load of ops work.



[deleted]


They will use S3, but they need a CDN in front. Surprised they don't use CloudFront - maybe that's what they've failed over to.


Apparently they switched from CloudFront after determining Fastly was faster for this use case. CloudFront is focused on large streaming services, not small HTTP resources.


One of the newest kids in the block is Loki (by Grafana) [1]

We're starting to explore it in production and it's looking very promising. Much, much simpler (especially to integrate) than ELK.

[1] https://grafana.com/oss/loki/


Consent is one of the legal bases for processing personally identifiable information[1]. There are five more, among which "legitimate interest" can cover a variety of cases.

[1] https://ico.org.uk/for-organisations/guide-to-data-protectio...


Yeah, but the "legitimate interest" implies that the processing is necessary (because it override your consent). In which context and what kind of analytics is really necessary ? Analysis of the incoming channels ? Understanding if there are some technical problems ? Comparing engagement from different marketing solutions ?

I'm working on that market and find that interpretation is quite difficult as soon as you have multiple actors around the table. Example: because recommendations from DPAs are not exactly the same, then you may have different requirements of the same company from different country legal department within the UE.


One interesting thing about consent under the gdpr is that users can later withdraw consent, and if that is your only legitimate reason, then you have to get rid of all the related data. It's best if you can show that there are multiple legal bases.


jgc is not a "random" Cloudflare person ;)


My point is precisely that to me, "jgc" IS a random person. How the heck do I know who this person is.

It shouldn't matter, and it should not be required, that someone "known and important" within an organisation decides to start doing hands on tech support in social media following a PR disaster.

If "jgc" is actually someone important within this company then maybe after fixing this issue, they can then go fiox their tech support by setting up and ombudsman and get their PR disasters off the front page of HN.


It’s the CTO according to their HN profile ;)


You're missing the point. It shouldn't be necessary for someone to know who's-who in order to get things resolved.


You may be right, but knowing "who's who" is very largely how general business gets done. Buying services over the internet from an anonymous black box with no support is a recent disruption.


No, normally you didn’t have to know someone in the C suite to “get business done”. That’s totally unscalable.

What’s a recent development is the complete lack of support when shit goes south. Back when you were interacting with real reps you had people that could see when stuff was obviously wrong and escalate appropriately.


Did I say anything about C-suite? Your point is nearly word for word the same as mine, I'm not sure why you're replying as a refutation.


For a regular generic Cloudflare customer like me, for personal use, jgc is one of the random Cloudflare person. I have started a spreadsheet with his name, email, comment link, and my copy of screenshot of comment; just in case if I need to email him anything in future.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: