src/plugins/WebOfTrust/WebOfTrust.java

@@ -1351,7 +1351,7 @@ public synchronized boolean verifyAndCorrectStoredScores() {
 	 * 
 	 * ATTENTION: Must be called before the {@link SubscriptionManager} is initialized: It doesn't
 	 * leave the SubscriptionManager event database in a correct state. Initialization of the
-	 * SubscrptionManager will flush its database and fix that.
+	 * SubscriptionManager will flush its database and fix that.
 	 * 
 	 * ATTENTION: This function can cause OutOfMemoryError since it puts all existing Identity /
 	 * Trust / Score objects in large HashSets instead of iterating over the result of a database
@@ -1369,7 +1369,8 @@ public synchronized boolean verifyAndCorrectStoredScores() {
 	 *    Before this can be done, please however convert all callers of this function to work with
 	 *    the new behavior. This especially applies to the upgrade code for old database formats
 	 *    which uses this function - it can likely be removed if the newer database format versions
-	 *    were deployed in an official release a long time ago already.
+	 *    were deployed in an official release a long time ago already. (Edit: Actually I think it
+	 *    doesn't use this function, I think it merely links it from the JavaDoc.)
 	 *    Alternate solution: Amend startupDatabaseIntegrityTest() of all classes which require
 	 *    uniqueness to check whether another object with the same ID exists. This should be
 	 *    benchmarked though as O(N) queries for an ID could be very slow if the database queries
@@ -3393,8 +3394,7 @@ public Vertex(Identity identity, int rank) {
 		// used to amend a non-sorting queue to be able to handle the few cases of MAX_VALUE which
 		// need sorting?
 		PriorityQueue<Vertex> queue = new PriorityQueue<Vertex>();
-		// Use IdentityHashSet because Identity.equals() compares more than needed.
-		IdentityHashSet<Identity> seen = new IdentityHashSet<Identity>();
+		IdentifierHashSet<Identity> seen = new IdentifierHashSet<Identity>();
 
 		final int sourceRank;
 		try {