Focalboard open source, self-hosted alternative to Trello, Notion, and Asana
github.com
github.com
(From someone who saw this for the first time)
The way we handle dupes basically follows from a couple of core principles: (1) frontpage space is the scarcest resource on HN (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...), and (2) curiosity withers under repetition (https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...).
Of course, no story counts as a dupe if you haven't seen it before! but we have to moderate for the statistical case.
Mattermost embed silent, nonconsensual phone-home spyware from segment.io in their open source server app! I was astounded when I discovered this (nearly totally undocumented) misfeature that, in some ways, defeats the point of selfhosting an open source project.
I don't think I trust software from them without a significant audit for data leaks/spyware/phone-home, as it seems to me that they don't really care about user privacy even in selfhosted versions.
Which at time of writing states:
## segmentio/analytics-go
This product contains 'analytics-go' by Segment.
Segment analytics client for Go
* HOMEPAGE: * https://github.com/segmentio/analytics-go
Disable silent phone-home for usage tracking:
MM_LOGSETTINGS_ENABLEDIAGNOSTICS: 'false'
(The fact as to why marketing spyware is termed "diagnostics" is left to the reader to discover.)Disable silent phone-home for version freshness check:
MM_SERVICESETTINGS_ENABLESECURITYFIXALERT: 'false'
Grep the released binary for 'api.segment.io' if you don't believe me. I use a Dockerfile along the lines of: FROM mattermost/mattermost-team-edition@$$cap_mattermost_version
RUN sed -i 's#api.segment.io#xx.example.com#gI' /mattermost/bin/mattermost
RUN sed -i 's#securityupdatecheck.mattermost.com#xxxxxxxxxxxxxxxxxxxxxx.example.com#gI' /mattermost/bin/mattermostFor an open source project, working solely on app stores (for all the conveniences they provide for certain users) seems weird. I would really love to try this, but the app store requirement is a big barrier.
I just installed Linux on my desktop and GrapheneOS on my phone and despite the loss of functionalities I felt liberated.
If you distrust big companies handling your data, make the jump it's absolutely worth it. I wouldn't go back.
Linux on the primary desktop is still mostly a nonstarter for me due to the lack of decent email apps (call me old fashioned but I won't do webmail) and, of course, no Word/Excel. Open/LibreOffice are unusable for professional work. Anyone who claims otherwise hasn't tried.
For Linux, I was speaking about your home setup: I use Windows at work too.
I just built the desktop app in <5min by checking it out and running:
make prebuild; make linux-app
Substitute linux with win-wpf or mac.
They also provide both linux and windows binaries from their GH releases.It's only for OS X they do not provide a compiled binary, which you can presumably build easily.
Given that, it's quite entitled to say it's "working solely on app stores".
I'm not Mattermost, but if I made a desktop project in the future I probably wouldn't bother with providing OS X binaries for each release either (I'm a bit out of the loop on what the latest is but doesn't it require Apple hardware and/or a provisioned dev cert even for "sideloaded" apps these days? Is it as straightforward to set up in CI as normal builds?)
I also don’t think it’s entitlement to give feedback on open source projects, which typically have better feedback mechanisms and acceptance from external sources than from commercial vendors. It seems obvious now that Mattermost has other priorities and doesn’t know how and when to close tickets.
We published to the App Stores to see if that would lower the barrier to adoption. We learned that that while they are convenient for most folks, some can't access them, in particular the Windows Store, due to firewalls, corp policy, etc. So far, this seems to be a bigger problem for Windows than Mac in general.
To be transparent, we want to automate all the App Store publishing. It is currently a semi-manual process. It turns out that the Microsoft Store process is easiest (mostly uploading an MSIX file, which they sign for you). Signing for the Mac App Store was brittle for us, and became more manual. Notarizing for standalone builds has additional steps on top of that. Hopefully, Xcode Cloud will eventually solve all these problems.
BTW, another easier way to build might be to fork and use the GitHub actions:
1. Fork the Focalboard repo
2. Go to the Prod-Release Action in your fork (https://github.com/YOURID/focalboard/actions/workflows/prod-...)
3. Enable it if needed (the first time)
4. Run
5. Download the generated packages
I haven't seen this widely used, but might be a great way to try out new projects initially.
The rise of “privacy friendly” or “we don’t share your data” marketing messages IMO is a sign of growing desire towards privacy preserving methods of consuming software.