[0] http://www.theverge.com/2015/12/18/10582446/congress-passes-...
285 karma · joined May 25, 2015
[0] http://www.theverge.com/2015/12/18/10582446/congress-passes-...
I feel like Gitlab is heavy. Gogs is neat, but incomplete. If you don't need/want bloat, gitolite works well.
[0] gitolite.com
PS. If you need a favicon from any site for a plugin or otherwise, easiest way I've found is https://www.google.com/s2/favicons?domain=duckduckgo.com. Will grab it from wheverever the sysadmin decided to put it.
[0]https://duckduckgo.com/params [1]http://mycroftproject.com/submitos.html
* Better privacy
* uBlock with EasyPrivacy list
* Https everywhere
It really feels like a landgrab and not anything anyone has been asking for. Firefox has to compete with the Chrome web store, but you can't burn your house down to save a room. What's left if Firefox becomes some centralized market akin to iOS, Windows Store, Play etc. Forced AMO signing flies in the face of the decentralized web. "Malware happened" and "Chrome does it" aren't really answers.
I think getting backed into a corner has made Moz take risks with their ideology. Hopefully they give developers and users a lot more time to deal with the upcoming changes.
The main two things Wordress has on static generated blogs at the moment are their current community and the editing experience. The editing is of course by design. I have heard that prose.io[0] is nice, but have never worked with it. Essentially webhooked github for cms-free blogs. To me, that seems like the way we should be going.
edit: add link, their site is mainly for access [0] https://github.com/prose/prose
As for git. The reason these blogs are so heavy is because editing text files for most people requires a text editor interface on the http which in turn means you need dynamic content whicn in tern means you need a database which in tern means you need a way to submit this code so php which in t... and down the rabbit hole goes. If you get rid of the "editing files requires a text editor" part, then your site is easy and maintainable.
Git I think is a bit more programmer-focused of an api for random blogger joe, but a light wrapper might work. Maybe something like emailing a server with subject "POST: title of blog post" body "text for post" and having the server grab that data from the email, if it came from an allowed user, throwing it into the posts/ folder, git committing it and then deploying it to an apache server on itself. Actions like "delete", "edit" would just search for files with the exact name as in the subject and do the required git action on it.
Something like this could probably work. Email clients already have the text editor users want, why rebuild the wheel? If there was someway to wrap this all up without requiring users actually host their own entire email, I think it would be nice. I think teaching your mom git is a pipe dream unfortunately even if it would fix the Copy-of-Copy-of-Birthday-List_OLD2.txt problem.
A lot of this is unncessary, I could just be using css. I like that there's not all this asset-flow magic built out, just simple npm with bash cli. Unix philosophy and very little heavy lifting. I think there's still hope.
Now if we can just teach casual users git...
[0]https://gohugo.io/ [1]http://www.blevesearch.com/news/Site-Search/ [2]https://tlvince.com/static-commenting
I know the Univeristy of Wisconsin used to roll its own email, but recently started using Outlook acounts for everything and I'm definitely not a fan. Migration was painful or it at least seemed so. If orgs are able to isolate their architecture from the cloud and services, it might work out. Unfortunately, a lot of companies and organizations treat aggregate privacy like a preference instead of a requirement. Bartering chips.
My cynicism may be unfounded, but a company by the same name helped write the book on fostering lock-in not too long ago.
[0] http://www.theverge.com/2015/11/3/9662414/microsoft-reduces-...
This is getting more and more relvent since solid competition is starting to crop up everywhere. Gitlab, Bitbucket, GOGs, Gitolite, Gerrit. Not apples to apples of course, but Enterprise has a lot of decisions when it comes to git control.
Even the things that could be considered Github "lockins" aren't really so: Google's git-appraise[0] could make pull-requests portable, Github's wikis are portable by their very nature[1], software like git-issues[2] could make issues portable. Not in the immediate, but decentralize-everything is a rising sentiment.
The only real lockins I see are Github's work-flow and social community. If either become toxic, developers will start to look elsewhere. Like Microsoft, I'm sure Github can ride the majority-player wave for years before it starts really hurting them, but simply saying a community-centric company only has to look out for their paying community's interests is short-sighted.
[0] https://github.com/google/git-appraise [1] https://github.com/gollum/gollum [2] https://github.com/duplys/git-issues
[1] https://www.raspberrypi.org/blog/piphone-home-made-raspberry...
edit: typo
Also, being able to toggle the UA and setup lists to dynamically set it is helpful in my usecase.
https://addons.mozilla.org/en-US/firefox/addon/uacontrol/
https://addons.mozilla.org/en-us/firefox/addon/user-agent-js...
String...
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Update the string every now and then?
https://techblog.willshouse.com/2012/01/03/most-common-user-...
Disable all plugins.
Best I got, sorry.