The cool part about using Alpine as a minimalist desktop is you can run the entire system from RAM - assuming you're running in diskless mode.
I've showed people my Alpine desktop setup _on their own laptop_ by booting from a USB. After booting, I unplug the USB, continue running the distro, and then restarting their machine as if nothing ever happened. Lots of cool factor driving motivation there, but I agree it's not as easy to use nor maintainable for most people.
Also if your workstation dies, just toggle BIOS settings - if needed - and boot on another machine. No swapping / migrating drives required. Works amazingly if you're used to running on crap / dated hardware.
I assume financially this would probably not be feasible or sustainable everywhere but I really wish malls could lean further into theme parks rather than shopping hubs
Most of them are half way there with movie theaters, arcades, etc. I recently went to one with an attached Medieval Times.
I'm curious how much filling in laser tag, rock climbing, and other in person only activities would generate turnout.
Not intended on initially being what you're looking for, but contributors and those interested often discuss privacy implications of developing software in the Off Topic chat for privacy focused project I've created.
Many have tried - very recently - and seemingly stalled or failed at creating something like this with wide adoption, most notably Tim Berners-Lee with the SOLID protocol
The roadblock is always getting major tech companies to accept it as a valid means of accessing user data.
The amount of times I've heard about SOLID on NPR or other popular mainstream newscasts only to garner little to no support is astounding. Definitely take note where others have seemingly failed here because it's an uphill battle.
Sort of tangent, but the fact that Block Protocol is also managing the distribution of the resulting UI components, unlike Solid which encouraged people to consume the data independently through an API, makes it more accessible.
Personally my hesitancy in embracing Solid is the complexity. What I really want is essentially an HTTP filesystem API for my programs. Like a modern WebDAV to replace Google Drive. All the linked data stuff might be useful down the road but I currently don't need it.
Comment above does a good job at describing the distinction. It's more than just re-usable HTML/CSS/JS, that's just how they're making it accessible to others. There are entities associated with the HTML/CSS/JS mapped alongside the component, which is the core benefit here.
Tried the demo and got stuck at the Stripe payment step and hit the error "Provided API Key is wrong".
That said, this is a desperately needed product for small teams. Was considering building something like this as a SaaS for the last couple years. A small team I was apart of spent multiple sprints mulling over onboarding tweaks for our users involving all these components.
If it's not already a feature or being worked on, please consider making template Q&A flows that can plop users in a bucket. It's often asked for right before or after signup and is a relatively big lift to keep building over and over.
Thank you very much for the feedback! Yes, we see the pain on small teams and also on big companies with complex flows or when they want to scale user acquisition.
Can you provide an example of the template Q&A flows? You mean the onboarding screens?
Btw, we've just fixed the API key for the payment flow, thanks for reporting :P
So many signups now involve taking a small survey that will sort you into a some cohort. Lots of times, this is required prior to even entering an email or password. Making this process easy, or having a template with predefined dynamic questions and answer flows (even if they're fake and meant to be changed) would be super helpful and solve a whole engineering effort in one fell swoop.
Note, some of that is a requirement by the Matrix protocol and is out of clients control. It's ultimately up to the server to configure different password requirements.
> Clients SHOULD enforce that the password provided is suitably complex. The password SHOULD include a lower-case letter, an upper-case letter, a number and a symbol and be at a minimum 8 characters in length. Servers MAY reject weak passwords with an error code M_WEAK_PASSWORD.
While it can, my opinion is the client and server should not enforce anything about password strength, but MAY warn the user about weak passwords.
The criteria that I think would be acceptable to be enforced includes:
- A maximum (not a minimum) length, which must be suitably long, perhaps 200 bytes (or longer).
- Rejecting passwords containing null bytes.
- Rejecting passwords containing sequences of bytes that cannot be transmitted using the protocol, if it is necessary to transmit the password using the protocol at all (which it might not be, since it might use a hash instead). (This depends on the protocol.)
- If despite the advice above, the client knows that the server will reject other passwords too, and knows precisely what the criteria are, the client can reject the same passwords.
Examples of some things that should be allowed (and should not be rejected) include:
- Passwords that are short.
- Passwords that include your username as a substring.
- Character classes/lack of character classes (e.g. you should not require nor prohibit punctuation).
- Control characters (if not causing problems with the protocol like mentioned above).
- Invalid UTF-8 sequences.
(Just because they are allowed though, does not necessarily mean that they should be recommended.)
Also, passwords should always be case-sensitive.
The user should decide by themself what password they want to set, although it is OK to include advice that is optional.
Not to be overly pedantic, but SHOULD is not a requirement according to https://www.ietf.org/rfc/rfc2119.txt, but a recommendation that should be fully understood before making a different decision. I fully agree that it should be a different measure of complexity though!
As a side-note, I wish I could give lastpass a regex or pattern or something to check auto-generate guesses against (it would be great to have a [trusted] library of these, too). I often end up regenerating or tweaking my auto generate settings a few times for every new account I create to get around this stuff.
Password managers are great until you need to log in on someone else’s machine. Especially when you don’t have your device on you. It’s bitten me before.
If you have hundreds of unique passwords, I don't see an alternative unless you're a savant or use predictable patterns. But that doesn't mean there aren't ways to get around it. For one, using a password manager shouldn't stop you from remembering your most important passwords, especially those you expect to use in other people's machines. You can take some extra care to make these important passwords easy to remember while still being secure. I could go on but everything I'd say is quite obvious.
Fluffychat is mentioned a lot here as a good UI/UX alternative to Element. Just wanted to bring up another that I'm working on called Syphon. It's not at the stage where it can compete with Fluffychat in terms of spec parity or maturity, but I think it's worth discussing as an effort.
Like I said, it's still very much in Alpha and needs quite a bit of work, but the UX flows and design have been well received by others. Though there is an opinionated default UX and design paradigm, there is a focus is to make everything customizable and the theming options are growing over every release.
The goal is to eventually find a sweet spot between Discord and Signal and bridge the gap to Matrix between those communities.
I have a demanding day job and other obligations that keep me busy, but I spend nearly all my free time and every vacation in the last year working on this project. We're constantly looking for other contributors and there's several other ways to help including donations. Feel free to join the official room for updates to track progress and please feel free to reach out with feedback!
Additionally, I just merged Multi-account support this week and it will be in the next release. Not sure of any other Matrix client that has this feature, so there's some unique features that we're focusing on to set it apart.
> Additionally, I just merged Multi-account support this week and it will be in the next release. Not sure of any other Matrix client that has this feature
Mirage has this but it's the only one i know of. it also didnt seem to work with cross device signing last i tried it.
Very glad there's other clients supporting this. Thanks for the heads up!
I was under the impression some of the desktop clients had it in the form of swapping CLI flags on start, but it seems to support switching under the settings menu in the latest release. Much like email, many people will have more than one user they'd like to swap between so very glad to see other clients adding this feature with user friendly UX.
Yea, element has support for multiple profiles but you have to run multiple clients to use multiple accounts. It;s a bit like firefox profiles and it works but I don't really count it as multiple account support.
nice, i tried quaternion a long time ago so i wasn't aware it had it now. i haven't tried neochat before even though i use kde. i'll give it a shot and see how well it works
I'm almost more excited because of the proxy network affect this will have on microkernel popularization and alternatives like Dahlia OS (https://dahliaos.io/) that are looking to be independent distros of Fuchsia.
I understand peoples concern about a walled garden situation here, but I'd argue to only become worried if Fuchsia suddenly stopped being committed to openly and someone needed to maintain a fork. The working code for both the microkernel and the OS is all open source.
