I am loving the new release cadence!
I am loving the new release cadence!
my understanding is that terms of service would be helpful but not needed if someone trued to sue because you blocked access to the site. I would not expect ToS for a site like you are explaining, but if it did it would say "the web admin will ban you if you are naughty, you have been warned"
For privacy policy i think what you wrote to give us context is near perfect. Explain how your app stores data, be specific about encryption at rest and in motion. If your app is designed to hold name, email address, billing info you should highlight that in your policy. including a (monitored) contact email for questions would be nice, but not needed imo unless you are storing PII
While not a solution right now, I just want to add that the general transit feed spec aims to solve the data interoperability of different transit systems. The transit system keeps a publicly accessible zip file up to date, and then anyone can pull/parse the schedule/prediction data in a consistent way across transit systems. I know in the us adoption is slow, with vendors prefering to build their own walled gardens and transit agencies lacking the vocabulary or skills to advocate for more open data/tools
For keeping track of tasks on my projects i use todo txt. For each of my projects will drop a file named todo.txt in the root. each line is a task, and i order them based on priority. I can walk away from it and when i start working on the project again, i have an simple way to see the list of tasks i have laid out for this project.
I personally find it less useful to see the "big picture" of all tasks, and this lets me focus on the details of my projects without forcing a bunch of structure.
It looks like there is one here:
VS Code's extension system makes it pretty easy to build your own code snippet extension. I use my own private extension to easily "generate" different types of markdown files (ie readme vs a troubleshooting guide) from my personalized snippets.
Clouds and Feuds from Age Of Wonders
Hosting my own git server on my NAS made my life easier and better due to the new freedoms it offers. Backups are centralized, and I have all the space i need to keep any interesting code safe. I am using forgjeo now and highly recommend it. You can also use other front ends (or none and just ssh/filesystem) but forgjeo gives me artifacts (ie docker registry), code search, LFS, and more. With my own git server, my local filesystem only has what I am working on recently (or as my workstation space allows). My home folder has a folder for each version control system (git, pijul, svn). Inside of these i have 2 sub folders: /
Some examples of different domains are: open, work, personal, dragonish. I do not separate what forge or remote service in the filesystem, this is a persona boundary.
I use git remote names and branches in each repo to handle what software forge and any upstream/maintainers i need to work with. As an example my work repos only get pushed to my work server (ie, only 1 git remote named origin set to my work's server), but my open ones will go to forgjeo and github (i setup 2 git remotes, origin and github. origin in this domain goes to my forgjeo). If i have a need i go into some more git branching strategy which I do find has helped me over my life, but I think I am overthinking this post now! keep it all simple enough for what your needs are.