readme updates

README_goals.md

@@ -34,14 +34,14 @@
  * Integration with RSS feeds, for reading news or blogs
  * Moderation capabilities for posts, hashtags and blocks
 
-**Features which won't be implemented**
+## Non-goals
 
 The following are considered anti-features of other social network systems, since they encourage dysfunctional social interactions.
 
  * Features designed to scale to large numbers of accounts (say, more than 20 active users)
  * Trending hashtags, or trending anything
  * Ranking, rating or recommending mechanisms for posts or people (other than likes or repeats/boosts)
- * Geo-location features
+ * Geo-location features, unless they're always opt-in
  * Algorithmic timelines (i.e. non-chronological)
  * Direct payment mechanisms, although integration with other services may be possible
  * Any variety of blockchain
@@ -49,4 +49,6 @@ The following are considered anti-features of other social network systems, sinc
  * Enterprise features for use cases applicable only to businesses. Epicyon could be used in a small business, but it's not primarily designed for that
  * Collaborative editing of posts, although you could do that outside of this system using Etherpad, or similar
  * Anonymous posts from random internet users published under a single generic instance account
- * Hierarchies of roles beyond ordinary moderation, such as X requires special agreement from Y before sending a post
+ * Hierarchies of roles beyond ordinary moderation, such as X requires special agreement from Y before sending a post. Originally delegated roles were envisioned, but later abandoned due to the potential for creating elaborate hierarchies
+ * Federated blocklists. Initially this seems like a good idea, but the potential down sides outweigh the benefits. eg. Two allied instances share their global blocklist. Some time later one instance is transferred to an adversary, or gets hacked. Adversary can now control your global blocklist and trash your instance very quickly that way.
+ * Federated moderation. Again, seems like it might be beneficial initially. Share the burden of moderation. But under realistic conditions people could be pressured or bribed into giving federated moderation access, and the consequences could be very bad. Individuals going on power trips, controlling multiple instances and heading back towards centralization.

README_roadmap.md

@@ -6,8 +6,9 @@
 
 ## Groups
 
- * Unit test for group creation
  * Groups can be defined as having particular roles/skills
+ * Parse posts from Lemmy groups
+ * Think of a way to display groups. Maybe assign a hashtag and display them like hashtag timelines
 
 ## Questions
 
@@ -19,6 +20,7 @@
 ## Code
 
  * More unit test coverage
+ * Unit test for federated shared items
  * Break up large functions into smaller ones
  * Architecture diagrams
  * Code documentation?