Smaller systems.
Clearer decisions.
The idea, why it matters, and a link to read more from the original publisher.
YOUR PEOPLE. YOUR COMMUNITY.
A focused home for IT people. The conversation that helps. The opportunity through someone you know. A community you join by personal invitation.
One small decision.
A surprisingly useful thread.
A DIFFERENT STARTING POINT
Choose a deliberate space: people admitted personally, opportunities with a connection, and conversations built around the work you care about.
PEOPLE BEFORE REACH
Personal invitations and phone approval make joining deliberate. A short specialist profile gives each conversation a little more context.
An illustrative design comparison, not a claim about every social platform. Invitations support trust; active moderation still matters.
A LITTLE LOOK INSIDE
Pick a part of the community. The same clear format keeps the focus on the person, the conversation, and the next useful step.
The essentials, in the same short format for everyone. Your work, your strengths, and where you can help.
Eight skills. Three relevant roles. Your experience at a glance.Backend engineer
Building reliable services. Happy to talk .NET, architecture, and the first years in engineering.A short role description, the company, and a direct contact. When a member is the referrer, their name and profile stay attached.
Know who shared it. Ask a useful question. Take the next step directly.Open Studio · Illustrative company
Build focused services with a small product team. Practical experience with .NET and APIs.
Share what you learned, ask for help, and keep the replies with the conversation. No group setup required.
Clear threads. Saved posts. Shared experience.We are reviewing our boundaries. What is one change you would make again?
Start with the change that needs three teams to agree. That is usually where the conversation gets useful.
Short English summaries with the original resource attached. Community notices keep meetups, conferences, and useful updates together in Inbox.
Read the essentials. Open the original. Talk about what matters.The idea, why it matters, and a link to read more from the original publisher.
Interactive illustration · Fictional profiles, opportunities and discussions
TRUST STARTS AT THE DOOR
Human-first is a commitment to how the community is run: personal admission, people with context, and active care when something does not belong.
Access starts personally, rather than through an open sign-up form.
A quick approval connects your phone to your account. No password to remember.
A question. An answer. An opportunity. The people make the community.
Invitations, device-bound access, and moderation support a cleaner space. They do not automatically prove identity or make abuse impossible.
THE COMMUNITY, EXPLAINED
A short guide to the current development build. Android and iOS are in development; there is no public download yet.
Find a useful thread, help someone solve a problem, or take the next step through a member connection.
Personal invitationsThe owner sends a personal, expiring invitation. Enter it in the app, then share the verification phrase shown on your phone through your trusted contact with the owner. Access begins after that device is approved.
There is no password, public sign-up or guest access. A code is personal: do not share it. If it is copied, contact the owner to revoke it. Independent phrase verification protects the first activation; an invitation alone does not prove someone's identity.
Feed brings posts and sourced news together. Help keeps questions and replies in clear threads. Jobs keeps opportunities short. Inbox holds community notices and the private-conversation area, whose delivery is still in development.
Create a post, comment, save something useful, or report content needing attention. Hiding a person filters your own feed and attributed jobs; it does not erase their records or block private messages.
A member referral keeps the referrer's name and short profile attached to the job. An ordinary sourced vacancy remains a job without an invented referrer. Each role has a company, short description, and a direct application link or contact.
A referral is a connection, not employer endorsement or a hiring guarantee. Applications happen directly with the listed contact.
The same format works for everyone: a short introduction, up to eight skills, three relevant roles, and an optional HTTPS link to a fuller CV. Keep it useful and easy to scan.
Cached content and drafts remain useful during the approved offline period. Public publishing is confirmed only after the service accepts it; pending work stays pending until then. A private draft is never shown as delivered.
Fresh news, jobs, comments and system notices need a connection. Peer transport, reviewed end-to-end encrypted private messaging, push delivery and encrypted history recovery are future phases.
Use the trusted testing channel supplied with your invitation. Include the app version, phone and operating system, the screen, and a short explanation of what happened. Never send invitation codes, tokens, keys, or other members' private information.
There is no public store listing or public support address yet. Real support and privacy contacts will be added before public account use.
PLAIN LANGUAGE, FROM THE START
Pre-release information for v0.5.1. Privacy, retention and deletion details must match the final service before public account use.
This page is entirely static. It has no registration form, cookies set by the page, tracking, remote scripts or connection to the app service. The scenes use fictional people and content.
Normal hosting may process connection information such as IP addresses and request logs. Hosting log retention is an operator configuration, separate from this page. External links open websites with their own privacy practices.
The service keeps the invitation email, stable account identifier, approved device and session records needed to manage access. Profiles, posts, comments, saved references, reports, personal hide preferences and community notices are service-held account records.
Only approved devices can access the community. Shared content can be copied or saved by its audience. System notices and their read state are server-stored notices, separate from future encrypted private chat.
Contact the owner through your trusted channel. Replacement is manually verified and keeps the same account. When approved, previous devices and sessions are revoked; server-held profile and community records stay with you.
A new invitation cannot restore unsynced drafts or unavailable encryption keys from a lost phone. Recoverable encrypted backup and key recovery are still being built. A disconnected device cannot receive immediate revocation or a remote wipe.
Local storage is separated by account. Private drafts are encrypted on the phone; that local protection is distinct from a completed end-to-end messaging service. Clearing app data or losing the phone can lose local work.
During development, contact the owner through your existing testing channel about data. Complete export, account deletion, retention, backup expiry and public request routes remain release work. Content removal is not a promise of permanent erasure from all caches, backups or copies held by others.
Con2Peer
Being built for Android and iOS. Access will remain by invitation.
Read the community guideNo public download yet. Private-message delivery, peer transport, and encrypted history recovery are future phases.
Data & recovery details ↗