Clients could interpret this value however they'd like, but basically the idea is that anybody that establishes their own service on the Atmosphere in the future doesn't feel suffocated by the restrictions of the current schema "standard."
3. Using a percentage value means two things: you're not restricting the value's identity as "not going" "interested" "going" and instead, each client can definite it in a way that it wants to. It also provides the ability to add more options, like "likely going" being 75%.
2. "Hybrid" means both at the same time for attendees, not one or the other. Having it be an array of values is a beneficial change, since it introduces the ability to have both in-person *and* virtual events at the same time (think livestreams or a meeting)
No, unfortunately I am not a programmer by any means. I can describe the use case of each defined point though:
1. Switching to a length of time, as opposed to using an end date, would make it significantly easier to prevent events that end prior to the start date, since it is always positive.
I've just posted a GitHub Discussion on @lexicon.community's lexicon repository, in order to redefine parts of the calendar Lexicon schemas, which theoretically will benefit everybody on the Atmosphere, like @openmeet.net, @smokesignal.events and @atmo.rsvp.
github.com/orgs/lexicon...
I ended up redoing the sculpt and I'm so much happier with what I have now, compared to what it looked like a month ago #3d #blender #modelling #vrchat
I ended up redoing the sculpt and I'm so much happier with what I have now, compared to what it looked like a month ago #3d #blender #modelling #vrchat
Reserving your handle is significantly better than somebody later down the line deciding to impersonate you and instil false impressions onto others on a platform you don't even agree with
You can basically self-host every single component of Bluesky on the AT Protocol already!! People were still on Bluesky when they were using blacksky.community because it's an alternative implementation of the "AppView"
I nominate myself, though I doubt I'd get past all of the very talented individuals here considering I haven't been able to find work in UX/UI yet and ended up resorting to contributing solely to open source projects like Roomy and Home Assistant...!!
Everybody could at the very least just wait until they release the post-mortem for the outage that just happened literally yesterday. It's not that deep. They literally disclosed *multiple times* that it was a DDoS!!
Y'all are being gaslit into believing the vibe-coded themselves to death during the outage that just happened. Let me give you three points why that's highly unlikely:
- It took them roughly 14 hours to resolve the outage,
- They went down suddenly without warning,
- Multiple services went down!!
@pfrazee.com I'm trying to delete this post, and according to pdsls.dev, it's not on my PDS anymore. But the post below is clearly still available, so I'm really not sure what's going on! It also seems like some of my posts recently were "resurfaced" onto the relay, meaning the timestamps are wrong.
Genuinely really cool but nothing beats pangolin.net tbh 🔥
My take on this issue is that it's a necessary evil until the protocol is established and people recognize and understand what it does. Because otherwise, you'll just end up confusing people into thinking your platform doesn't even support "Bluesky" accounts
You could try the For You feed!
And I can't recommend enough projects like @tangled.org, @npmx.dev, @openmeet.net and @roomy.space, that are building a promising future of decentralized web.
But Bluesky isn't *just* Bluesky, there's so much more to it. It's running on the AT Protocol, which is decentralized, which means this account I'm on right now isn't even on Bluesky's servers. ;)
A few sites I recommend are @iame.li's stream.place, @rude1.blacksky.team's blacksky.community,
Try this, if you haven't already.
Yeah the fact I could log into blacksky's app with eurosky data while bluesky was down means that old criticism of ATPro is definitely for the bin.
The future of the technology is definitely not cloud infrastructure though. It's incredibly harmful shit. We should focus on the fact that these AI cloud companies think it's okay to ruin peoples' lives in order to become as powerful as Google, and the ones that are replacing workers with AI.
But that's inherently "AI" because it's just a buzzword for neural networks. 😅
I agree. Low quality code due to individuals programming with reckless abandon, rather than ensuring what they wrote actually makes any sense, is absolute garbage. But there are real, genuine uses for the technology.
Clearly the AI agents will replace every job, and nobody will be required to work because CEOs can just tell a group of artificial intelligence agents to "build me the next Microsoft"! 🤣
lol I agree. But at least this time it isn't "unemployment is inevitable and you will waste away with the sands of time" and instead it's "you'll be replaced but we can just pay you for not working" lmaoo
at least they're saying "we should just pay people to do fuck-all while AI takes our jobs"
The post quite litrerally says "...despite ongoing Distributed Denial-of-Service (DDoS) attacks." Please just read for a moment before saying something's untrue! They're still going through the attack right now.
They're actively being DDoSed according to the dev team
okay cool. mentions are broken
I'm not sure why, but according to @rose.bsky.team they're being absolutely battered by a denial-of-service attack (I assume a distributed one, specifically) but they haven't appeared to mention this on @status.bsky.app for some reason, I'm not really sure why because this is hurting their rep badly
This one wasn't actually on them, they were DDoSed (that's why it wasn't possible to access other AT Protocol apps like Leaflet, Roomy, Whitewind, Blento, etc.)