I'm waiting for the day this is just a library you pass an image to and it returns an array. No, not a SaaS. Then on my own pump.io, diaspora, redMatrix etc. it just works. My data, my images, my network. I'm not against the tech at all though. Neat
I run a gitolite[0] instance on my server. It's great so long as you have another way to deal with issues and love the terminal. Access control is a breeze.
I feel like Gitlab is heavy. Gogs is neat, but incomplete. If you don't need/want bloat, gitolite works well.
There are duckduckGo privacy settings you can set. I'm not a big fan of a cloud store for your settings and thankfully duckduckGo allows for settings parameters in the url[0]. You can do things like require POST instead of GET, redirecting, forcing https etc. Once you get your search and privacy settings how you like them, take the resulting url and make an openSearch plugin out of it, manually or with something like my mycroft project[1]. Now any searches use your settings, no account/cloud settings needed. It's then easy to throw in every browser you use. Technically a plugin.
Firefox lets you do that natively too. Self destructing cookies deletes the cookies after you close the browser tab, not the entire window. If the browser doesn't provide complete isolation between tabs, this'll make it so the cookie isn't there to harvest from. You can set each site to tab/browser/never too.
If this is true, it's unfortunate. Things like flux should have a small footprint and a small working domain. I'm willing to spare some complexity for usability tools, but always end up getting off the bus when it gets too heavy.
I agree. It's helpful, but by no means novel or interesting beyond being a tool in the utility belt. It gets more attention than other tools far more interesting.
I use redshift[0] on my linux machines which I really like. Cyanogenmod has LiveDisplay natively which is practically the same thing unfortunately it works off off gps location and not manually editable lang/long. Both are really helpful.
Oh you're right! We need EME'd web assembly so Facebook can hide everything behind a proprietary binary blob. THEN the user will really be free from themselves and their own stupidity. \s
I think this whole thing is a bad idea. They won't allow a scary opt-out button because some software could turn it on, don't allow about:config because it could be flipped, don't allow a build flag in stable because malware could flip it and build. I mean... by that logic, couldn't someone reskin and redistribute alpha or the 'unbranded' with malware? Firefox is so afraid of malware, yet it encourages users to store their passwords in plain text in the browser?
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.
That's true, and you're right. Just a shot in the dark. Maybe someday one of the trendier email clients will support markdown rendering natively in their editors.
I didn't have to do migration, but there are aliases[0] for those who do. Again, I haven't used it so I'm kind of recommending something I haven't touched, but maybe it'll help you out.
There are quite a few themes out there already and growing rapidly. Adding a CSS theme is almost as easy as a wordpress theme. If you wanted a theme catered to your website, I would expect you'd have to get someone to style it up regardless.
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.
Neat project, good luck with it. I think I'll stick with Hugo, it's freaky-fast and postcss breaking CSS into an AST makes it really modular. Power moved from js into css which I'm okay with (and browsers are too).
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.
The intimidating thing for me was always how heavy blogging software was. Never really liked the idea of centralized hosting, but hosting some huge PHP blob with a database never felt like it was worth it. I'm hosting my own site now running Hugo and I love it. I agree that most people have moved to centralized hosting, but I'm seeing a resurgence of self-hosting with static site generators like jekyll, middleman or hugo. Things like static search[1] and static comments[2] are possible with some thought. Really neat and lightweight and with gitolite, I can keep my git repo containing the blog code on the server too, setup commit hook to rebuild the site and I'm maintenence free. I have some npm postcss scripts that build my scss, autoprefix it, etc and dump it into the assets for hugo to build from all in one go.
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.
Seeing what Microsoft has done recently with privacy on their newest operating system, I would not have high hopes for their cloud services. Of course the organizations should be weighing all the pros and cons but I share the sentiment that once the freebie well dries up, terms might be re-evalutaed or services held hostage. Also, and I know the OneDrive plan shakeup fiasco is not apples to apples[0], but I'm sure these free plans could suffer a similar fate. With this, it's not necessarily as easy as moving mom's photo album back to your desktop.
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.
This. Github's enterprise base is at least partially a subset of their open source population. If Github doesn't keep OSS momentum for their product, they lose the perceived "default client" status to git repositories. OSS and eventually enterprise starts looking elsewhere.
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] http://www.theverge.com/2015/12/18/10582446/congress-passes-...