you pointing out “mainly” just shifts his question to the next time he decides to host a service, which is what i meant to point out.

they might state that, but upstream syncthing says that the feature is intentionally hidden in the advanced settings and they plan to deprecate it.

apart from syncthing not being a backup solution, the question revolves around seldhosting im general, not purely on photo backup.

i don’t think the need for a plain calendar warrants a resource monster such as nextcloud.

There is a symlink trick on the server side. It’s a little annoying that it is only a workaround, but one set up it’s great! I was looking for the git issue where i found it, but was only able to find this one (it seems to be documented now).

https://github.com/Kozea/Radicale/wiki/Sharing-Collections

i know, but it is unnecessarily complicated. i ended up using filestash and am quite happy with it!

one thing still stopping me from using it is the lack of upload links. if i cannot send a link in my vacation group that everyone uploads their images to, the tool is out of the question.

that and screen sharing

honestly that isnthe only thing that stopd me from going all in on teamspeak/mumble

i just need a screen sharing solution (not necessarily built into those tools)

I was talking about this docker image: https://hub.docker.com/r/collabora/code/

correction from my side: it is the development edition, which means rolling release and possibly less stability, but it is worth a try imho (but i do not use it personally)

you can set up collabora without nextcloud, as well

i find the latex fonts weird to deal with. for me it is more a thing of setting up your template the way you want it and keep sailing with that.

edit: typo

you could have a look at etherpad. seems pretty cool and is extensible with plugins. i don’t know about resource consumption and security aspects, tho, because i don’t personally use it. there are also a few publicly usable instances to test it out (see their github). keep in mind, however, that those come with plugins and do not reflect the vanilla state of the tool.

Unfortunately died last year

so… it can not be FreeBSD? :)

Wait aren’t the system requirements for Mailcow crazy high? How can you run it + other software on a mere Pi? Also: do you have a static IP?

Do you mean local communities? If not, I do not understand your statement.
Also: can you explain how searching for communities is worse on smaller instances than on large ones? That does not make sense to me and does not reflect my experience at all.

I‘m all with you on the beehaw topic, but please keep in mind to recommend smaller instances to newbies, because that‘s what federation is all about. Aside from load distribution (lots of instances are run by individuals or groups on small(ish) machines), you can avoid being independent on single large entities keeping their uptime etc.

TLDR: recommend smaller instances for load distribution to get the best out of a federated world!

• whats your opinion on selfhosting mail servers?
• why have you chosen baikal over radicale?
• are you happy with filestash? im torn between filestash and filebrowser

• Nextcloud, mainly for calendars and contacts; occasionally for sharing files with others.
• Syncthing for syncing files.

Quick question: have you thought about hosting Radicale and filebrowser instead of NextCloud? I think that would be definetly lighter on your system.

Also: I have read lots of mixed opinions whether mailservers should be selfhosted - what is your take on this? Do you know about problems reaching the big player mailservers?