[deleted]
Areweyet
21–30 of 46 posts
Re: Areweyet
#22Re: Areweyet
#23Looks 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.
I would say Mozilla is doing well with speed. Firefox’s DOM traversal is thousands of times faster than chromes.
Re: Areweyet
#24it’s a childish distraction, and a testament to the demise of the org
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.
Re: Areweyet
#25What 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.
Most would agree with you. This is not pleasant.
Re: Areweyet
#26I 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.
Re: Areweyet
#27What 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.
Most would agree with you. This is not pleasant.
areweconsolidatedyet is clearly missing from the list
Re: Areweyet
#28Are we ready to abandon this annoying phrasing - yet?
Re: Areweyet
#29How about an “Are we wireless yet?” for Web Bluetooth.
Re: Areweyet
#30Earlier quoted context omitted.
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.
I'm not talking about updating that wiki page. Rather updating the target websites linked there, obviously.