Mastodon is significantly easier to set up, easier to use, more user friendly, and has a larger community than GNU Social and all the other alternatives. Non-technical visitors of privacytools.io will probably be discouraged by all the "here just set up a server and compile this" - so having the easy to use one first is likely the best option.
I also made some quality of life adjustments, such as adding .DS_Store to the .gitignore so that Mac users can contribute without accidentally checking in useless files, as well as added instructions on how to build the HTML files into the README.
Screenshots
## Description
Mastodon is significantly easier to set up, easier to use, more user friendly, and has a larger community than GNU Social and all the other alternatives. _Non-technical visitors of privacytools.io will probably be discouraged by all the "here just set up a server and compile this"_ - so having the easy to use one first is likely the best option.
I also made some quality of life adjustments, such as adding `.DS_Store` to the `.gitignore` so that Mac users can contribute without accidentally checking in useless files, as well as added instructions on how to build the HTML files into the README.
## Screenshots
<img width="1469" alt="screen shot 2018-11-22 at 7 19 06 pm" src="https://user-images.githubusercontent.com/2773700/48927546-7c6a3480-ee8b-11e8-843c-e008d4753fa8.png">
Previously we had the software dropdown sorted seemingly at random. Some things weren't even listed in the dropdown, and many were not in the right location...
Now all of that is fixed!
Additionally, the Key Disclosure section was randomly in the middle of all the software and does not appear to be linked to from anywhere. I moved it higher up the page so it fits better and is more visible (it seems important).
Just added some organizational changes.
Previously we had the software dropdown sorted seemingly at random. Some things weren't even listed in the dropdown, and many were not in the right location...
<img width="1453" alt="screen shot 2018-11-22 at 7 45 42 pm" src="https://user-images.githubusercontent.com/2773700/48927937-344d1100-ee8f-11e8-8c2f-8afa467e4425.png">
Now all of that is fixed!
<img width="1453" alt="screen shot 2018-11-22 at 7 44 37 pm" src="https://user-images.githubusercontent.com/2773700/48927919-0e277100-ee8f-11e8-9f52-8c6405bf1d8a.png">
Additionally, the Key Disclosure section was randomly in the middle of all the software and does not appear to be linked to from anywhere. I moved it higher up the page so it fits better and is more visible (it seems important).
Apologies for turning this into a giant housekeeping PR, feel free to cherrypick commits and decide on the other ones later (though I think it's a no-brainer to merge).
Apologies for turning this into a giant housekeeping PR, feel free to cherrypick commits and decide on the other ones later (though I think it's a no-brainer to merge).
bundle install took like 5 minutes on my Ubuntu 18.04, but simply changing the gem from gh pages to jekyll works too and lets me start working in no time.
Regarding the README update, could you please take a look at this? https://github.com/privacytoolsIO/privacytools.io/issues/609#issuecomment-441092679
bundle install took like 5 minutes on my Ubuntu 18.04, but simply changing the gem from gh pages to jekyll works too and lets me start working in no time.
Using it in your projects means that when you deploy your site to GitHub Pages, you will not be caught by unexpected differences between various versions of the gems.
So just for the future it might not be worth suggesting that contributors do this. At the very least, I personally didn't mind waiting the 2-3 minutes running a bundle install.
Hmm, I think the two gems are not guaranteed to function identically ([as per the Jekyll website](
https://jekyllrb.com/docs/github-pages/#the-github-pages-gem))...
> Using it in your projects means that when you deploy your site to GitHub Pages, you will not be caught by unexpected differences between various versions of the gems.
So just for the future it might not be worth suggesting that contributors do this. At the very least, I personally didn't mind waiting the 2-3 minutes running a `bundle install`.
@Shifterovich Also, are you on IRC/can I contact you somewhere else? I have a few ideas for changes I'd want to discuss but I don't think they belong here.
@Shifterovich Also, are you on IRC/can I contact you somewhere else? I have a few ideas for changes I'd want to discuss but I don't think they belong here.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
Mastodon is significantly easier to set up, easier to use, more user friendly, and has a larger community than GNU Social and all the other alternatives. Non-technical visitors of privacytools.io will probably be discouraged by all the "here just set up a server and compile this" - so having the easy to use one first is likely the best option.
I also made some quality of life adjustments, such as adding
.DS_Storeto the.gitignoreso that Mac users can contribute without accidentally checking in useless files, as well as added instructions on how to build the HTML files into the README.Screenshots
Just added some organizational changes.
Previously we had the software dropdown sorted seemingly at random. Some things weren't even listed in the dropdown, and many were not in the right location...
Now all of that is fixed!
Additionally, the Key Disclosure section was randomly in the middle of all the software and does not appear to be linked to from anywhere. I moved it higher up the page so it fits better and is more visible (it seems important).
Apologies for turning this into a giant housekeeping PR, feel free to cherrypick commits and decide on the other ones later (though I think it's a no-brainer to merge).
Thanks a lot. All of these are issues which majorly irritated me.
Regarding the README update, could you please take a look at this? https://github.com/privacytoolsIO/privacytools.io/issues/609#issuecomment-441092679
bundle install took like 5 minutes on my Ubuntu 18.04, but simply changing the gem from gh pages to jekyll works too and lets me start working in no time.
Hmm, I think the two gems are not guaranteed to function identically (as per the Jekyll website)...
So just for the future it might not be worth suggesting that contributors do this. At the very least, I personally didn't mind waiting the 2-3 minutes running a
bundle install.@Shifterovich Also, are you on IRC/can I contact you somewhere else? I have a few ideas for changes I'd want to discuss but I don't think they belong here.
t.me/Shifterovich or Shifterovich on Signal assuming you don't need my number or Shifterovich on Riot.im. I can do IRC/XMPP later today or tomorrow.