The uncommon chance to reply to an old review with fresh content. Via Twitter.
Some days, you just wake up and find some curious tweets bearing quite familiar content out there.
And suddenly it turns into the chance to clarify few old-style misconceptions and outdated facts about Apache Syncope.
Thanks to Alexander Nazarenko for giving me the chance to finally make some clearance.
@aanazarenko @syncopeidm is an #OpenSource prj at @TheASF and everyone is welcome to contribute: can you say the same of its competitors?
— F. Chicchiriccò (@chicchiricco) March 31, 2016
@aanazarenko Barely a (wrong) opinion; at #Tirasa we've been managing million users for several @syncopeidm deployments all around the world
— F. Chicchiriccò (@chicchiricco) March 31, 2016
@aanazarenko This was up to 1.2; with @syncopeidm 2.0 you can define any type on objects and provision natively https://t.co/MKjA4oXdhs
— F. Chicchiriccò (@chicchiricco) March 31, 2016
@aanazarenko Again, this information is outdated as well; @syncopeidm 2.0 defines a whole new security model https://t.co/Vmud36utdL
— F. Chicchiriccò (@chicchiricco) March 31, 2016
@aanazarenko Not exactly; besides parallel and priority-based provisioning, @syncopeidm also supports push tasks https://t.co/V5HBrhfG2c
— F. Chicchiriccò (@chicchiricco) March 31, 2016
@aanazarenko With 2.0 there's ongoing effort for better documentation https://t.co/zfa1FzGZ5J and we do feature the best community support
— F. Chicchiriccò (@chicchiricco) March 31, 2016
Not rated yet 