81–90 of 336 posts
Whats up with the name? Are you trying to get this thing to be a a complete layer over the OS?
What we hope to achieve someday is to make this a layer between your operating system and your web apps. Sorry for my pretencious phrasing, but essentially we want to be like an operating system for your web-apps. hope that makes a bit clearer
Been beta testing this (full disclosure, angel invester) and i can honestly say i miss it when i'm not on my Big Sur machine. Vim keybindings are such a win, and Sigma does it better than all previous attempts at a vim-like browser because it's properly modal. You hit i to Insert (interact) with a page and escape to go back to controlling the browser. Or you can ignore all that and just use it as a tabs-on-the-sed br…
Except vim's interface is confusing https://stackoverflow.blog/2017/05/23/stack-overflow-helping...
We're working hard to make sure users don't feel punished when switching to SigmaOS, and only feeling faster from there. Part of the inspiration is from Vim, but that doesn't mean we aren't learning from its mistakes :)
Been beta testing this (full disclosure, angel invester) and i can honestly say i miss it when i'm not on my Big Sur machine. Vim keybindings are such a win, and Sigma does it better than all previous attempts at a vim-like browser because it's properly modal. You hit i to Insert (interact) with a page and escape to go back to controlling the browser. Or you can ignore all that and just use it as a tabs-on-the-sed br…
Also, most other OSes have native splitting of windows.
Earlier quoted context omitted.
Fair point, can't convince you we're trustworthy just by telling you, but I can still say it anyways :P We don't use keyloggers. We don't sell your data. If we did, it would be a breach of our privacy policy and you could sue us, right? (Don't know if I should be suggesting you sue us, but since you won't have a reason to, think we're safe :p)
Is this how you defend your marketing claims on privacy? Sue us if we have a data breach?
Earlier quoted context omitted.
> To the people saying $15 is too much: SigmaOS is almost certainly targeting companies, not individual users. Doubtful, individual signups and education discounts show otherwise. Even as a company I'd be reluctant to purchase this.
Heya, actually our main target audience are prosumers who pay for productivity tools within teams and companies. As mentioned this is a tool made more for work specifically, like notion, Airtable and the tools like this.
Can the team benefits be realized in a poly-browser environment?
In your mandatory signup form, I am told "Looks like you missed one of the required fields: [facepalm] Problems". I do not suffer from any of the listed problems. … and now I have to dig up this login link? really testing my patience here…
Regarding the login flow, would you use Google Sign-In if we had it?
Could you describe what you are actually adding on top of the new Safari? Tab groups are there, sync of them too, keyboard operation too, sharing as well (your improved sharing does only seem to work when both the sender and receiver have your browser, so for a niche tool, it probably won't be useful that often). Which would mean, based on your landing page, that I'd be paying 15$ per month for split-screen. Don't ge…
Hey there! Thanks for your comment :) Here’s my take on tab groups (Safari) vs workspaces (SigmaOS): they seem similar, but they feel very different. e.g. • you don’t always see all your tab groups = no behaviour change, people will still pile up tabs they don’t need. Think of Slack: when you’re done with a workspace, you delete it. But if you’re done with a tab group, you just leave it there to clutter your browser,…
I get the vision. You're building Superhuman but for browsers. Power tools for power users who are willing to invest the $$ and the effort to reimagine the most frequently used tool on their computer. Bravo!
Earlier quoted context omitted.
I'm working on building it from scratch for SigmaOS :P. Should have it out in a couple weeks! edit: implementing Chrome extension API. All Chrome extensions will be available :)
What made you decide to build it from scratch? By following a different system you're leaving a lot of free work on the table. For example, I extensively use Vimium, Dark Reader, Stylus, TamperMonkey, and LastPass. By doing it from scratch, all of those extensions would need to be re-implemented in the SigmaOS API. I love the idea of SigmaOS but I can't abandon Chrome/Firefox if I can't have LastPass, for example.