Hey thanks for the detailed explanations.

Regarding SSO my concern is not the ChartDB team having my email, that I was planning to give anyway, but SSO provider knowing I’m using this tool. It’s a personal paranoia than anything else. I know it’s much safer and easier to have 3rd party SSO than managing your own authentication service. Done that, hated it. So not really that annoyed about it.

The Mac only part really annoyed me to the core. Then I received an email telling about Buckle, which amplified it. I think the problem is you advertise it as ‘ChartDB 2.0’ and then suddenly it becomes ‘Buckle’. I can understand the thought process behind such presentations, but really don’t like it. TBH I would not be this mad if a similar tactic was used by a large corporation. But being an open source tool I have some ethical issues with these practices.

Again, I know these are just some inconveniences, and not a scandal. So not really complaining, but just sharing how I felt. Apologies if that has been rude.

I have some critical comments not about the tool, but about another related stuff. Please look at the next section for doubts and suggestions.

The tool need to be more clear and less annoying about ChartDB v2.0.

So this is shown as some big rework, so I signed up. Only then it said only MacOS would support it initially. This was a huge disappointment and I felt kind of deceived into giving my email id I don’t remember seeing it’s only mac at the beginning on the sign up page. May be I missed.

Another thing is it looks like a different product altogether with the name ‘Buckle’. Again I didn’t see it in the sign up section. Why a new product name? Are you switching to freemium model?

Last but most importantly, why does a third party sign up for it? If you just want to inform the user when things are ready, just take the email and use it. No need to have access to my Google or GitHub account.

Apart from this terrible experience, I love the tool and how it visualises it.

I have a doubt. When I visualised my postgres db it also showed the views I had, apart from the tables. But I could not find an option to add a new view from the interface, so that I can use it as a more capable design tool. Is it a feature in the pipeline?

Also I could not find an option to set the length of Type: varchar. I remember seeing this feature in other design tools.

Sorry for the delay. I got busy. I’m not entirely sure this is a dynamic registration issue. Your screenshot points to something like a permission issue. This is a bit wild guess with very limited information.

Do you have any info saved when you attempted to register the client manually and use client id and secret?

I will try to do some tests when I get to my setup. Do ping me if you have any updates.

Oh, so no separate config is used and only env variables I guess. Is it possible for you to get the URL your app is requesting? If yes, please share a sample.

Also double check the realm name. I assume you created a new realm for your use and not using master.

Hi, I have some experience with Keycloak. So I assume you explicitly enabled you are using OIDC dynamic registration.

Can you share the config file after redacting sensitive contents?

Oh, never heard of amnezia. Never needed actually. But it looks like a good improvement on Wireguard. I will need a separate setup to test it out and currently I’m away from home with no clue when I will return. If I happen to find anything, I will definitely ping you.

In the HN page you linked many people mentioned v2ray. Have you tried that? How good is it?

Have you considered having Headscale on a cheap VPS? We are actually doing that and it is pretty capable. IIRC, you can configure not to use the tailscale servers at all, and use your own public VPS for coordination. Bonus point, tailscale hired the Headscale developer and maintainer, and they are allowed to work on Headscale while on their payroll. The team looks very much into FOSS.

The exact setup can be achieved by tailscale, a not really known feature is you can point your domain to the, tailscale IP (new ip assigned by tailscale), and it will act just like a normal hosting setup.

Advantage, any device or someone who you do not pre approve can’t see anything if they go to the domain and subdomain. They only work if you are connected and authenticated to tailscale network. I have a similar setup, if you need more pointers please ping me.

RustDesk

If you have used AnyDesk in the past, this gives the same experience. Recently used it and has a lot of features, including unattended access.

They recommend self hosting an instance for better performance.

One thing you can try out, if you haven’t done already, is configuring 2 different ports for the two users here. GUI has an option to adjust the ports, also you can configure two different services to start depending on the logged in user. I haven’t done it myself on Linux, but it looks like people had success. One R*ddit thread for example,

Syncthing on a multi user Computer

IP should not cause any issues. IDs are just a hash of certificate used by Syncthing. Can you elaborate a little on the current setup? Device, OS, User, etc. Also if possible can you explain your use case? As I mentioned, Syncthing is very specific to what it can do, so it may not be the best solution for your case.

Oh forgot to add that the last case that you mentioned, where multiple users sharing a PC, and keeping the folder in sync with all, is not straightforward. This needs another always-on (server like) device.

At least in Windows each user gets a different Syncthing ID. So if you sync the file with an always-on device, the other user can get the update when they come online from that.

Here one crucial element that needs to be highlighted is Syncthing is decentralised by design. I mean it is different from a server-client way of thinking. It is very much like how git stores content, if you are familiar with it.

For example, let us say I have 5 devices and there is a folder I want in all my devices kept in sync. Since there is no server, to propagate updates made in one device (let us call it Source Device) to other devices, it has to happen either directly, or indirectly. Here I’m assuming all 5 devices are configured to communicate with each other directly.

Whenever one of the other 4 devices (Device 1) becomes ‘online’ at the same time as of Source Device, the sync will happen. This is the direct way. The indirect one is, let us say after the sync happened between Source Device and Device 1, the Source Device goes ‘offline’, but the Device 1 continues to be ‘online’, now if Device 2 comes online, the change will be propagated from Device 1 to Device 2.

Note that the assumption, one device configired with all other devices is not the case, propagation of change has to take a path that similar to indirect way, even if all the devices are simultaneously online.

This configuration, where each device is configured to communicate with all other, is a pain to maintain, since Syncthing is not designed like a publish-subscribe model. What people usually do is, an always-on device (usually a server) is used as one of the devices that need to be kept in sync. Again, this is not a client server model, but each device is a ‘node’, and the always-on device is also just another node.

As you already experienced, it is very easy to get sync conflicts, if a folder is shared between multiple users, because of this decentralised design. In my opinion Syncthing works best for a single user. My use cases are, syncing my notes between pc and mobile, sync files scanned with the mobile to my pc, etc.

If your case is more focused on multiple users, WebDAV server can be an option. But again it’s not straight forward and may not cover all use cases. Depending on what you are trying to achieve, a tool more suitable might be available. For example, if the aim is collaborative development there is Iroh (Still in early stages of development)

I hope this helps.

I went through the comments briefly and didn’t see anything about cases. I highly recommend spending some money on a good case with good cable management slots. It may not look important but it will make life so much easier. Fractal cases are good budget friendly ones. I usually prefer large bulky cases (I like ATX), to ensure good ventilation and easiness to assemble things. Having plenty of space to move around helps a lot while cleaning also.

Another thing, you will see a lot of articles about positive pressure or negative pressure fan arrangement and all. TBH, I really don’t think that matters a lot. Just regular cleaning with a cheap rocket air blower will do. And more than 4 fans are not really needed. The gain is negligible. But ensure you have a good dedicated fan/water cooling for CPU cooling. I recommend Noctua for air cooling.

Oh regarding backing up your data, make sure you plug in your SSD once in a while, to avoid charge depletion. Nowadays the claim is SSDs have better retention and you don’t need to keep it active, but I’m not really sure.