dschramm

As a normal person I couldn't agree more, but look at it from a business or indiehacker point of view. If you use Twitter to share your work and connect with potential customers, it's a bit of a loss. It would be similar to creators or streamers if someone were to buy YouTube or Twitch and potentially ruin it.

What if we just don't acknowledge the new name and refer to everything by Twitter or Tweet?

Backend is 100% Go with Clickhouse for analytics data and PostgreSQL for everything else and a Vue frontend :)

You can take a look at Pirsch Analytics [0], which I am a co-founder of. We take privacy very seriously, that is why the core of Pirsch is open-source [1].

[0] https://pirsch.io/

[1] https://github.com/pirsch-analytics/pirsch

Dark grey is probably reserved for the iMac Pro.

Spoiler alert: It will be the fastest iMac ever.

I got so used to the Apple logo on the chin bar that removing it makes it looks like a knockoff product.

They did get more annoying lately though. Nowadays you have to wrestle through a horrible click game of dark patterns to not accidentally accept anything. Things like putting a small "Accept all" in the top right corner where you expect a close button or hiding the settings with at 12px in light grey.

Hey Hackers!

We're a two-person team based in Germany and proud to announce the beta launch of our latest product!

Pirsch is a simple, privacy-friendly, open-source web analytics solution free of cookies. It can be integrated into your website using JavaScript or directly into your backend. We put a strong focus on developer friendliness by offering an easy-to-use API, SDKs for different programming languages, integrations for popular platforms, and good documentation.

The main benefit of our backend integration is that it can't be blocked by browsers while respecting your visitors' privacy at the same time.

Pirsch does not collect personal information. All visits are anonymized and aggregated into meaningful statistics once per day. This ensures that we don't save individual page visits longer than 24 hours while you get the data you need. For details, you can check out the open-source core of Pirsch on GitHub: https://github.com/pirsch-analyt...

The name is German and refers to a special kind of hunt: the hunter carefully and quietly enters the area to be hunted, he stalks against the wind to get as close as possible to the prey without being noticed.

During the beta, we will make improvements, fix bugs, and add more features. Here is a list of a few additions we had in mind:

* add more documentation

* email reports

* data export

* more SDKs

* goal, event, and campaign tracking (further down the road)

We expect to move out of beta at the end of February. Everything will be free until then, but you can find prices on our website. Let us know what you think!

Cheers,

Daniel

We completely rebuild the frontend of our app [1] to focus on keyboard input. It was just released and I am quite happy with it.

[1] https://emvi.com/blog/product-update-june-2020-0DdK57ngZ2

Disclaimer: I am a co-founder.

I guess Emvi[1] checks all your boxes. We are currently working on a new user interface that focuses on keyboard input and it will be available this summer. You can read in our blog [2] how it all started. Markdown-like shortcuts [3] will come with it as well!

[1] https://emvi.com/

[2] https://emvi.com/blog/a-new-experimental-user-interface-QMZg...

[3] https://twitter.com/emvi/status/1264962445585637385

Nice to see that the "Zettelkasten" is getting more and more attention. We published an article about it on our blog a couple of months ago as well:

https://emvi.com/blog/luhmanns-zettelkasten-a-productivity-t...

Good point. We are on QWERTZ aswell, so we are thinking about making it customizable at some point.

We are trying to present GUI users with good arguments for a switch. Our tests with people that are unfamiliar with CLIs showed they were up to speed after a short amount of time.

You are right, I created a ticket for this to be fixed in the next release!

Interesting thought, I would love to hear the leading UX designers of those companies discuss their ideas, desperately trying to settle on a solution they all like.

That's definitely something we have to look into. We currently see mobile usage primarily for searching and reading and less for creating content. But you are right, this needs special attention. We do not want to maintain two different approaches.

We have not found any reliable numbers on keyboard usage vs mouse input yet, but it would be quite valuable.

Compared to normal shortcuts the commands are easier to remember, because they mostly represent the verb for the action you want to accomplish. Instead of memorizing Ctrl + E or similar for a new article, you type /write or an alias like /new. This way you only have to know what actions are possible, without connecting them to an inconclusive key combination. Most commands will auto-complete after the first two letters, so you are not losing that much time either.

Our frontend is build on Vue.js and the shortcuts are handled by global JS events.

I agree, that's one of the challenges we have to tackle. The commands being contextual to the page you are on helps in my point of view, but we have to explore ways of onboarding users in a proper way.

Hello HN!

We just rolled out this little MVP for a new user interface for our knowledge base software.

I would love to hear what you think about it!

Cheers, Daniel

Other knowledge bases and wikis tend to rely on a tree-like hierarchy and setting access permissions with a top-to-bottom approach. In Emvi permissions are set on per article basis, so they can have company-wide reach and still be edited by a small team only. We think this scales better with growing organizations, because silos are removed by default.

Let me know if you have any more questions.

I agree, the culture in an organization makes or breaks a knowledge base. We try to lower the barrier of entry by not giving an article a definitive place, meaning you don't have to think about where to put something when writing a new doc - similar to Wikipedia.

We do not have an import feature yet, but that is definitely coming. Where would you like to migrate from?

Hello HN!

Emvi is our approach to a easy-to-use knowledge base for companies and teams of all sizes and we finally reached public beta. You can use it to write down everything you need to remember, share or document and make it discoverable for everyone else in your organization.

We found that existing tools structure content in a tree-like hierarchy which tends to limit internal reach and scalability. For Emvi, we implemented a system that is closer to sites like Wikipedia, Medium or even YouTube - articles are linked internally, curated to lists and grouped by tags.

Our goal is to make it accessible for both technical and non-technical users and to keep the content maintainable for the long term.

Features we already include:

* Powerful search with filters and sorting options

* Activity feed and notifications

* WYSIWYG-editor with real-time collaboration

* @-mention any element (articles, lists, tags, users or groups)

* Full article change history

* Fine-grained rights management for users and groups on a per article basis

* Mobile support

* English and German UI

* Multiple translations for articles and list titles

Over the next few months we are planning to add comments, integrations, embeds, import/export and markdown support. We already have an API which can pull articles from Emvi, visit our blog to see it in action. Shortly after leaving beta state, we will offer a self-hosted version aswell.

Feel free to share your thoughts and questions in the comments.

Cheers, Daniel

Hello HN, co-founder of Emvi here!

Emvi is our approach to a real-time knowledge base and we finally opened registrations for public Beta. We found that existing tools structure content in a tree-like hierarchy which tends to limit reach and scalability.

For Emvi we implemented a concept that is closer to pages like Wikipedia or Medium - articles are linked internally, curated to lists and grouped by tags. Our goal is to make it accessible for both technical and non-technical users and to keep the content maintainable for the long term.

Some features we already include:

* Powerful search with filters and sorting options

* Activity feed and notifications

* WYSIWYG-editor with real-time collaboration

* @-mention any element (articles, lists, users, groups or tags)

* Full article change history

* Fine-grained rights management for users and groups

* Multiple translations for articles and list titles

We are currently working on comments and embeds and an early API is available on GitHub[1].

Feel free to share your thoughts and questions in the comments.

Cheers,

Daniel

[1] https://github.com/emvi