Areweyet(wiki.mozilla.org)
wiki.mozilla.org
Areweyet
https://wiki.mozilla.org/Areweyet
16 comments
What an awful format. We couldn't have just had a centralized site?
I like the gimmick. I don’t think I would have bothered checking any of this otherwise and I’m in the field.
That's probably being addressed with the "Are we meta yet?" Project that is listed.
One really nice AreWeYet that's missing from this list is http://areweplayingyet.org/ from the time when HTML5 was all new and most of the web was still Flash audio players. Even includes a test suite, which is broken nowadays because audio codecs in browsers have moved on :)
This is a wiki, so if you know of some sites that should be listed add them!
Strangely, no entry for IsItYet or HowLongUntil - which deal with such timeless popular topics as Christmas and Burning Man.
AreWeTHEREYet
It's amusing how many of the websites are broken due to certificates or outright squatted.
I clicked on one at random, "arewesmoothyet". It linked to blogspam about how to get started with affiliate marketing.
I guess the site got hacked. The table lists one "Doug Thayer" as the owner, but without contact information...
Edit: found an email address, notification sent.
Edit: found an email address, notification sent.
arewedefunctyet?
arewebankruptyet?
arewebankruptyet?
Looks like the initial concept got lost in translation. The original “arewefastyet” was created to focus relentlessly on one single goal and be accountable by making it public.
If you have fifteen of those hidden under funny URLs you’re kinda missing the point.
If you have fifteen of those hidden under funny URLs you’re kinda missing the point.
I'm not sure if you're saying that (say) "Asynchronous I/O in Rust" should be tracked by arewefastyet.com or that "Asynchronous I/O in Rust" should not be tracked by any website at all, because neither of those make sense.
I think the argument is that if tracked it should not be done on a website using the branding of the original campaign because doing so dilutes the original brand?
I would say Mozilla is doing well with speed. Firefox’s DOM traversal is thousands of times faster than chromes.
Depends on what you're trying to do. For my app Firefox is so slow that it's unusable until https://arewewebrenderyet.com/ is rolled out on all platforms.
Considering the page is not even working I'm not very hopeful.
Considering the page is not even working I'm not very hopeful.
Different people have different specialisms, and they each have their own goals.
[deleted]
Forced unfunny meme.
Trying to do everything in Rust is a trap for some people, I remember I once tried using yew to make my static personal site in Rust and wasm. Thanks for my time writing Rust now I have much better understanding of choosing the right tool for the right task.
I think using any client-side WASM framework for a public website is a pretty bad idea right now. I wouldn't even use Blazor from Microsoft, which has a lot more funding than Yew.
Yeah, I think it depends, for high-interaction web apps and games it's fine, but for content based sites it's very unnecessary and hurts accessibility.
[deleted]
it’s a childish distraction, and a testament to the demise of the org
Most companies have old/unmaintained wiki sites. That doesn't mean the organization is dead.
Care to expand?
That they even had resources working on this says a lot
https://wiki.mozilla.org/index.php?title=Areweyet&action=his...
Since it's mediawiki we can view the history of updates; Having less than 5 updates every year means this is probably only an afterthought when someone comes across an "are we ... yet" site. There's not someone at Mozilla whose only job is to track them down.
Since it's mediawiki we can view the history of updates; Having less than 5 updates every year means this is probably only an afterthought when someone comes across an "are we ... yet" site. There's not someone at Mozilla whose only job is to track them down.
What suggests to you that those were "resources working on this" and not just people, inside or outside of Mozilla, doing that because they thought it was funny or interesting?
Judging from how infrequently it's maintained and the many broken links, I think it's safe to say nobody is being paid to edit this part of the wiki.
What a waste of domain space (yes, I know they're abundant, but still.) areweaudioyet.com says nothing about its contents. areweasyncyet.rs had the right idea with the .rs domain name, but anyways, I feel like all of these would be better organized on one wiki, with one list for each category. Easier to search, edit, and hyperlink.
Who cares? There’s virtually infinite opportunities for domain names - unless you think there are better, more legitimate uses for the phrase “are we audio yet?” And it’s not like domain abandonment isn’t already handled by ICANN.
When I click a link, I want to know where I'm going. Where do you think "arewesmoothyet.com" will take you? If you guessed some Mozilla related thing purely from context, well you're also wrong. It's actually some WFH/affiliate marketing course. This was my point; domains are expensive and temporary for people who don't care. Because of this stupid joke, people actually interested in "Firefox Nightly hang telemetry visualization" or whatever have nowhere to go. One wiki, one page per topic, is all you need.
Also about half of the domains are down at this point...the smart one hoated itself on github.
The Republic of Serbia is probably async enough already…
Most would agree with you. This is not pleasant.
first two links I clicked on didn't work. Low effort post.
[deleted]
I noticed a link for distributed/peer-to-peer. https://github.com/arewedistributedyet/arewedistributedyet
I am working on a Node/browser app that solves for this. The idea is to invert the web, which is inherently public, and you get an experience that’s inherently private. With privacy you can do things that aren’t possible or healthy on the public web.
It works out of the box if both end points are IPv6 but IPv4 will require some additional service support to work outside of private networks, due to NAT.
The application is currently just a file sharing tool but soon it will have a text message component. It’s about to achieve fully distributed test automation in the browser, which is a necessary maintenance tool to test the application using user events and DOM navigation across multiple computers for distributed end-to-end tests. If I modify the architecture of the application to support loading and unloading of external components then the application becomes a micro operating system, but this requires many security considerations I have not explored.
https://github.com/prettydiff/share-file-systems
Please keep in mind this application is highly experimental.
I am working on a Node/browser app that solves for this. The idea is to invert the web, which is inherently public, and you get an experience that’s inherently private. With privacy you can do things that aren’t possible or healthy on the public web.
It works out of the box if both end points are IPv6 but IPv4 will require some additional service support to work outside of private networks, due to NAT.
The application is currently just a file sharing tool but soon it will have a text message component. It’s about to achieve fully distributed test automation in the browser, which is a necessary maintenance tool to test the application using user events and DOM navigation across multiple computers for distributed end-to-end tests. If I modify the architecture of the application to support loading and unloading of external components then the application becomes a micro operating system, but this requires many security considerations I have not explored.
https://github.com/prettydiff/share-file-systems
Please keep in mind this application is highly experimental.
Are we ready to abandon this annoying phrasing - yet?
How about an “Are we wireless yet?” for Web Bluetooth.