Transparency
We believe in being transparent about the services and technologies that power chrrp. Here's everything you need to know about our infrastructure and dependencies.
🔴 Critical Services
These services are essential. If they fail, parts of chrrp stop working.
| Service | Purpose | Provider |
|---|---|---|
| PostgreSQL | Production database (users, tweets, follows) | Railway managed |
| Resend | Email delivery for account confirmation & notifications | Resend (resend.com) |
| Railway | Application hosting & runtime environment | Railway (railway.app) |
| Scaleway Object Storage | Image/avatar storage (S3-compatible) | Scaleway (scaleway.com) — EU-hosted |
⚙️ Important Infrastructure
Core dependencies that power the application:
| Technology | Purpose |
|---|---|
| Sinatra + Rack | Web framework & HTTP server |
| Puma | Application web server |
| BCrypt | Password hashing & authentication |
| Rack CSRF Protection | Security against Cross-Site Request Forgery attacks |
📊 Analytics (Optional)
Privacy-friendly analytics. Can be disabled without affecting functionality:
| Service | Purpose | Provider |
|---|---|---|
| Plausible Analytics | Privacy-friendly web analytics (no cookies, GDPR compliant) | Plausible (plausible.io) |
🔐 Environment Variables
The following environment variables are required in production:
| Variable | Purpose | Required? |
|---|---|---|
DATABASE_URL |
PostgreSQL connection string | ✅ Yes |
RESEND_API_KEY |
Email delivery API key | ✅ Yes |
|
🚧 | |
|
🚧 | |
|
🚧 | |
|
🚧 | |
RACK_ENV |
Application environment (production) | ✅ Yes |
SESSION_SECRET |
Secret key for signed session cookies | ✅ Yes |
WEB_CONCURRENCY |
Puma worker/thread configuration | ✅ Yes |
🌍 Data Residency
- Application & Database: Hosted on Railway (US-based)
- Avatars: Hosted on Scaleway Object Storage (Paris, France — EU-hosted)
🇪🇺 Migration to EU Infrastructure (Scaleway)
We are planning to migrate the full stack to Scaleway (Paris, France) for complete EU data sovereignty:
- Hosting: Scaleway Serverless Containers or Instances (currently Railway, US-based)
- Database: Scaleway Managed PostgreSQL (currently Railway managed)
- Avatars: Already on Scaleway Object Storage ✅
- Email: Evaluating Mailjet (France) or Brevo (France) as EU alternatives to Resend
Our goal is to have zero US-based dependencies and full GDPR compliance by end of 2026.
📜 Twitter Feature History & twttr Status
A comprehensive timeline of every major Twitter/X feature and whether chrrp has implemented it. Vote on what we should build next!
View Feature Timeline & Vote »
📋 Changelog
🤖 The Algorithm™
chrrp offers two timelines on the Public Timeline: Normal (chronological) and The Algorithm™ (engagement-ranked). Here’s exactly how The Algorithm works:
| Signal | Weight | Description |
|---|---|---|
| ★ Favorites | ×3 | Each like adds 3 points |
| ↻ Retweets | ×5 | Retweets are the strongest signal |
| 💬 Replies | ×2 | Conversations boost visibility |
| 👥 Author Clout | ×0.1 per follower | More followers = higher score. The rich get richer. |
| 🕑 Recency | 10 / √hours | Newer tweets get a boost that decays over time |
| ✅ Verified | +10 | Self-verified users get a flat bonus. Of course. |
| 🎲 Chaos | 0–5 random | A random factor so the feed is never quite the same twice |
Formula: score = (favs × 3) + (RTs × 5) + (replies × 2) + (followers × 0.1) + (10 / √hours) + random(0–5) + (verified ? 10 : 0)
Only tweets from the last 7 days are scored. The highest-scoring tweets appear first. Unlike Twitter/X, our algorithm is fully transparent — no hidden signals, no corporate interests, no ads. Just engagement, clout, and chaos.
🛡️ Security
- All passwords are hashed using BCrypt
- CSRF protection enabled on all POST/PUT/DELETE requests
- Email confirmation required for account activation
- Emails delivered via Resend (DKIM, SPF configured)
Last updated: March 2026 | This page is automatically updated when our infrastructure changes.
twttr is a satirical art project and April Fools' joke. It is not a real social network and is not affiliated with, endorsed by, or connected to Twitter, X Corp., or any of their subsidiaries in any way.
This project is a humorous homage to the early days of Twitter (circa 2006) — back when it was still called "twttr" and microblogging was a wild new idea. It is intended purely for entertainment and nostalgia purposes. No trademark infringement is intended.
Looking for the real thing? The official platform formerly known as Twitter is now X — visit x.com for the official service.
