Facebook page

[Cristian Marchi]

I know, that was my mistake: I didn't check for an existing one when I 
opened the official page. I'm already in contac with the manager of the 
UNofficial page and I'm also an admin for it. That means I can merge the 
two pages but there are some cons:

- all material in the page with less "likes" will be lost (comments, 
answers, images, news ecc...). Fortunately the likes will not be lost 
but merged.
- the unofficial page has the name "Gnucash" and not "GnuCash" and that 
is not easy changeable. You need to request a name change to fb but is 
not sure it will be approved.
- same as previous point applies to the facebook page url: the official 
one is https://www.facebook.com/GnuCash while the unofficial is not so 
simple.

At the moment I'm posting the GnuCash news to both pages waiting to 
merge them (I don't really know what I'm waiting...!)

Regards
Cristian

Il 06/11/2012 11.28, Geert Janssens ha scritto:
> Although I spend only very little time on facebook, I was curious 
> enough to go searching for the GnuCash facebook page. To my surprise 
> there are two:
> http://www.facebook.com/pages/Gnucash/195886766945?ref=ts&fref=ts
> http://www.facebook.com/GnuCash?ref=ts&fref=ts
>
> The first announces itself as the UNofficial GnuCash page, is the 
> longest around and has 420 likes.
> The second announces itself as the official GnuCash page, is more 
> recent and only has 177 likes.
>
> I suppose that's how facebook works. Anyone can create a page on 
> anything. And someone started a page before any of the developers 
> thought about it. I just wonder if this makes much sense and if 
> possible how to focus this effort to one page. Be gentle with me here: 
> I'm really unexperienced when it concerns social networks ;)
>
> Geert
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
> .
>