I know it may sound stupid but in my latest project I chose ULIDs because I can easily select them as one word, instead of various implementations of browsers, terminals, DB guis, etc each have their own opinion how to select and copy the whole UUID. So from that point of view ULIDs "look" better for me as they are more ergonomic when I actually have to deal with them manually.
I don't think it's stupid and this is one of the reason I prefer ULIDs or something like it. These IDs are very important for diagnostics, and making them easily selectable is a good goal in my book.
No... No, it's not. Just require password/confirmation for every purchase. I have 3 kids and not a single one has purchased anything without me approving it (where they did not pay with their own pocket money).
(a) Not everyone can afford to manage that
(e) They key point is that it needs to be standardized to the point of the vendors supporting it. As long as there is a general API (for example) on the device that I can point a plug-in to, it's fine, but AFAIK such a thing does not exist at this point in time.
Personally I'm using Migadu at the moment and for me the killer feature is that the price per month is not bound to users and/or domains. I have several tens of "users" (many are myself but for reasons with completely separate identity as far as the server is concerned), and 8 or so domains. There is barely any traffic (in the order of <10 emails in and out per day).
Most other providers I would have to pay 10-30x as much, just because I have several users and domains, at a grand total overhead cost of 0$ to the provider.
They have a lot of positive points, but I can give a few negatives to try to balance out the opinions:
* When sending emails to others, in my experience they usually arrive at spam. This could be because in those cases I was sending from domains less than one year old, but I don't think I've had this issue with other providers (e.g. Protonmail).
* Using them to send emails in any automated way (e.g. scripting) is against their TOS. I understand their reasoning, but I would have liked this rule to be relaxed a bit because I would really like to use it for sending notifications to myself, so I would be happy even with a restriction like "if sender and receiver are the same address (or part of the same mailbox), you're allowed to use scripts to send those".
* They don't guarantee any kind of SLA. If they go down, they go down. Not a problem most of the time, but during the start of The Pandemic they had a lot of downtime and that made me realize how painful it is to try to use email when the provider has flaky availability. They fixed it after ~3 months or so, but that was bad enough to make me stop using them for some time. When I heard they fixed it I gave them a second chance and haven't had any issues since then (it's been 3-4 years already and I haven't noticed issues). But this single experience is hard to forget, so I don't use them for anything critical (stuff I would need to read in less than 24 hours or so, much less respond), just in case. Even if SMTP should mostly ensure that you eventually receive emails, and that your sent emails eventually reach their destination, I still have the critical stuff sent to a Gmail or Outlook address.
Despite those points, I like their service enough that I still recommend them from time to time.
I've been using them for years and did not realize they don't allow automated emails. At some point I was sending some automated emails from one inbox to another, but they were very infrequent, less than 1 a day. If you're looking for email-based notifications, I'd recommend Pushover [0] anyways. It's more flexible (can do email, curl, etc.), free, and won't violate ToS.
> Some sites disabled pinch zooms (massively frustrating for images).
Best are the blogs that have embedded images of graphs or something and they are as large as you can make them (edge to edge). Try pinch to zoom... nope. Tap on image... Here is a smaller version of the image (not edge to edge). Oooookay... Can I zoom now? Hahahhahah....nope!
My mistake, I did know they were one of the two. I should have double checked. In general I know the difference between the two just forgot which Migadu was based on.
I am maintaining a fairly complex set of nodered flows, dealing with some long running tasks performed by other tools.
When checking n8n the impression was that it's like a v2 of NodeRed that learned from what NR did wrong. Lots of tools an capabilities you end up wishing for in NR are built into n8n.
For example:
* data flow is simplified, no one global "msg" var that gets clobbered by every 2nd custom script
* you can fairly easily test flows
* you can see execution history, including in/out data
* you can see exacting flows
General question: Is there an actual use for this kinds of projects, beyond showing what can be done? I have seen many different "web desktop" projects and while most of them were impressive in their own (technical) ways, I could never see the an actual use case for them.
My Synology NAS uses something like this for its navigation and even if it's initially strange, you instantly miss it when you access it from your phone, when the UI turns into this nested list which is not intuitive at all
I personally hate this from Synology. While their apps are meaningful structured and look good, it is just a natural mismatch to put sub windows into a parent window. Anyone remembering multi sub window apps in the Microsoft office suite in the 90s/00s. Was also horrible without a browser/html involved.
StarOffice (precursor to LibreOffice) used to take this one step further and replicated the taskbar and start menu inside the application window: https://winworldpc.com/product/staroffice/5x
Yes, and from day one Opera (when it was still called Multitorg) used it to give us something like "tabbed browsing". I think that was in the mid-1990s ;)
Yeah, same. I have a synology NAS and the desktop-of-windows-in-a-window aspect of it just seems archaic to me. I have a browser with tabs, thanks. If I really need two things going, I'll open two tabs or two browser windows.
I also like the Synology UI. It is helpful to see multiple apps at the same time and is especially useful when moving files around to have two or more file browser windows open.
We talk about have consistent desktop experience everywhere. This provides exactly that. Your desktop is everywhere you go.
What sucks is, you need a whole browser for it. What sucks is, I think that's the only way to do it. A full on VM to make it real.
I would use this if the browser stack had more promise of not changing for 50 years and not owned by Google. Unfortunately our last place of freedom is native execution.
Personally I can see myself using this to access my homelab from work without having to open extra ports. Since I can't install a personal VPN client on my work machine, a web-based desktop behind a login would give me most of what I want.
Guacamole was actually my first choice and it's what I used a year ago. In that time span I've screwed up enough that my lab actually needs a whole rebuild, so I'm looking at alternatives to see what could be swapped over. As it is, I think Guacamole remains my first choice. I was just responding to the question of what this could be used for.
As someone who has spent years working on one of these, that is a very interesting question. I do it as a passion/side project so it's not as important to me, but I also like to think of it like the "Field of Dreams" philosophy of "If You Build It, They Will Come". I hope one day if I add enough features and interconnect enough things, the applicability will show itself.
I'd use this to store files on an encrypted Digital Ocean droplet, better than fiddling around with Nextcloud. I treat cloud storage as a USB stick; file management is 100% manual, no sync.
