ViperActual

On January 2, 2024, we launched to orbit our first six Starlink satellites with Direct to Cell capabilities. Launch and early tests of the technology were all completed without issue. On Monday, January 8, less than 6 days after launch, we sent and received our first text messages to and from unmodified cell phones on the ground to our new satellites in space using TMobile network spectrum. This validates that our link budget closes, and the system works!

I'm excited for this service as it'll be the most tangible rollout of new technology enabled by SpaceX's rapid launch approach to satellite mega-constellations to most people.

Scrolling to the top of a new post screen erased any post body you may have typed if you scroll back down. This only happens if you happen to have a tall image that you've uploaded to post. Normally the entire page displays without scrolling, which is why it may have gone unnoticed.

I was looking at the thread for Sync because I was wondering how the same issue might be handled in Connect. Seems like it has the same issue. RIF handled this by having a view more button that displayed child comments in a separate view once the nested levels hit a certain threshold so they weren't smushed against the edge of the screen.

Currently, Connect will ask if you'd like to open a clicked URL. You only have yes or no options.

Adding a copy URL button would prevent having to view the page in order to access the copy URL option from there.

Adding the standard share button isn't as useful to me since I'm only trying to share URLs to friends. But I noticed the lack of this when I'd backed out of a page and figured I'd share it. But ended up having to view it again just to do so.

This would be a local app-managed setting that adds a toggle to each community.

When enabled, this toggle allows all of the posts from that community to be combined with all other communities of identical name, from other instances under a common category name.

Because this is a per-community toggle, this lets you filter out communities of identical names from an instance you may be on, that you want to exclude from this category.

For example, enabling this setting on the identically named (and themed) communities of [email protected] and [email protected] would combined all content from both communities together under a single category called Fediverse.

If there were another instance with a community of the same name but of a different topic, then leaving this toggle disabled for that community instance would exclude it from this category.

Categories can then be treated like communities in the subscribed community list, under a separate section just like how communities are split between All/Local.

___

As an additional bonus, the app could ask the user if they would like to consolidate identically named communities. It would then provide a list of these identically named communities, with checkmarks beside them to quickly toggle this setting.

To reduce spam, if a user wanted to submit a post to this category, they would have to specifically select the community instance they wanted to post to.

___

Lastly, if this idea of more app-managed consolidation is taken to the extreme, then perhaps allowing users to combine multiple accounts together across each instance could be possible. Where even if two instances defederate, if the user has an account on both instances, they can still view the content as normal. Perhaps this could be called global mode, where accounts only interact with the specific instance they exist on, but combines local feeds from each account/instance together.