You don't need to include additional libraries in your project. There are no dependency conflicts. In addition, RestFB is highly portable and can be used in both Android projects and normal Java applications.
Although we provide a standard implementation for our core components, each component can be replaced with a custom implementation. This allows RestFB to be easily integrated into any kind of project. Even Android projects are supported.
TThe RestFB API is really minimal and you only need to use one method to get information from Facebook and one to publish new items to Facebook. We provide default implementations for all the core components, so you can drop the jar into your project and be ready to go.
Our Facebook types are simple POJOs with special annotations. This configuration is designed for ease of use and can be used to define custom types very easily.
Newest Version of the
library is available from RestFB's home on Github.
View the
changelog here.
RestFB is a single JAR - just drop it into your application and you're ready to go. Download it from
Maven Central:
| Philosophy | Stance | |------------|--------| | | No. Revenge treats people as means to an end. | | Utilitarianism | Only if it prevents greater harm and increases overall happiness. | | Virtue ethics | Rarely. Forgiveness is the virtuous path; revenge corrupts character. | | Retributive justice | Yes — punishment should fit the crime, and the victim deserves satisfaction. |
The phrase evokes the idea of revenge as a dessert: delayed, savored, and intensely pleasurable — but potentially unhealthy in excess. While “revenge is a dish best served cold” is an English proverb (likely derived from the 19th-century French phrase “La vengeance est un plat qui se mange froid” ), the Spanish phrase Dulce Venganza adds a crucial layer: the emotional quality of the act . It suggests not just patience, but enjoyment . The Dulce venganza
| Aspect | Bitter Revenge | Dulce Venganza | |--------|----------------|----------------| | Timing | Immediate, hot | Delayed, cold | | Emotion | Anger, rage | Satisfaction, cunning | | Method | Violent, messy | Clever, often non-violent | | Goal | Cause suffering | Restore balance + enjoy it | | Aftermath | Guilt, escalation | Catharsis, closure (often) | | Philosophy | Stance | |------------|--------| | | No
Still, in fiction — and in private fantasies — Dulce Venganza remains irresistible. It is the dessert of the soul: delicious, dangerous, and never quite as satisfying as we imagine. “La venganza nunca es buena, mata el alma y la envenena.” (“Revenge is never good, it kills the soul and poisons it.”) — Spanish proverb, often ignored in favor of the sweet version. | | Virtue ethics | Rarely
But the wisest stories and psychological studies suggest the same truth: the sweetest revenge is often living well . Not as a cliché, but as a strategy — building a life so full that the offender becomes irrelevant.
This write-up explores the concept not just as a literal act, but as a cultural, psychological, and narrative archetype. 1. Introduction: Defining the Term “Dulce Venganza” — literally “Sweet Revenge” — is a concept found in literature, film, psychology, and everyday morality. Unlike brutal, impulsive retaliation (often associated with “amarga venganza” or bitter revenge), Dulce Venganza implies a calculated, elegant, and deeply satisfying form of retribution. The “sweetness” refers to the emotional payoff for the avenger: the moment when justice (or perceived justice) is served, often with irony, poetic balance, or public humiliation of the wrongdoer.
restfb source code is placed on Github and the library itself evolves with the help of many great people. A lot of Github users contribute to restfb. We get many hints and questions, and of course many pull and feature requests. And we'd like to say thank you to everyone who has helped along the way!
The development of restfb is sponsored by these great companies and individuals. If you also like to sponsor us, please check the sponsor button on our RestFB Github page or send us a short note .
Copyright (c) 2010-2025 Mark Allen, Norbert Bartels. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
