Shay/ticketchain
1
0
Fork 0
mirror of https://github.com/0xShay/ticketchain.git synced 2026-01-11 13:13:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Removed extra bullet point in README.md

Browse Source
This commit is contained in:
Shay Patel
2024-11-23 15:02:58 +00:00
committed by GitHub
parent c2a8f88846
commit f7b27ff600
1 changed files with 0 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@@ -16,7 +16,6 @@ Many popular ticket sites exist, that allow customers to browse different upcomi
- These central services consolidate all of the data and compute for their services in one spot. One possible risk to consider is a cyberattack - if the central organisation is compromised, all customer data is at risk of being stolen and leaked. Another possible risk is the central server going down, meaning ticket services would go down, which is not ideal if thousands of attendees are trying to verify themselves at an event. - These central services consolidate all of the data and compute for their services in one spot. One possible risk to consider is a cyberattack - if the central organisation is compromised, all customer data is at risk of being stolen and leaked. Another possible risk is the central server going down, meaning ticket services would go down, which is not ideal if thousands of attendees are trying to verify themselves at an event.
- Hidden booking fees - Hidden booking fees
- Centralised platforms often impose high service fees which aren't visible when viewing events. This is a lack of privacy issue because it is unclear how ticket prices are determined, leading to mistrust in customers. - Centralised platforms often impose high service fees which aren't visible when viewing events. This is a lack of privacy issue because it is unclear how ticket prices are determined, leading to mistrust in customers.
-
## Proposal ## Proposal