Where it does store the metadata or database info ?
In the NextCloud instance somewhere.
Readit NewsZeWaren commented on My ridiculously robust photo management system (Immich edition) jaisenmathai.com/articles... · Posted by u/jmathai
ZeWaren commented on My ridiculously robust photo management system (Immich edition) jaisenmathai.com/articles... · Posted by u/jmathai
Habe you tried nextcloud + memories app?
Every metadata is stored in EXIF and the directory structure on disk defines the directory structure in the app (and vice versa).
When you want to move your tooling or just do things manual again, grab the disk and your are ready.
I'm very happy with Memories.
I store my pictures on a NAS jail. That directory is mounted read-only on another jail with NC and Memories. I like the guarantee that my gallery app cannot alter my files.
Also, many gallery apps don't allow browsing a directory tree. You have one level of "albums" and that's it. Memories support it. I have pictures 5-6 directories deep, following a system that makes sense to me.
With all due respect - I totally understand you may need a rooted phone, I’m just curious what you use it for? I’ve never had a modified or rooted phone so I don’t know of any of the reasons you might need one.
I want to backup my entire phone on a local server I own. Apps, app data, settings, WiFi passwords, call logs, etc. Good luck without root.
Wireguard is cool, but there's some reasons it's worth considering OpenVPN (why I still use OpenVPN anyways). First, OpenVPN has kernel mode now (called DCO, which I think Netgate maybe has upstreamed to FreeBSD); I've found it's performance on hardware with AES-NI on Linux is actually often better than wireguard. Second, there's a lot of quality of life things that just work on OpenVPN that you've got to use a ton of duct tape to make work with Wireguard, a major one being handling DNS record change (think especially dynamic DNS, which is likely if this is IPv4 and a residential connection). This is a huge pain with Wireguard, but just works on OpenVPN. Similarly if you have multiple WAN links, like I do, for OpenVPN it's just two connection stanzas and it largely just works. Again for Wireguard you're adding lots of duct tape to make it work right. I know Wireguard is the new hot thing, but it leaves a lot to be desired in the resiliency and features department.
I use wireguard as my main VPN to connect to my homelab from my phone and my laptops.
I also have an OpenVPN as a backup option, running behind sslh. My same port on my router (443) serves both a webserver hosting photos, and that OpenVPN instance. This allows me to VPN into my home in most firewalled office networks.
I wonder if it also happens to people with aphantasia, who are unable to visualize things in their head.
ZeWaren commented on I tried every todo app and ended up with a .txt file al3rez.com/todo-txt-journ... · Posted by u/al3rez
My requirements were:
- ability to sync the TODO lists between devices (web and android).
- ability to have sub-items, so that I can organise my complex lists into magnificent trees of tasks. I sometimes have 5 levels of details on some travel checklists.
- ability to handle periodic tasks, and ability to create a task and hide it until a specific date (topics for my future self)
- ability to be self-hosted.
I'm now using Vikunja, and Tasks.org for the Android side. That setup has worked for me wonderfully for a couple years now. Vikunja has a ton of features I don't use, and that's fine. They don't get in the way.
ZeWaren commented on Graphene OS: a security-enhanced Android build lwn.net/SubscriberLink/10... · Posted by u/madars
ZeWaren commented on KOReader: Open-Source eBook Reader github.com/koreader/korea... · Posted by u/charleshan
I manage my ebooks using a self-hosted instance of calibre-web.
This allows me to sync my library to my Kobo e-reader using KOreader.
Also, turning pages is faster than with the stock reader of the device.
ZeWaren commented on Why blog if nobody reads it? andysblog.uk/why-blog-if-... · Posted by u/alexgiann
I document technical things on my blog and hardly anyone reads it.
But later on when I need that thing again, I just go there and I have the perfect documentation available for the topic (it's perfect since I wrote it hahaha).
The way I've seen OKRs work so far was always the same:
Top management defines a strategy for the company.
Each department (commercial, marketing, product, etc.) create department OKRs from the company OKRs.
The year/term starts.
Each department comes to the implementation teams (product, IT, BI, support, etc.) with a HUGE list of poorly defined objectives or tasks.
The implementation teams only have limited capacity and can only deliver maybe 15-20% of what everyone wants. No one actually thought of checking if the objectives have any reasonable possibility of being delivered at all during the term.
Optional drama to decide what's going to be actually worked on might happen.
When the term ends, and if communication isn't a disaster between the departments, some MVPs are delivered.
A new term starts, and either the previous objectives are continued, or they're simply forgotten in favor of new ones.
Rinse and repeat.
edit: formatting and typo.