• 44 Posts
  • 213 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle
  • It’s been an incredibly slow churn to progress.

    The most noteworthy thing at yesterday’s hearing was a report on a Unclassified secret access program - Immaculate constellations which outlines types of UAPs and their behavior. The problem is it’s brought in via an unverified source, either current or former member of the DoD. Also it’s improperly formatted for a DoD doc. But that can possibly be explained via them editing it for public use. Otherwise it was mostly just what’s already been known just told under oath in an official context. It also has a much greater emphasis on USOs(underwater UAPs).

    The most interesting and ironclad to come from everything so far has been Schumer’s Unidentified Anomalous Phenomena Disclosure Act of 2024 (UAPDA) which is attempting to get passed with the NDAA (Annual defense act). In the act it lays out the groundwork for UAPs existence and that the government is in charge of both reconnaissance and recovery of them, and most of the secrets are held behind the Department of Energy.

    A lot of Chuck Schumer’s comments and amendments play relatively safe though saying “if this exists” then here’s a law. But there was also a lot of work put into a 2023 UAPDA with that NDAA and actually got shot down by Republican military industrial complex lackeys so take from that as you will.

    The 2023 amendment was fought over heavily because it required a return of all classified uap biological materials and non biologics to be returned to the US government from private contractors. Which is another big bullet point.

    I think the most news we’ll get soon is whether the 2024 version of the UAPDA is included in the NDAA this year.













  • Open protocols and APIs seem pretty meaningless to me if there’s a single point of control for the brand.

    You’d need to expand on this more for me to understand you. Yes there’s a single point of control from a moderation standpoint (labeler), as there is on Lemmy instances. But anyone can host their own ATProto relays and the Bluesky relay will federate with each other automatically.

    If everyone migrates to bluesky and then bluesky says “of we’re not doing that open thing anymore because of this new embiggened thing we’re doing” everyone will still be on bluesky.

    Not necessarily because the accounts are atProto accounts and you can migrate to another platform(albeit another doesn’t exist yet) without data loss. As far as the Bluesky app goes it really just shows you atProto posts and hosts your data (similar to Lemmy instances) they as an entity just also maintain the OSS backend Relay crawler and more.

    I really think a lot of people have this perspective that it’s not decentralized just because it truly is a lot more complicated due to there being like 5 different moving pieces of decentralization (PDS, Relay, Appview, tbd labeler, algorithm) and they do a great job at obscuring it for regular users which is a great thing. And nobody has really tinkered around and set-up any sites or integrations with it yet. I’m personally trying to get a two way mastodon integration as it’s possible but nobody has done a solid implementation (just somewhat gnarly bridges between protocols)


  • This isn’t necessarily true. Just because their architecture is harder and not a simple server host does not strip away its decentralization.

    They have decentralized the following:

    • App access (can build your own or show openProto posts in your platform

    • Algorithms

    • Relay (backend albeit rumored to be expensive)

    • More if you consider the domain name hosting stuff and media storage control. Also moderation is planned to be decentralized.