Social & Connections

FlightLeague’s social side is built around logged activity, connections, and discovery. Depending on your setup and activity, you may see areas such as a For You feed, a Friends feed, and empty states that encourage you to add people or share something. The feed can surface public flights from Pilot mode, public trips from Traveler mode, milestones, reactions, comments, and other activity connected to the community layer. It is designed to feel useful even if you use the app mainly for logging, but it becomes much richer once you build connections and share some public activity. If your feed looks quiet at first, that usually means you need more friends, more public activity, or a little more time to build your network.

The Friends feed focuses more directly on activity from people you are connected to, while the For You feed is broader and geared more toward discovery. That means you may see a different mix of content, people, and activity depending on which feed you are viewing. This applies to both Pilot and Traveler mode because it is part of the social layer rather than the logging layer. If you mainly want to keep up with people you know, the Friends feed is usually the better home. If you want to discover more public activity across the community, For You is the more open stream. If either feed feels empty, it is often because you need more connections or more visible activity in your network.

You can discover people in a few different ways, including searching by name, searching by friend code, exploring suggested connections, and reviewing mutual connection suggestions where available. Friend code search is often the most direct method if you already know the person you want to add. Name search is useful when you do not. Both pilots and travelers use the same core connection system, so you can build a network across either mode. Once you find the right profile, you can usually send a friend request from the connections or profile context. If search results feel too broad, try using a friend code instead. It is quicker and reduces the chance of sending a request to the wrong person.

Friend requests let you build a more intentional network inside FlightLeague. When you send a request, it appears as outgoing on your side until the other user accepts or declines it. Incoming requests are the ones other users have sent to you and that you can review from the connections area. Once accepted, the relationship moves into your active connections and can shape what you see in feeds, suggestions, and social context. This works for both pilots and travelers. If someone is already in your connections, you should not need to send another request. If a request seems stuck, it may simply still be pending, or the other person may not have acted on it yet.

Yes, when a flight or trip is public and appears in social contexts, other users may be able to react to it or comment on it. This applies to both Pilot mode and Traveler mode, because comments and reactions sit on top of visible activity rather than belonging to one logging type only. These interactions are part of what gives FlightLeague its community feel. If you would rather keep a specific entry personal, set it to private before saving or sharing it. If you do make something public, expect that it may become part of a broader social conversation. You can usually access comment threads from the activity itself or from related notifications if someone has interacted with your content.

A user profile can show identity details, social handles if they chose to add them, stats, connection context, recent visible activity, and other profile summary elements. What you see depends on what that user has made visible and how their activity is set up. A pilot profile may lean more toward flight and aviation context, while a traveler profile may feel more trip and travel oriented. Both still sit within the same overall profile framework. If a profile looks limited, that does not necessarily mean something is wrong. It may simply mean the user has chosen more private settings, has not completed their profile yet, or has not built much visible history inside FlightLeague so far.

FlightLeague includes tools for managing your social graph, including removing friends and blocking users when necessary. Removing a friend is useful if you simply no longer want that connection. Blocking is the stronger option when you want to stop contact or reduce unwanted interaction more clearly. These controls are typically managed from the profile or connections context rather than from logging screens. They apply across both pilot and traveler use because they are account-level social controls. If you are unsure which one to use, think of remove as a relationship clean-up and block as a safety or boundaries tool. You can also review blocked users later from settings if you need to check or reverse a decision.

An empty or quiet feed usually means one of three things: you do not have many connections yet, not much public activity has been shared in your network, or your own visibility choices are keeping most things private. This is common with new accounts in both Pilot and Traveler mode. FlightLeague includes empty-state prompts to encourage you to add friends, search by friend code, or share activity when you are ready. If you prefer a more social experience, the fastest fix is usually to build a few connections and make selected entries public. If you prefer the app mainly as a personal log, a quiet feed is not a problem at all. It simply reflects the more private way you are using the product.