If anybody here is using gnome instead of KDE, there is "GSConnect" that allows you to use your current desktop environment with KDEConnect on your android mobile phone.
In a similar vein, I am not on Gnome or KDE but have been using the basic kdeconnect functionality, such as sharing clipboard and transferring files, through kdeconnect-cli quite happily. It comes with the standard kdeconnect installation I believe.
This can be useful whenever you need additional models w/ attributes that are not known in advance. For example you may want to allow your users to create a mask where they can enter data based on their own structure. e.g. google forms or strapi https://strapi.io/demo
This site pulls in 6750,83 KB of data assets and scripts. It has disables the shortcut for the developer tools, and fullscreen-prompts me to give them an email address to read the article. without the option to skip, of course.
I am convinced this is not good web design either.
It disables most other shortcuts too. No fullscreen (F11), no "new tab" (Ctrl+T), no tab-jumping between links and input elements. I usually browse without using a mouse and suddenly got trapped inside this article, since they also disabled "close tab" (Ctrl+W)
I detest the fact that the browser uses the F-keys for its own shortcuts. We have an a web-app ported from a mainframe app that uses the F-keys for functions the _user_ carries out and users love being able to press F1 through F12 to activate buttons and other page elements. Familiar users can navigate throughout a complex app without the mouse and without continuous, repetitive tabbing.
Overriding the browser should absolutely be allowed.
For some things, sure. No excuse for being able to override to the extent that you can't leave a site without plugging a mouse in. Maybe, maybe, that could be allowed with an up-front confirmation dialog, but definitely not forced.
It's necessary for some things like games and certain web apps. I made a javascript game awhile ago, about guessing the next character in source code, which required disabling Tab.
It also prompted me to install the app, which is always nice.
Didn't Google work out that 'get the app' modals result 70%of the time in immediate tab closure, in the general population, not just among us angry HN nerds?
People complain that the Firefox NoScript extension is hard to use and breaks sites, and I see threads like this and think 'time to re-evaluate'.
The site with FF + NoScript loads perfectly. Everything I need to read the article and use my keyboard shortcuts works fine, no tampering with my preferences. 20 requests, about 1.5kB and loads in just a hair over one second for me - perfect.
It really is an improvement over the defaults that most websites deliver. It's true that some sites completely break without JavaScript but these are not the norm, and if they are worthy you can always choose to whitelist them temporarily or permanently. I've used the extension for about ten years and have only needed to whitelist a few dozen sites total.
Do yourselves a favor and give it a try if you haven't already. I can't guarantee you will love it immediately but as your 'cut through all the bullshit' option it truly excels.
Usually the functionality of the app exists in the backend, which would be server side. No matter what you do on the frontend, there should be no way for you to trigger actions in the backend you were not authorized to perform.
I always wanted to do something like this as long as I can remember, build something (more or less) self-sustaining in the middle of nowhere to feel fully independent.
I am really curious to what extent the author plans on living there? Will there be houses next to the communal building? Solar Panels? A Generator? An on-site well?
It is this Idea of your own small ecosystem which makes Minecraft so attractive. This is real life Minecraft and I hope to do something like this one day.
Edit: Just to add some interesting Project: There is open source hardware for everything you need to build your own village in the "Global Village Construction Set"[1]
At first it will be a summer-only thing, but we hope over 5-10 years to make it sustainable all year round. We want to use it mainly as a place to work together and get away from cities.
Next summer we will be putting up a 30' yurt, a huge battery bank, and a generator. Water is the hardest, so we'll probably have to catch rain and use a desalinator.
Oh-- we have awesome LTE and 4G coverage there, too!
Congrats on your purchase! Having 4G internet is a very nice addition to your infrastructure, and critical in this day and age. Even if you want to disconnect for extended periods of time, you still have to pay your bills and taxes.
Speaking from experience, solar panels and car batteries work very well to supply a minimal amount of power for daily use (LED lights, charging cell phones and laptops, etc), but a generator will likely be needed for the occasional heavy equipment use. I'm less of a fan of windmills, but they have their place.
Water is indeed the most important infrastructure element to get right, but the solution you go with often depends heavily with your power choices. It's one thing to leave a desalinization system running 24x7 and maintain it, but it's a whole different story if you need something that can be shut down and restarted several months later. Maintenance and long-term reliability become important factors. Maybe you'll get lucky and find you can drill a well for fresh water, but the size of your island makes me think that is unlikely.
Other fun things to think about: plumbing, septic systems, waste disposal, hot water systems, lights, cooking, and refrigeration.
Then there is always the debate of redundancy vs. simplicity. and the real cost of maintaining an often fragile infrastructure.
I am very curious to hear more about your progresses in building out your island infrastructure and have subscribed to your blog.
Thanks! I actually have an RV with solar and LED, so I'm very familiar with the awesomeness of running off the grid. I'm not sure we'll get enough solar to make it cost efficient, but we're still looking into it.
I haven't done enough research into desalination-- I had no idea that shutting it down for a while is a problem. Why is that?
We may also do rainwater recovery + filtration for drinking/cooking, and salt for showering. Worst case we have to bring water over every time and shower in salt.
Planning on doing propane or wood to heat water, propane for refrigeration and cooking.
Thanks for subscribing! We'll be going out in the spring to do some more work and will definitely keep people updated on progress.
My extended family owns a cabin on a tiny island on a lake in Wisconsin.
* You're right - having a house on an island is cooler than having a house on the shore. :)
* Probably not applicable to you, but when they need to move heavy things (Backhoe to dredge the dock, materials, etc.) to the island, they drive them in over the frozen lake in midwinter.
* The power comes in over an underwater cable. Something you might want to look into.
First of all, owning an island sounds awesome. Congrats on making the leap.
I don't know how much knowledge you have about desalinators, but here is a FAQ by the company that makes the reverse osmosis unit that I use at work: http://www.searecovery.com/marine/src_faqs.html Being so close to land, you will need a way to sterilize the water. A UV attachment should work.
I also recommend taking a course in Wilderness First Aid. I took a 70 Hour Wilderness First Responder course by Wilderness Medical Associates. It was an excellent course.
I Would love to migrate 50+ KVM VMs to LXC-Containers, but there seem to be some problems left with security[1][2].
I cant wait to get my hands on Docker, but I lack the SELinux knowledge to secure everything the 'proper' way.
Is LXC (and therefore Docker) really ready for Production yet?
It depends on how you are using containers. If you control what code is run in them and who has access to the containers and their hosts, then production use should be fine as far as security goes.
However, if you're trying to run something which lets untrusted people login to the containers or run arbitrary untrusted code in the containers, then I certainly wouldn't recommend doing that with containers in a production environment.
One project you might like to keep an eye on is CoreOS [1]. As I understand it, their goal is to create an OS which will come configured to safely run containers. Once it is ready I would expect it will be suitable for use in a production environment.
