• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: October 21st, 2023

help-circle



  • I know the developer of this website. It’s hard paywall. You won’t be able to bypass it by modifying the elements in any sense.

    As you mentioned in some other comments, only the currently archived ones will be available. If you are looking for just this specific article, let me know, I will archive and share the link here. If you are looking for a method to bypass it entirely, I don’t think it’s possible.

    Also I assume you are not in a position to afford the subscription. It’s fairly decent considering the quality of articles. So whenever you can afford it, subscribe and support them. Nowadays good long form articles are non existent in Indian media.


  • 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.







  • sorter_plainview@lemmy.todaytoLinux@lemmy.mlBalenca vs Ventoy?
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    5 months ago

    I have a different experience. There was one thread which linked to a github issue. The issue said some blobs don’t have source code. Ironically when I went on to check, the blobs mentioned in the issue had source code, but there were other blobs which seemed to miss the source or build instructions.

    I would love to have an independent audit to put this issue at rest. All that happens is more and more noise and no resolution. I am not a programmer so can’t really help here.




  • 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.