"Its not a bug, its a feature"

Tesla has a special deal with panasonic[0], maybe they ""colab"" on the development of the batteries

[0]https://www.tesla.com/blog/panasonic-enters-supply-agreement...

Ah I looked for something more current and it seems Panasonic is operating production inside of Tesla's factory: https://www.theverge.com/2019/4/11/18305976/tesla-panasonic-...

maybe there is a "size" as in how much storage he/she has. Or maybe bandwidth issues. I do not own a large NAS nor i have fast internet for uploads and stuff, so 3,6G is a god sent.

Thats not very freedom of you

Wonderful tool! Reminds me of dbdiagram[1] we use at a project of mine, but that one is kinda slow and sometimes messes up the organization just because it felt like it.

Do you have plans on having something like export to SQL or import from SQL?

[1]https://dbdiagram.io/

Shouldn't be hard to do both things, will def. add that. Part of the plan is to switch to Tree-sitter and use other languages as well.

Yes I like dbdiagram.io and it's great that we can get something that's more flexible that works the same way.

And now they are syncing the fork lmao

This is a brilliant take.

I put a lot of though in this some time ago. So i made a python script, running on my server, that if something doesnt happen for at least 2 weeks automatic mails will go out to friends and family, each with some access to stuff they might be interested about and a final message.

I know this is a bit paranoic but its the best i can do. Also most of my passwords are on a kpdb file so with the master credentials someone could get all the access to everything (that would go to my VERY close family for example)

> if something doesnt happen for at least 2 weeks automatic mails will go out to friends and family, each with some access to stuff they might be interested about and a final message.

So that means if your server got hacked today, the hacker would have access to everything? Put differently, what I'm asking is: How exactly are you managing your credentials?

No, the 3XXXG series do not support ECC; which simply do not work. This is because the iGPU doesn't support ECC RAM.

> This is because the iGPU doesn't support ECC RAM.

What, how? The only part of the chip that touches the ECC bytes should be the memory controller itself. The reads and writes going across the internal fabric should be exactly the same.

Also the PRO versions support ECC and seem to have the same iGPU.

i have a couple:

my way of tokenizing: https://github.com/chrsBlank/Fernet_Tokenization i posted here before, i am making a social app and i dont like JWT tokenization so i made my own.

fbchatbot: https://github.com/chrsBlank/FbChatBot no longer working due to facebook api changes, i wrote that at 16yo because i could not focus on studying since i was talking to people on FB back then, this sent automatic messages and if the message contained "important" i would get a desktop notification

small toolset for various things: https://github.com/chrsBlank/autosave started as an autosaver (ctrl-S) and has more stuff implemented, i actively add more things that my coworkers ask.

Cayde,Newlight,SmartS: all projects that "started" either with friends or alone and never came to actually make them. Cayde is my personal AI that runs on a personal server (no data leaves the LAN). NewLight was gonna be an encrypted P2P messager with interesting features. SmartS would have been a "cart" for websites that could predict if the price would go down soon telling you to hold. All public on my GH: https://github.com/chrsBlank

I have a server, a small project of mine, and i installed nextcloud. Now my whole family and close friends use it to backup our photos. The official app for it is exceptional for syncing (you can set it to ONLY do the sync when charging or other parameters). There are other benefits of nextcloud (contact backup/Calendar/Messaging etc) and you can set it up on a raspberrypi with an external hard drive, throw it near your router (preferably both on a UPS for an "always on" solution) and forget about it. All the management can be done though the web interface (updates, new apps which you could find something helpful to you, etc ) and the installation is pretty easy.

If you decide to go with it, i recommend that you get a domain and set it up as a DDNS through cloudflare.

I could never bear the stress of being in charge of someone else's photo backups.

Especially when the option is just for them to pay $10 or something to a huge company that'll have pretty much 100% uptime and zero chance of lost files.

Its really not that hard. Just don't fuck around with backups, throw them all into Backblaze B2, S3 or what ever else.

I have the same setup as the person you're commenting to, initial setup was easy. Just test out your backup strategy thoroughly.

This is a proper HN reply, two counts of "just" =)

If it was a matter of "just" not fucking around and "just testing out the strategy", everyone would just resell B2/S3 capacity with a markup.

Having the only copy of someone's family photos is not a responsibility I'm willing to have. YMMV though and more power to you if you want to do that.

My preferred solution would be phone -> local backup (for safety) -> Google Photos (for convenience). If the sync to local is about as good as google this would be the best for me.

Distant Plan b: phone -> google photos -> local backup. The problem here is that the only way to get your originals out of google photos is to use google takeout which is basically a dealbreaker here.

My solution is same as your plan A. Except that local backup is a NAS that also stores all backups from computers as well as photos from phones. Then everything goes to back blaze and photos go to Google photos for convenience of sharing.