this post was submitted on 19 Jan 2025
44 points (97.8% liked)

Civil Aviation

308 readers
26 users here now

News from civil commercial and noncommercial aviation, videos, discussions, and more.

Basic rules

1. English onlyTitle and associated content has to be in English.
2. No posts about military aviationAvoid any and all posts related to military aviation.
3. No meme postsNo meme posts. Those should go to [email protected].
4. Instance rules applyAll lemmy.zip instance rules listed in the sidebar will be enforced.

Icon attribution

If someone is interested in moderating this community, message @[email protected].

founded 9 months ago
MODERATORS
[email protected]
44
TSA Final Rule: You Will Need REAL ID To Fly In The US Starting On May 7 (simpleflying.com)
submitted 2 weeks ago* (last edited 2 weeks ago) by [email protected] to c/[email protected]
22 comments fedilink hide all child comments
 

The Transportation Security Administration (TSA) has announced that starting in May 2025, following the publication of the final rule regarding the use of REAL ID enforcement across airports in the United States, travelers will have to have identification that meets security requirements.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 2 weeks ago

Thanks. Changed.

I do wish various folks creating protocols would just use URIs and at least try for some consistency across the wider internet. Matrix uses @user:server for people, #room:server for rooms (probably patterned after IRC, which uses #room but, not being federated, has no server part); Lemmy uses !community@server for rooms unless you're following from Mastodon in which case you drop the "!"; and apparently no prefix for user accounts (like email addresses). Just, like, pick a lane. I'm sure it's no issue for people who spend all of their time in one place, but for filthy casuals it can be a challenge to remember what format is used where.

Things aren't confusing enough; let's just pick a random format for every new protocol, rather than adopting an addressing format from a highly adjacent protocol.