Remilia profiles in your app
The profile fields that identify a Remilia account, and how an app shows its name, handle, color, and picture.
Names and handles
The display name comes first, in the familiar site monospace style. The
~handle sits on a quieter line beneath it. A profile-link card can show
view profile on that line, as the live account menu does. Permission
descriptions and app names stay outside the identity badge, so the selected
account is easy to find.
An empty display name falls back to the handle. When both are unavailable, the app shows Account unavailable while it retries and invents no identity. Long names wrap on narrow screens. A truncated name shows its full value on focus, on tap, and on hover.
Display names and handles can change. Account state uses the validated OpenID Connect (OIDC) identity as its key, not a displayed name, handle, or avatar. The badge identifies the account. It does not prove a current permission, trusted consent, or a verified publisher.
Profile fields
These fields come from the profile response. The authenticated profile supplies a logged-in identity control. A public profile read can supply the card of another user.
color is a numeric hue, not an RGB value or a CSS string. An app normalizes a
finite number into the range 0 to 359 before it assigns a CSS property. A missing
or invalid value gets a default treatment. A name hash never replaces a saved
hue, because the name-derived color of chat and the profile preference are
separate conventions.
The name stays readable across all hues. The example uses the hue for the background and the border, with neutral text. Permission state never reuses the profile hue. Active, Removed, and Pending have their own labels and icons. The identity styles use Remilia-Mono, which the access-control kit includes.
Profile pictures
The PFP URL comes from the response, not from the handle. Relative image paths
resolve against https://www.remilia.net. The picture is square, uses
object-fit: cover, and has its size reserved before it loads. The menu card
uses a 31 px square with a 2 px border in the profile hue. A 32 px circle suits
the smaller identity badge in a permission popout.
When the PFP is absent or fails to load, initials or a neutral avatar fill the
same space. The RemiliaNET mark identifies the service and never replaces the
PFP of a user. When the visible name already labels the avatar, an empty image
alt avoids a repeated identity for screen readers.
Account changes
The name, the handle, and the PFP come from the same profile response. On an account switch or logout, the app clears the earlier identity and discards late responses for that account. A failed refresh never leaves the avatar of another account beside the current name.
Example
This card reads the public production profile of Remilia Jackson and shows the returned name, saved hue, and PFP. It uses the mini profile card of the live site, with a square PFP, a cropped seal, the saved color, and a barcode along the bottom edge. When the picture cannot load, the card falls back to initials. The card shows identity without a navigation action.
For the steps, see Add a profile card.
Files
A copy of the kit that your app serves does not receive updates from this site.
