---
# System prepended metadata

title: Bristol Worksprint

---

# Bristol Worksprint

## TODO

- [x] Decide on feature scope for post view
- [x] Write down pros / cons of link ontology with literals vs Entry objects
- [x] Make proposal for Entry interface
- [x] Move all data methods from flux ui into utils
- [x] Move all data types from flux into utils
- [x] Cleanup fetch/creation functions
- [x] Write prolog parsing function 
- [x] Create ui and methods for getting and creating forum posts 
- [ ] Get holochain binaries working an all machines
- [ ] linkMutation method on ad4m & languages
- [ ] Filter posts by most popular and latest
- [x] Ad4m-connect should download ad4min automatically for given users machine using latest ad4m release
- [ ] Error showing when starting ad4min even if no error 
- [x] Try/catch around expression get
- [ ] ad4m-connect uses the new runtimeInfo agent data when doing its shit
- [ ] Should neighbourhood meta information be static?
- [ ] Do rename of neighbourhood/perspective API (publishFromPerspective)
- [x] Local links should be added to a neighbourhood so we can store flux specific local information about the community
- [ ] Offer tiptap editor as webcomponent
- [ ] CommunityState should be removed, when we have local links and dont need LocalCommunityState
- [x] Username does not populate on signup flow
- [ ] images should be compressed before uploading
- [x] hydrate state should run in the background and not block the rendering

---

## Code Guidelines

- Any places where multiple ad4m calls are made to make some flux action should be as their own function in utils/api
    - or if your method is making some actions to create a result in Flux specifically
- timestamp not createdAt
- author not creatorDid
- community not neighbourhood, when refering to a community in Flux (community defined as a perspective with flux community links)

---

## Forum Spec
- When creating a channel you define the initial view to init this channel; but can be extended later
- Each channel has a tab to switch between message view and forum view
- Messages can be converted to exist in forum view, or forum posts can be converted to exist in message view
- Forum messages can be upvoted by given community tweak emoji which would sort the results of forum posts
- Forum messages can be sorted by last created
- Forum posts contain rich text

## Spec (extra)
- Channel navigation displays the associated views below the channel name
- Global forum view can be seen to get all forum posts across all channels
- Global messages view can be seen to get all forum posts across all channels
- Community tweaks can be set per channel 
    - community tweaks can be used to set which channels messages are pulled from
- Images and other file types in the chat view
- (optional) images & links

---

## Bugs from refactor / test

- Community data does not load on join but only on refresh
- Forum post Entry methods
- Prolog queries for forum posts
- Entry API for channels?
- Replace all SDNA predicates with const values
- Dexie store does not duplicate cache values