Foam author here! I am very open to all suggestions in this area. Foam is a new project I built solely to my own requirements, but I'm actively seeking feedback on how to make it more broadly applicable as per our principles:
https://foambubble.github.io/foam/principles
That would seal the deal for me. I have tens of thousands of documents, notes, pictures etc. spread across hundreds of subdirectories. Foam looks extremely promising.
Amazing! Please let me know in GitHub issues or Twitter DMs how you get along. This is a very early alpha release, keen to hear feedback at all levels!
Foam author here! I'm not personally familiar with VSCodium, but contributions in this area would be extremely welcome as long as they don't prevent any of our Roadmap features working on VS Code!
Foam author here! I also don't like dependency on Jekyll, and over time I want to build a bespoke static site generator for Foam (possibly based on Gatsby) that's able to create a richer browsing experience.
Thanks for the idea! I have quite a few on the Roadmap already, and would love to hear more in GitHub issues
Hi! Foam author here. We generate markdown references to bridge [[wiki-link]]s to work with Markdown tools. For the time being this is optimised for a) the editing experience in VS Code and b) the GitHub pages publishing pipeline, so it's more convenient to generate markdown links without the `.md` suffix.
I think the problem is that you're including these links in the README. New visitors expect all the links there to work, but they are broken.
If the README only included basic information and a link to the github pages, it would be easier to follow.
P.S. since I'm already typing, have you considered supporting semantic links, in addition to the regular ones? It will make the relationships between the pages clearer at a glance, and allow for better automation in the future. It might also help in visualization, for example you could toggle only specific relationships, to get a simpler graph of the information you care about.
That's actually a good idea. Right now we pay the salary to you, and you can then donate it to a charity. It would be way more tax efficient to just skip the middle step.
I agree this could be the case, except that there is no pressure to work on anything work-related. You can literally contribute to any OSS project, whether it's your own video game side hustle, a learning project in a language we don't use, or, if the mood strikes, also one of our projects' dependencies.
This is a great idea. I don't know if it's even a starter, tax code wise, but would be amazing if it could be done.
For the time being, we are happy with $20 for the reasons outlined in the post itself. It's not an incentive, it's a reward, and a purely optional one. Many people in the company (I'm the author) do work on Open Source and don't make use of the benefit, because they don't care about the money. This, for us, is fine.
I don't care about it now as a full time employed adult. As a university student I could have well become a full time maintainer of some of the scientific libraries that have been neglected since the 80s.
Now as a gainfully employed productive member of society I like the idea of going on a legal tax strike when the government does something I absolutely detest.
>Oh by the by, since you are trying so hard to destroy civil society again this year, here's my bill for keeping it running. You're welcome.
Which is precisely why it would never happen. But you should definitely spend some ~money~ speech on politicians and lobbyists to start some of them thinking about it.
