This is Stan, posting.

Here you go:

Windows: https://1password.onfastspring.com/in-app/1password-7-for-windows

Since the website does not mention it clearly:

Turn it off.

Remove the power

Hold Volume Down and Power on the right side of the device. (not on the remote)

Turn the power back on while holding the buttons.

Watch if the notification LED turns green.

So the TeamViewer team decided to not save settings directly to the .ini file that is processed during start up, causing all your settings to reset to default every time you launch the app.

Workaround is as follows:

Start TeamViewer Portable

Configure everything to your liking

Go to Extras > Options > Advanced > Show Advanced Options

Scroll all the way down until you reach Export settings for TeamViewerPortable and hit that.

Save the file as tv.ini into the same directory as TeamViewer.exe

Close TeamViewer

Open ´TeamViewer.iniand changeimportsettings=0toimportsettings=1`

Copy paste your ogg/mp3/wav(?) file to

/sdcard/Notifications for notification sounds.

/sdcard/Alarms for alarm sounds.

/sdcard/Ringtones for ringtones.

If they then do not show up in your System > Sound > Notifications file picker, move those folders to /sdcard/DCIM/Media instead. So

/sdcard/DCIM/Media/Notifications for notification sounds.

/sdcard/DCIM/Media/Alarms for alarm sounds.

/sdcard/DCIM/Media/Ringtones for ringtones.

If they still do not show up, reboot your phone.

WinSCP by default uses temporary file names for files above a certain size, when uploading to a server. This makes you lose permissions and user/group settings on files you upload and chose to replace existing files on the server.

You can disable this here by making it not use temporary files.

Default: https://i.imgur.com/vQagaA9.png

Without Icons: https://i.imgur.com/AS8fdoh.png

Disclaimer: Every single number I state in this post is pure guesswork.

Every time I have to read a "the insiders want more builds" thread on Twitter I just have to shake my head and wonder why Microsoft keeps doing the Windows Insider program the way they are doing it now, instead of the far better version they have on the Xbox. But when you really think about it, the Windows system is just better for them, not for users though.

The main complaint with the Windows Insider system is always that there are too few, too many, too buggy, too not-buggy releases and everyone wants to get pleased but the crowd can't agree on what they really want. Obviously. People are different.

The problem comes from the point that ~80% of the Windows Insider system members is made up of non-technical people. There, I said it. It does not sound nice but my ball park number is probably super off but you get what I am trying to say. Many people just signed up to have the latest and greatest, get updates faster or just prance around saying how they are part of a team of special people that gets to test software, sometimes even writing "QA Tester for Microsoft Corporation" in their CVs.

To be clear, I am not hating on them. I did the same when I was 15/16 and got into the first private beta programs and I was hella proud of it. But what this does is diluting the focus a release branch of the Insider program has. I know like 2(?) people that are on slow, the rest is all not on the program at all or on fast. So, what happens when non-technical people are on fast and get more and more buggier builds? Are they happy about that? Do they know how to file proper feedback? Will they stay on that build for longer? I think the answer to all of that is "no".

The Insider program is largely a huuuge generator of telemetry for Microsoft. You don't have to be a technical person to generate telemetry though. You just happen to be useful while you suffer through broken shit. Is that fun? Does that give you some sort of accomplishment? Do you think you are helping?

The Xbox and Windows Insider ring systems

Xbox

Omega

Delta - ~3 updates a week

Beta - between 8 and 15 a month

Alpha - around 15 to 20 a month

Windows

(needs stats on release cadence)

Release Preview aka "dead weight that should be used to test Cumulative Updates every month instead"

Slow aka "let’s just get bit more telemetry to make sure all our fixes worked in Fast"

Fast aka "The Thing"

Fast + A/B

Fast + Skip Ahead aka "The worst idea ever that just feels like a bad hack and should be removed"

Fast + Skip Ahead + A/B

Skip Ahead

So, when Microsoft reaches the end of a development milestone for their bi-annual releases, there is a point where they switch branches and use Fast to stabilize the final version that is to go out to everyone in the world. At some point the pressure from Insiders got too high, claiming that they feel bored or left out of the development progress because Microsoft clearly is already working on the next version of Windows but they can't test it yet. In comes Skip Ahead. What should have been a new release ring above Fast or a reason to rebalance the current rings' purposes, gets implemented as a tacked on extra dropdown that works only twice a year, has a limited number (not shown in UI) of people that can sign up for it and disables itself after it is no longer used.

I get that it was probably the fastest way to implement this, but it just feels plain bad. In my opinion, Fast should just have been the branch that is always on the latest dev branch. If Microsoft switches, so do users. If you want to be on the safe side, switch to Slow in those times. But this would have required a change in their flighting strategy, to move everything down one ring and try to make users understand. Which they would not have. Know why? Because most people just sign up for the program and then forget about it only come back to complain.

A/B Testing

So, A/B testing is Microsoft's way to do what the Xbox system does, but silently and without pissing people off. In the Xbox system, people are clearly more experienced and more knowledgeable if they reached a higher feedback level and climb their ranks from Omega to Alpha because they had to prove it.

But there is no such thing in the Windows program, while it is clearly useful since you want to know the dedicated testers from the "I just want the latest shit, always"-crowd. You know that you can give the more technical people a more broken build and faster releases because they can probably handle it, because, you know… they are more technical. They are probably also wise enough to keep a few machines on a more stable branch or maybe don't run the latest build on their daily driver at all.

So... how do you tell those people apart if they are on the same branch and using the same builds? A/B testing. Microsoft can completely decide which features you get to test based on what they know about you, they can tell if you are the more technical person, based on how you interact with the OS, the feedback system and more. And they don't have to tell you or anyone about it, so people that don't get chosen for a test don't feel left out, just have "bad luck". Guess what happens now? The more technical people get the more experimental features that have a higher chance of being broken, and most of the non-technical people don't. But some still do because telemetry is important. Grats to those lucky guys, I guess.

What they did with that is basically adopting the Xbox system in silent, without any visible benefit to the user. Why not do it in the open and let people work for their right to get to test more experimental stuff? Let them prove that they can handle it.

Do you just don't want to appear to be mean, segregating like that? So, they don't feel left out? I don't really know but I think Microsoft should just switch to a clearly tiered system openly. Offer rewards for every tier you climb, actually give them something for doing being helpful instead of just being telemetry bots.

1. Forward 80 and 443 to 80 and 443 on your router 2. Install the Synology WebStation package 3. Turn off

Automatically redirect HTTP connections to HTTPS  in the DSM Control Panel –> Network –> DSM Settings. 4. Start the WebStation package 5. Create a Virtual Host with your DynDNS domain name as host 6. Ensure the backend server and PHP is set, along with checking the box for port 80/443. Setting not configured for PHP is fine.

Launch the Control Panel app and go to Security => Certificate => Addand follow the instructions of the wizard. 

Prerequisites:

Run dism /Online /Cleanup-Image /RestoreHealth

If it completes fine :goto end

If it fails with

Error: 0x800f081f The source files could not be found.

open

C:\Windows\logs\CBS\cbs.log.

If it mentions Microsoft-Windows-TestRoot-and-FlightSigning-Package, then this guide is for you.

There are two ways to fix this problem, one is sledgehammer and just delete the package and remove the registration of it from the registry, the other is using NSudo and CBSEnum to remove the packages the elegant way.

Sledgehammer:

Assign your user ownership of and delete 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

Assign your user ownership and delete

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

Search your system drive for Microsoft-Windows-TestRoot-and-FlightSigning-Package and delete every file that comes up.

It should be 4 files in C:\Windows\servicing\Packages

Elegant: 

So for most of Skype's existence, a Skype group had a group name and a group topic that could be changed individually of each other.

With the later versions (it started after 6.21) this was changed so now groups only have one option: "Rename group", which actually does not rename the group locally you, yet changes the topic of the conversation, which is a global action that changes the name it is shown as for everyone in that group.

On mobile (Android/iOS) this was changed before it happened in the Desktop clients which lead to confusing interop between users because on mobile you clicked "rename" yet it changed the "topic" for everyone.

Community Manager Claudius pointed out here (http://community.skype.com/t5/Windows-desktop-client/Missing-Features-in-the-new-design-preview/m-p/... that the base behaviour change, going from two options for "topic" and "name" to only "name" (that actually changes "topic") was done because it was too confusing for users.

I can understand that if those confusions got reported by mobile users, because their button was actually always called "rename", yet changed the topic. On Desktop it all made sense and I hereby plead to get the option to rename groups locally back.

My favorite example on why this new behaviour is bad is the following: It means that instead of showing a familiar, easy to remember and recognizable name, the contact list now shows the topic, a often (maybe?) changing text that is not representing the members of said conversation, as the name.

Let's say you have more than one group of friends (hey, it happens) on Skype to talk about different things. One is your football club and the others are the chess dudes. You obviously name those groups "The sports guys" and "The chess guys" for your own sanity and ease of use in identifying them in your list. Both groups often have a similar topic set, mostly the date of the next meeting.

Now, with the new design, you are left with two entries in your contact list, both conveniently named "Next meeting at 5pm". Now what? Which one is which? No way to know at a simple glance. You really have to open the group and look at the members list to really know.

As a person who has been using Skype for group conversations for years and years, this really grinds my gears and I have been trying to get the developers attentions in varius threads on this forum (http://community.skype.com/t5/Windows-desktop-client/Missing-Features-in-the-new-design-preview/td-p... once in the Android section (http://community.skype.com/t5/Android/Wrong-behaviour-in-group-conversations/td-p/1968699) where this problem has existed for a looong time and was probably the root cause of user confusion, and over more private channels and the app feedback page.

With patch 6.1, Blizzard introduced a new heirloom system to keep track of the various items you find that you can use while levelling that scale with the level of characters. It supports upgrades and keeps the upgrade progress on an account wide level. Upgrades are done by buying an item and using it on the heirloom in the heirloom journal. If you upgrade an item in the journal, every character wearing said item automatically has the upgraded version.

As with every new expansion as of lately, in Warlords of Draenor, Blizzard introduced a new legendary quest line. Which, at the end, rewards a legendary ring. This ring exists in many variations, strength DPS, agility DPS, healing, agility tanking, strength tanking. As soon as you reach a new step while progressing through the quest line, you get a more powerful variation of the ring. If you want to also have a different version of the ring, let's say for playing a different spec, you have to buy it for gold from a vendor. Those additional rings do not upgrade, if you upgrade your main ring, you have to buy the higher version again, for gold, at the vendor. At the end, when you reach the legendary quality level of the ring, you can still get upgrades for it, in the form of an item that drops from the last boss of the current raid tier. Each item increases the rings item level by a flat amount. It does not increase the item level of any secondary rings that you have and might want to use while playing a different spec. This time there is no way to buy a higher item level version of the ring from the vendors.

So after reading these two paragraphs you should already have a faint idea of what I'm going for with this. Basically Blizzard implemented a nice system that does not cripple players that play many alts, offers smooth and easy to understand upgrading, yet still costs a bit of gold, which is always a goal for them, to keep the economy healthy, and then they decided to not apply it to the most important item of the whole expansion.

I'm pretty sure it is already too late for them to switch the rings over to the better system now, but I hope they read this and learn for the next expansion.

How this should have worked: - At the start of the legendary quest line, you get to chose one ring. If you want to use more than one ring, you have to buy the base version at a vendor. - At each new step quest line, you get an item that upgrades all your unlocked rings to the next level. The vendor now offers the higher item level version for sale. - At the end of the legendary quest line, all your legendary rings are on the same level, if you spent the money at the beginning and unlocked them all. - Now with each raid end boss kill you get an item that, once again, upgrades all unlocked rings by a flat amount of item level. The vendor now offers the higher item level version for sale.

This way you neither punish alt players, rerollers nor dual/tripple spec users and yet still drain some money from the players to keep the economy healthy. Of course there still could be added requirements for how alts are allowed to unlock the rings, like having to complete the quest lines before they can use the upgraded version so alts don’t get everything “for free” without doing anything.

Pretty sure no one @Warcraft read my blog entry [1] but there have been changes to Apexis shards:

Characters will gain triple the amount from eligible creatures during this Bonus Event. Completing several area assault objectives during the event awards a sizable amount of Oil to fuel new Naval Missions as a part of the Shipyard.[2]

[1] http://omgstanposts.tumblr.com/post/113894272248/wow-make-apexis-gear-useful

[2] http://blue.mmo-champion.com/topic/372637-62-ptr-patch-notes-may-13/

Since Skype gets worse with every update, I decided to downgrade to 6.21 and stay there. When you do that, Skype will always tell you that there is an update available in the form of a prompt that looks like this:

To disable it, you need to do a few more things:

1. Open up Skype and go to 

Tools => Options => Advanced => Automatic Updates 

and click the “Turn off automatic updates” button.

2. Open up a command prompt as Administrator and do

sc stop "SkypeUpdate" sc config "SkypeUpdate" start= disabled

Currently you can buy gear for certain slots at special vendors in your factions’ capital city in Ashran. They cost Apexis crystals and are upgradable for another huge crystal cost. You didn’t know about them? No problem, they are way overpriced and you will probably never farm the crystals to buy one.

Let’s look at an example, the head slot:

Base item: Item Level 630 - 5000 Apexis crystals

First upgrade: Item Level 645 - 11500 Apexis crystals

Second upgrade: Item Level 655 - 20000 Apexis crystals

Third upgrade: Item Level 670 - 20000 Apexis crystals

So we are looking at 56500 Apexis crystals for one (1!) item at item level 670. That is insane. 

Now if we assume that you do the Apexis daily every day, which gets you either 800 or 1000 crystals and one follower mission that grants 600 Apexis per day, it takes you around 35 days for ONE (1!) item.

My suggestion is to just drop one of the upgrade steps and cut down the Apexis cost substantially. Also add a new item to the vendors that let’s you reroll the secondary stats of those items because currently they all have suboptimal stats for almost every spec. I know a lot of people in World of Warcraft and none of them even considered ever buying one of those items, be it for their main characters or just lousy alts.