They recommend not using it to receive a large number of transactions, the actual size of the transaction is not an issue.

Try MultiDoge : http://multidoge.org/?dl=win
It's a light wallet and does not download the blockchain.

It is important to know that MultiDoge is a so called light wallet. It is meant for your day to day transactions. If you are a miner, you should NOT use MultiDoge as your wallet. Receiving big transactions, such as pool payouts, can clog up a light wallet. This is a known issue with all light wallets and must be considered before usage.

The essence is: Do not use a light wallet to handle a big amount of transactions, mining being one example. Use the refrence client instead.

I'd change them to something more secure for you.  You can try adding in that allowip option as well.  Read up on bitcoin or litecoin rpc and api.  Lot's of things you can do to protect yourself and your coins.

Then you have an issue elsewhere.  Firewall, router, something...

I understand.  We all start somewhere.  The 'rpc' functions (or settings as you see them here) are settings so something external (if you want it to) can act upon your wallet (or install of the wallet).  For example, I run a couple of simple games.  I use a wallet install to keep track of each users amount they are playing with.  I use the rpc settings to do this:

rpcuser would be a username that you would use to connect to your install.  It's just like a username here on bitcointalk or an email address you'd log into facebook with.  If you decide to solo mine a coin, you'd use this rpcuser (name) to 'log' into your wallet and start mining on the network.  That's the reason it's there.  You want to set it to something secure (only you'd know) as it can be exploited.  More on that in a sec.

rpcpassword is just what it says.  A password to use in combination with your rpcuser.  Again, set this to something secure.

rpcport is the port number one would use to connect to your wallet.

NONE of these are of any use to you whatsoever when you're synching, so again, don't get hung up on what they do/used for.  Just basic authentication IF you'd ever decide to use it. 

This line
is what I suspect your problem is.  Normally you'd want that in your .conf file as a precaution to keep others out, but at times, i've learned, that it can prevent a wallet from synching.

Try this:

THAT should get you synching... If it doesn't start after 3 minutes or so, do the 'delete everything' trick I outlined above.  KEEP that wallet.dat file backedup .

We'll get you a synching client and THEN you can learn what all this stuff is.

Silva, your rpc user and pass are strings of text that you can make up.  Make them whatever you feel is secure.  At the current difficulty of FLAP I doubt you'll be using them to solo mine, so just make them something secure.  The rest of that file looks good.  If you save this .conf file and restart the flappycoin qt and it still will not begin synching after about 3 minutes, try this:

Go back into your /appdata/roaming/flappycoin dir and backup the wallet.dat file.  Now, CAREFULLY, delete everything (including folders) in the directory BUT the wallet.dat file and the .conf file you just created.  For example, all that should be left when you're done deleting is the .conf file and the wallet.dat file.  Now, restart that flappycoin qt and it should begin synching.

And make sure you have latest version of wallet.

put inflapcoin directory under apps... For temporary solution...

AppData\Roaming\Flappycoin

flappycoin.conf

this text below....

testnet=0
listen=1
addnode=27.3.192.200:11556
addnode=94.22.75.142:11556
addnode=162.243.219.6:46285
addnode=221.121.207.215:11556
addnode=185.27.69.250:57835
addnode=210.229.52.135:1095
addnode=84.229.197.76:4599
addnode=188.40.106.68:35651
addnode=110.169.60.173:60370
addnode=111.98.41.44:61363
addnode=101.226.247.43:50061
addnode=94.208.110.64:11556
addnode=50.178.24.180:52588
addnode=203.174.12.17:62980
addnode=88.82.176.110:11556
addnode=77.173.110.4:11556
addnode=185.27.69.250:52009
addnode=87.11.234.16:64248
addnode=176.116.104.28:65008
addnode=119.125.183.169:51385
addnode=81.234.144.8:11556
maxconnections=100
server=1
daemon=1
rpcuser=yourser
rpcpassword=yourpw

rpcconnect=127.0.0.1


this worked for me