21

Have an exciting project to share or a problem that you are trying to solve?

This is a general open thread to talk about what you're working on - or want to work on!

Feel free to share ideas, ask for help, or just fill us in on your cool project :)

Anything goes in terms of topics, just as long as it is STEM-related.

Have an exciting project to share or a problem that you are trying to solve? This is a general open thread to talk about what you're working on - or want to work on! Feel free to share ideas, ask for help, or just fill us in on your cool project :) Anything goes in terms of topics, just as long as it is STEM-related.

29 comments

I'm not sure if it counts as a project, but I started looking into how complex it would be to set up an etherpad on a server I own, for a private group discussion, since Discourse seemed like a lot of overhead and google docs is nosey. Turns out it's very very easy to set up manually, so I'm quite tempted to just do that since it should only be used for a little while and then discarded, but I also know that's the story of every piece of tech that ends up being depended on for everything and used for 30 years... So I should probably put the time in to find/make an ansible role or whatever. But bleh.

That totally counts! And I would say at least 40 years minimum for relying on software... haha. Though this sounds like a situation where you don't want perfection to be the enemy of good enough.

Tangentially, do you have any insights into how Google Docs is nosey?

Ah I just mean general google nosiness, eg: needing an account to write things in a shared doc. Idk exactly what data they harvest but there's no reason people should have to have accounts to do realtime text editing together, especially if the doc can be password-protected to stop randomers editing it. I've been thinking about lightweight options for private judge discussion for the fiction prize; I wanted something that wouldn't be massive overhead to host myself (or to ask a trusted party to host) if people didn't want to give data to a third party or make an account anywhere else. And anyone can write in any publicly hosted instance, but nothing can be deleted from the history once it's up, so I think we need to be able to delete files in case someone pastes personal details into one by accident. So I think that would mean it needs to be self-hosted, so if people were concerned about the security of me hosting it, I'd definitely want to have it all automated so nobody else got that maintenance burden and I could just go 'here is script, point it at your ip' to the host.

Ah, that makes sense. Having to create an alt Google account to edit a doc is really burdensome, plus the risk of unintentionally logging in/editing with a main Google account. I am excited to see what you come up with :)