sushimako

https://www.instagram.com/fontwien

https://en.wikipedia.org/wiki/Karl-Marx-Hof

https://goo.gl/maps/E1PvcZahSPVjk4RY9

- https://github.com/nakkaya/ferret/blob/master/ferret.org

- https://en.wikipedia.org/wiki/Literate_programming

[...] they *also* added a raw image mode that will never break again and doesn't require Mach-Os. And people said they wouldn't help. This is intended for us.

HN discussion about this tweet: https://news.ycombinator.com/item?id=29591578

Each project gets its own directory somewhere in my $home with some subdirs. There might be various others specific to the project-domain, but these are the most common:

• notes/ contains plaintext files of everything i write down. File-name structure is <date-str>:<note-type>, e.g. 2020-05-09:call (:call are the most typical ones). As others have also suggested, I take a lot of notes for record keeping & plannning purposes.

• workspace/ contains all source code repositories, or other files necessary to work. Pretty much anything I might touch while coding.

• auth/ for things like ssh public keys used on the project

• downloads/ Project-specific downloads.

Then I create new entries in my ~/.bash_aliases that "get me" right into the coding-env of a project. Say I work on a python project, I might have an alias that looks sth like:

  alias fb='cd ~/fooproject/workspace/foobot && echo "loading virtualenv..." && source .venv/bin/activate';

  alias foh='cd ~/opendecks/workspace/foh';
  alias fohj='cd ~/opendecks/workspace/foh/src/clj/opendecks/foh';
  alias fohs='cd ~/opendecks/workspace/foh/src/cljs/opendecks/foh';

Lastly, I started employing chrome/chromium's user-profiles to seperate browsing for each project. This isolates work-related browsing from my personal activity (cookies, logins, passwords etc), and provides a nice cognitive barrier against procrastination. I'm not logged into any social networks on those work-profiles and switching to my private profile to browse facebook is a more concious act than opening a new tab in the current window. Each browser profile is set-up to save all downloads to the project-specific `./downloads` directory, again not to mingle (potentially confidential) resources.

I haven't automated any of the above steps, because it's so simple and takes me at most 10-15 mins to create a new instance. This has worked really well for me so far, because it clearly seperates almost all resources associated to a project, while being friction-less in tooling/switching between workspaces (versus e.g. waiting for a VM or docker instance to start). Another nice side-effect is that I can easily archive or clean-up past projects.

  user=> (< 1 2 3)
  true

Federation of self-hosted servers and the "official cloud" seems to be on Wire's road-map, cf:

* Third paragraph of OP

* https://www.reddit.com/r/selfhosted/comments/5vylls/wire_end...

* Last sentence on https://medium.com/@wireapp/open-sourcing-wire-server-code-e...

This announcement anticipates (a) getting developers to use surrogate UIDs instead of @username for mentions, and (b) that their clients will only use display names in the future and rely on specific UI elements to distinguish ambiguous ones.

[0] https://medium.com/slack-developer-blog/network-effects-gett...

Here[3] is some very outdated documentation on the first version. We initially tried to connect the walls via bungees - didn't work out at all as you can imagine. The following year we added the velcro system after I found this amazing post [2] on a hexayurt mailing-list, describing someone's experiments with materials. Without that person's efforts and time spent on research I could have never finished this one!

Of course there's already a bunch improvements lined up for a v2 - hopefully next year :)

[0] http://imgur.com/a/8K1dR

[1] https://en.wikipedia.org/wiki/Hexayurt

[2] https://groups.google.com/d/msg/hexayurt/2QRUl3txk-8/v_A0DDc...

[3] http://flo.jottit.com/moonberry

Already ironed out identical columns but can't seem to find anything else. Any idea?

My co-founder and I moved on to a new project a year ago, but this thing is still buzzing along on a cheap DO box and works like a charm with basically zero maintenance. Frontend is vanilla JS, backend in Go and the protocol is our slight modification of differential sync[0] to (re-)synchronize all text and metadata.

[0] https://neil.fraser.name/writing/sync/