Prompted by DEFCON 31
https://www.figma.com/file/Y8BdOLeo2PZdFESD3Qzhl2/Pi-Relay-Marketing?type=design&node-id=0%3A1&mode=design&t=m9L60iLi34odYfD6-1

https://www.figma.com/file/Y8BdOLeo2PZdFESD3Qzhl2/Pi-Relay-Marketing?type=design&node-id=0%3A1&mode=design&t=m9L60iLi34odYfD6-1

Conducting an Audit for Pi Relay

If you're new to the project and looking for a way to contribute, conducting an audit in your area of expertise can be immensely valuable. Below are some areas where audits can be conducted, along with guidelines on how to proceed:

Usability Audit

1. Interface Design: Assess the intuitiveness of the interface. Is the navigation straightforward? Are the buttons and links clearly labeled?
2. User Experience: Install and use the app. Are there any pain points or areas where the user might get stuck?
3. Consistency: Check for consistency in design elements like colors, fonts, and layout across different pages.
4. Feedback and Error Messages: Ensure that the system provides clear feedback and guidance to the user, especially in case of errors.
5. Report: Document your findings with screenshots and specific examples. Suggest improvements where necessary.

Security Audit

1. Vulnerability Scanning: Use automated tools to scan for vulnerabilities like SQL injection, cross-site scripting (XSS), etc.
2. Code Review: Manually review the code for potential security issues, such as improper handling of user data.
3. Authentication and Authorization: Verify that the authentication mechanisms are robust and that users have appropriate access levels.
4. Data Encryption: Ensure that sensitive data is properly encrypted both in transit and at rest.
5. Report: Create a detailed report of your findings, including potential vulnerabilities and recommendations for mitigation.

Accessibility Audit

1. Compliance with Standards: Check if the application adheres to accessibility standards like WCAG (Web Content Accessibility Guidelines).
2. Screen Reader Compatibility: Test the application with screen readers to ensure it is navigable and readable.
3. Keyboard Navigation: Ensure that all functionalities are accessible via keyboard.
4. Color Contrast: Assess if the application has sufficient color contrast, especially for text.
5. Alt Text for Images: Verify that all images have appropriate alternative text for screen readers.
6. Report: Document your findings with examples and suggest any necessary changes to improve accessibility.

Writing Audit

1. Clarity and Conciseness: Check for clear and easily understandable text.
2. Consistency and Style: Ensure tone, style, and terminology are consistent.
3. Grammar and Spelling: Look for grammatical errors or typos.
4. Technical Accuracy: Verify accuracy of technical information.
5. Localization and Internationalization: Review content for proper localization.
6. Report: Document findings and suggest improvements.

Performance Audit

1. Load Time: Evaluate application load times and interactivity.
2. Resource Utilization: Assess CPU, memory, and network usage.
3. Optimization: Identify areas for performance improvement.
4. Scalability: Test how the application handles increased load.
5. Report: Provide analysis with metrics and recommendations.

Code Quality Audit

1. Code Structure: Review code organization and structure.
2. Best Practices: Assess adherence to coding standards and best practices.
3. Redundancy and Efficiency: Identify redundant or inefficient code.
4. Documentation: Check the quality of code comments and documentation.
5. Report: Offer insights and improvement suggestions.

General Guidelines for Auditing

• Detailed Reporting: Provide clear, actionable feedback in your audit report.
• Reproducibility: If you find issues, include steps to reproduce them.
• Prioritize: If you identify multiple issues, prioritize them based on impact.
• Be Constructive: Focus on providing constructive feedback that can help improve the project.
• Follow-up: Be open to discussing your findings with the maintainers and other contributors.

Your audits are crucial in helping us improve Pi Relay. We appreciate the time and effort you put into examining our application thoroughly in your area of expertise.

Which 2.13-inch Eink Waveshare is Recommended?

First of all, I am a complete beginner with tor and raspberry pi. However, using your script I was able to start a middle relay and monitor it with Nyx.

I then ordered the recommended Waveshare display, connected it via their docs and successfully ran their python demos. Next, I came back to this site and ran the e-paper setup script which appeared to run successfully and rebooted. Once I rebooted I started the tor service, verified it was up using Nyx, but the display has not shown any data.

1.) Is there any special command to run once the Pi is rebooted to start the display?
2.) If not, do you have any tests/commands/logs that I can run to help me troubleshoot?

Thank you very much for Pi-Relay.. it is exactly what I needed to start my relay.

Only allow alphanumeric characters.

Problem:
Right now the screen doesn't communicate if the device is online, but only if the app is running. This can lead to users running the service without knowing it's unreachable.

Potential Solution:
A wifi signifier in the same pattern as smart devices and personal computers.
Full strength: ---
Medium: --
Weak: -
None: /