u_tamtam

@u_tamtam@programming.dev

• ⁨Comment⁩ on ⁨Haptic: A new local-first, privacy-focused and open-source home for your markdown notes⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  I think you should give Trilium(Next) Notes a try:

  • it has the hierarchical notes structure that you are familiar with in obsidian

  • it has better ways of keeping things organized (attributes can be values or references, can be shared and inherited, which provides a flexible framework for having notes “types” as templates that can be extended, e.g. people vs. colleagues, businesses vs. companies, etc)

  • it has the concept of note hoisting (which lets you focus on a note and its sub-notes, so other projects/spaces don’t come in the way of autocomplete and placing references), and workspaces that builds further on top of that

  • it can be used standalone (local client/offline-only, like obsidian) but coupling it with a remote-server opens more interesting use-cases (synching, sharing notes with others by public URLs, one-user/multi-client editing) which gives the best of both worlds (local-first/online-first) and lets you access your personal notes on devices you don’t necessarily own (which obsidian doesn’t). The mobile app story isn’t great (it’s a PWA with limited offline capabilities at the moment), but isn’t worse than the alternatives either (I can’t really work and think long form on a handheld, no matter the editor experience, but perhaps that’s just me).

• ⁨Comment⁩ on ⁨Haptic: A new local-first, privacy-focused and open-source home for your markdown notes⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  You need to list out your requirements. What do you want to do? Where do you need your data? Do you care about open source? Self-hosting? Do you have an idea how your content will be organized? Will you ever need to tap into it as data? Etc

• ⁨Comment⁩ on ⁨Haptic: A new local-first, privacy-focused and open-source home for your markdown notes⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Have you tried trilium notes? Not as hyped and polished, but does extraordinarily well IME.

• ⁨Comment⁩ on ⁨Haptic: A new local-first, privacy-focused and open-source home for your markdown notes⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  I didn’t like obsidian’s lacking in attributes structuring/typing and the fact that it cannot serve over a web UI (for wherever you cannot install the heavy client or just to share notes via URL), and found trilium notes to be doing that perfectly, and much much more. Highly recommend.

• ⁨Comment⁩ on ⁨What self hosting feels like (It's painful, please help 🥲)⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  Matrix seemed interesting right until I got to self hosting it. Then, getting to know it from up close, and the absolute trainwreck that the protocol is, made me love XMPP. Matrix has no excuse for being so messy and fragile at this point. You do you, but I decided that it isn’t worth my sysadmin time (especially when something like ejabberd is practically fire and forget).

• ⁨Comment⁩ on ⁨Linkwarden - An open-source collaborative bookmark manager to collect, organize and preserve webpages | July 2024 Update - New iOS App, Full Page Copy, User Administration and more... 🚀⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  How does that compare to wallabag?

• ⁨Comment⁩ on ⁨Best way to host Nextcloud with Collabora Office?⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

  That’s… a tool in the bucket for that. But I’m not really sure that’s the point here?

• ⁨Comment⁩ on ⁨Best way to host Nextcloud with Collabora Office?⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

  I don’t think containers are bad, nor that the performance lost in abstractions really is significant. I just think that running multiple services on a physical machine is a delicate balancing act that requires knowledge of what’s truly going on, and careful sharing of resources, sometimes across containers. By the time you’ve reached that point (and know what every container does and how its services are set-up), you’ve defeated the main reason why many people use containers in the first place (just to fire and forget black boxes that just work, mostly), and only added layers of tooling and complexity between yourself and what’s going on.

• ⁨Comment⁩ on ⁨OrcaSlicer V2.1.0 Official Release⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

  The UI of Prusa slicer is hot garbage though.

  I give orca/bambu the edge for “prettier on screenshots”, but in practice, I don’t find their UI paradigm to be more efficient nor convenient.

• ⁨Comment⁩ on ⁨So You Think You Know Git? - FOSDEM 2024⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  I’m with you. Hg-git still is to this day the best git UI I know…

• ⁨Comment⁩ on ⁨Rant: Cura did the one thing a slicer shouldn't do⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  I’ve been on the prusa slicer side of things for a long time, and you won’t see me arguing in favor of cura. That said, you should probably consider doing daily backups of your home folder, using something like Borg/restic which have great incremental and compressed backups (practically backing up TBs in seconds).

• ⁨Comment⁩ on ⁨Do any of you have that one service that just breaks constantly? I'd love to love Nextcloud, but it sure makes that difficult at times⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  Most containers don’t package DB programs. Precisely so you don’t have to run 10 different database programs. You can have one Postgres container or whatever.

  Well, that’s not the case of the official Nextcloud image: hub.docker.com/_/nextcloud (it defaults to sqlite which might as well be the reason of so many complaints), and the point about services duplication still holds: github.com/docker-library/repo-info/…/nextcloud

  You can typically configure the software in a docker container just as much as you could if you installed it on your host OS…

  True, but how large do you estimate the intersection of “users using docker by default because it’s convenient” and “users using docker and having the knowledge and putting the effort to fine-tune each and every container, optimizing/rebuilding/recomposing images as needed”?

  I’m not saying it’s not feasible, I’m saying that nextcloud’s packaging can be quite tricky due to the breadth of its scope, and by the time you’ve given yourself fair chances for success, you’ve already thrown away most of the convenience docker brings.

• ⁨Comment⁩ on ⁨Do any of you have that one service that just breaks constantly? I'd love to love Nextcloud, but it sure makes that difficult at times⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  See my reply to a sibling post. Nextcloud can do a great many things, are your dozen other containers really comparable? Would throwing in another “heavy” container like Gitlab not also result in the same outcome?

• ⁨Comment⁩ on ⁨Do any of you have that one service that just breaks constantly? I'd love to love Nextcloud, but it sure makes that difficult at times⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  Well, that is boldly assuming:

  • that endlessly duplicating services across containers causes no overhead: you probably already have a SQL server, a Redis server, a PHP daemon, a Web server, … but a docker image doesn’t know, and indeed, doesn’t care about redundancy and wasting storage and memory

  • that the sum of those individual components work as well and as efficiently as a single (highly-optimized) pooled instance: every service/database in its own container duplicates tight event loops, socket communications, JITs, caches, … instead of pooling it and optimizing globally for the whole server, wasting threads, causing CPU cache misses, missing optimization paths, and increasing CPU load in the process

  • that those images are configured according to your actual end-users needs, and not to some packager’s conception of a “typical user”: do you do mailing? A/V calling? collaborative document editing? … Your container probably includes (and runs) those things, and more, whether you want it or not

  • that those images are properly tuned for your hardware, by somehow betting on the packager to know in advance (and for every deployment) about your usable memory, storage layout, available cores/threads, baseline load and service prioritization

  And this is even before assuming that docker abstractions are free (which they are not)

• ⁨Comment⁩ on ⁨Do any of you have that one service that just breaks constantly? I'd love to love Nextcloud, but it sure makes that difficult at times⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  and why would that be? More abstraction thrown in for the sake of sysadmin convenience doesn’t magically make things more efficient…

• ⁨Comment⁩ on ⁨Do any of you have that one service that just breaks constantly? I'd love to love Nextcloud, but it sure makes that difficult at times⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  Take that as you want but a vast majority of the complaints I hear about nextcloud are from people running it through docker.

• ⁨Comment⁩ on ⁨QNAP NAS Remote Access with WireGuard VPN⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  Would be nice to be able to run WG on the NAS directly and not need a server, wouldn’t it? I believe there are a few go/rust userspace WG servers out there but I don’t know if anyone’s using them for anything like that.

• ⁨Comment⁩ on ⁨PeerTube stress tests: resilience lies in your peers!⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  Except for a marginal fraction of the top YouTubers, aren’t most of them getting paid to inject sponsored links and from donations/patronage these days? It seems that the deal you are referring to has been off the table for a majority of YouTubers for a very long time now, and I don’t see why other platforms wouldn’t be as good, or even healthier than YouTube to provide them that kind of revenue.

• ⁨Comment⁩ on ⁨Unison | A friendly, statically-typed, functional programming language from the future · Unison programming language⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  unison is currently the closest to showing how it is actually done

  What makes you say that? As far as I’m aware, even the theoretical soundness of it isn’t a done deal (this is a harder nut to crack than e.g. rust’s borrow checker)

  Overall, I think one of 2 things will happen:

  In this niche, perhaps, I don’t believe any of those will gain mainstream adoption (though I hope I’m wrong)

• ⁨Comment⁩ on ⁨Sharp corner algorithm⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  I get that but your original sketch seemed to be showing smaller and smaller radiuses shaping the edge, which necessarily implies thinner and thinner layers. Now I fail to see what’s different from what sliders currently do.

• ⁨Comment⁩ on ⁨Sharp corner algorithm⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  So you would need different later heights around the edges just to stack those ever thinner lines? How do you think this will interact with the rest of the print?

• ⁨Comment⁩ on ⁨Unison | A friendly, statically-typed, functional programming language from the future · Unison programming language⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  Sorry if it came that way :)

• ⁨Comment⁩ on ⁨Unison | A friendly, statically-typed, functional programming language from the future · Unison programming language⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  functional languages aren’t battle tested or imply they aren’t useful in real world problem solving

  Yup, I never said that, though? What I was about was to draw a parallel between functional programming languages and explorations from several decades ago vs the new languages and explorations going into effect typing/capabilities programming now (and the long way ahead for those).

  What I find interesting is that those pioneering FP languages never came to top the popularity chart, implying that I’m not expecting Unison to be different (but the good parts might make it into Java/C#/Python/… many years from now).

• ⁨Comment⁩ on ⁨Unison | A friendly, statically-typed, functional programming language from the future · Unison programming language⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  “Capabilities” is the new “Functional Programming” of decades prior,

  Scala is also expanding in this area via the Caprese project: docs.scala-lang.org/scala3/reference/…/cc.html and it promises Safe Exceptions, Safe Nullability, Safe Asynchronicity in direct style/without the “what color is your function” dilemma, delineation of pure vs impure functions, … even Rust’s borrow checker (and memory guarantees) becomes a special case of Capabilities.

  I believe this is a major paradigm shift, but the ergonomics have yet to be figured out and be battle-tested in the real world. Ultimately, like for Functional Programming Languages (OCaml, F#, Haskell, …) I don’t expect pionniers like Unison/Koka/Scala to ever become mainstream, but the “good parts” to be ported to ever the more complex and clunky “general purpose” programming languages (or, why I love Scala which is multiparadigm and still very thin/clean at its core).

• ⁨Comment⁩ on ⁨I was able to completely migrate from Fusion 360 To FreeCAD⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  Yup, absolutely, it’s a good idea. Did you think of creating a feature request on their bug tracker? github.com/FreeCAD/FreeCAD/issues

• ⁨Comment⁩ on ⁨PSA: Try FreeCAD Link Branch (it's a big improvement!)⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  individual toolsets (2D Animation, Video Editing, VFX, Sculpting, Poly Modeling, Bone Rigging, Scripting – ALL with entire workflows associated with them) – has managed to be a wildly usable solution despite many of its individual subsystems working together.

  Yup, I believe this boils down to good project management, someone has to steer those individual components so they work together better, in a cohesive manner, to make the result more than the sum its the parts. This is especially difficult in an opensource context where different contributors have different interests, and I think Blender, having managed that much, is an example to follow.

  And I agree with everything you wrote, I don’t expect FreeCAD to get there in a reasonable timeframe unless it gets serious funding and expertise brought in.

  Plasticity is a good project to follow, I don’t think they are comparable nor intended for the same audience, but there are product design aspects to learn from it, definitely :)

• ⁨Comment⁩ on ⁨I was able to completely migrate from Fusion 360 To FreeCAD⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  Oh, I think I understand. I generally select a bunch of things and use wiki.freecad.org/Sketcher_ConstrainEqual and never thought of selecting the dimensions directly. That sounds like a good idea/convenience indeed :)

• ⁨Comment⁩ on ⁨I was able to completely migrate from Fusion 360 To FreeCAD⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  Totally fair and fine :) Having kept an eye on the project for several years already, I think it’s heading in the right direction (and no alternative has emerged), but yeah, the road ahead is very long!

• ⁨Comment⁩ on ⁨I was able to completely migrate from Fusion 360 To FreeCAD⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  it’s a bit annoying when you can’t click something to use as a reference.

  You mean, that? youtu.be/x7_KgeLOcKY?feature=shared

• ⁨Comment⁩ on ⁨I was able to completely migrate from Fusion 360 To FreeCAD⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  I don’t want to be this guy, but if you are willing to fork that much, perhaps you could consider donating some to FreeCAD? See it as an investment: in the end you would get a better version of a software that you truly own 🙂