archive.org

Psst… don’t tell anyone, but: Android development on Element X has now caught up with iOS and we’ve released an early edition of Element X in the Google Play Store.

Since we published our first release of Element X for iOS on the App Store in July, we’ve been swamped with Android users asking how to get involved too; and so now we’re officially making Element X goodness available on both platforms.

As a reminder, Element X is the fastest Matrix client ever - up to 6000x faster than any other Matrix client; and aims to be not just the best Matrix client, but the best messaging app in the world; better than Telegram, WhatsApp, iMessage and other mainstream messaging apps.

In particular, Element X provides instant launch, instant sync and instant login (once your account is warmed up). It also has a far cleaner - more intuitive - interface, making it quicker and delightful to use. Under the hood, we’ve rewritten the engine of the app in Rust, giving spectacular performance and sharing reliability between both iOS & Android.

Now, today’s release isn’t finished yet; it focuses on messaging rather than collaboration use cases (so no filters, threads or spaces), encryption UI isn’t finished, and account registration and management isn’t hooked up yet. However, it’s still very usable as a daily driver for experienced users, and so this is intended as a preview to let more early adopters play with the app as soon as possible (and see how well it performs in the wild!). Meanwhile we’ll be following up with a much broader release once account management is in place in a few weeks.

To use Element X you need a homeserver with sliding sync support (e.g. matrix.org). Support in Element Cloud is coming shortly, and much much more - watch this space! Please let us know how you get on at #element-x-android, and please submit feedback from within the app if you hit any bugs.

cross-posted from: https://lemmy.ca/post/4763702

ghostarchive.org

The Federal Trade Commission is likely to sue Amazon.com Inc. later this month, capping a four-year antitrust investigation into the company, people familiar with the matter said Tuesday.

The antitrust suit is expected to target the online retail giant’s popular marketplace, where third-party merchants, who now account for more than half of the company’s online sales, pay a commission on each sale, according to the people, who asked not to be named discussing the potential suit. Merchants have complained that Amazon unfairly ties access to its marketplace with its logistics service.

The long-expected complaint will be the fourth the agency has filed this year targeting Amazon, stepping up pressure by the Biden administration, which has focused on antitrust and competition as a keystone of its economic policy. FTC Chair Lina Khan, Biden’s pick to lead the agency, has long had the online commerce giant in her sights, writing a seminal paper as a law student about how to rethink the antitrust laws in connection with its online platform.

Top company executives met with the FTC’s three commissioners in mid-August to discuss the suit, though no settlement was discussed, according to the people.

The FTC, which has both antitrust and consumer protection mandates, has been investigating Amazon for potential anticompetitive conduct over several aspects of its business, including its marketplace, Prime subscription service and cloud computing.

In May, the agency sued the e-commerce giant in two separate cases for failing to delete data about children collected by its Alexa speakers and illegally spying on users of its Ring doorbells and cameras. Amazon said it disagreed with the FTC’s allegations, but agreed to pay $30.8 million to resolve the cases.

One month later, the FTC again sued Amazon in a consumer protection case, alleging the company duped consumers into signing up for Prime membership and deliberately made it hard to cancel. Amazon denies the allegations and that suit is ongoing.

The Wall Street Journal reported earlier that the new suit is expected this month.

ghostarchive.org

The Federal Trade Commission is likely to sue Amazon.com Inc. later this month, capping a four-year antitrust investigation into the company, people familiar with the matter said Tuesday.

The antitrust suit is expected to target the online retail giant’s popular marketplace, where third-party merchants, who now account for more than half of the company’s online sales, pay a commission on each sale, according to the people, who asked not to be named discussing the potential suit. Merchants have complained that Amazon unfairly ties access to its marketplace with its logistics service.

The long-expected complaint will be the fourth the agency has filed this year targeting Amazon, stepping up pressure by the Biden administration, which has focused on antitrust and competition as a keystone of its economic policy. FTC Chair Lina Khan, Biden’s pick to lead the agency, has long had the online commerce giant in her sights, writing a seminal paper as a law student about how to rethink the antitrust laws in connection with its online platform.

Top company executives met with the FTC’s three commissioners in mid-August to discuss the suit, though no settlement was discussed, according to the people.

The FTC, which has both antitrust and consumer protection mandates, has been investigating Amazon for potential anticompetitive conduct over several aspects of its business, including its marketplace, Prime subscription service and cloud computing.

In May, the agency sued the e-commerce giant in two separate cases for failing to delete data about children collected by its Alexa speakers and illegally spying on users of its Ring doorbells and cameras. Amazon said it disagreed with the FTC’s allegations, but agreed to pay $30.8 million to resolve the cases.

One month later, the FTC again sued Amazon in a consumer protection case, alleging the company duped consumers into signing up for Prime membership and deliberately made it hard to cancel. Amazon denies the allegations and that suit is ongoing.

The Wall Street Journal reported earlier that the new suit is expected this month.

^archive.org^

Hello again,

Today, rather than discuss one of our upcoming projects, I’d like to share an update about the studio itself and outline our vision for BioWare’s future.

In order to meet the needs of our upcoming projects, continue to hold ourselves to the highest standard of quality, and ensure BioWare can continue to thrive in an industry that’s rapidly evolving, we must shift towards a more agile and more focused studio. It will allow our developers to iterate quickly, unlock more creativity, and form a clear vision of what we’re building before development ramps up.

To achieve this, we find ourselves in a position where change is not only necessary, but unavoidable. As difficult as this is to say, rethinking our approach to development inevitably means reorganizing our team to match the studio’s changing needs.

As part of this transition, we are eliminating approximately 50 roles at BioWare. That is deeply painful and humbling to write. We are doing everything we can to ensure the process is handled with empathy, respect, and clear communication. With that last point in mind, I want to take a moment to explain how we got here, what we’re doing to support our colleagues, and what this means for BioWare’s current and future games.

WHAT’S HAPPENING NOW

After much consideration and careful planning, we have built a long-term vision that will preserve the health of the studio and better enable us to do what we do best: create exceptional story-driven single-player experiences filled with vast worlds and rich characters. This vision balances the current needs of the studio—namely, ensuring Dragon Age™: Dreadwolf is an outstanding game—with its future, including the success of the next Mass Effect™.

We’ve chosen to act now in part to provide our impacted colleagues with as many internal opportunities as possible. These changes coincide with a significant number of roles that are currently open across EA’s other studios. Impacted employees will be provided with professional resources and assistance as they apply for these positions.

While it’s unlikely that everyone will find a new role within the company, we are committed to supporting our staff as they navigate this change. Our sincere hope is that they can continue their exemplary work at studios who stand to benefit immensely from their talents.

IMMEDIATE IMPACT

If you’re wondering how all of this will impact development of Dragon Age: Dreadwolf, let me be clear that our dedication to the game has never wavered. Our commitment remains steadfast, and we all are working to make this game worthy of the Dragon Age name. We are confident that we’ll have the time needed to ensure Dreadwolf reaches its full potential.

I can also tell you that every member of our team, even those departing BioWare, deserves credit for crafting a spectacular experience. These are our colleagues and friends, and we would not be here without them. I am so proud of all the work our team has done.

WHAT COMES NEXT

While this is an extremely difficult day for everyone at BioWare, we are making changes now to build a brighter future. We’re excited for all of you to see what we’ve been building with Dreadwolf. A core veteran team led by Mike Gamble continues their pre-production work on the next Mass Effect. Our commitment to quality continues to be our North Star.

As cliche as this sounds, there truly is never a good time to enact changes like this, but we trust that we have the right leaders and team in place with vision, passion, and proven track records to deliver world-class Dragon Age and Mass Effect experiences that our fans will love.

For now, I want to thank everyone at BioWare—past and present—for making the studio what it is. I also want to thank our community for your continued support. We’re eager to reveal more about Dreadwolf, and we look forward to discovering what else the future holds.

Gary McKay
General Manager, BioWare

Context^piped^^-^^invidious^^-^^lemmy^

There won't be a big WAN Show segment about this or anything. Most of what I have to say, I've already said, and I've done so privately.
To Steve, I expressed my disappointment that he didn't go through proper journalistic practices in creating this piece. He has my email and number (along with numerous other members of our team) and could have asked me for context that may have proven to be valuable (like the fact that we didn't 'sell' the monoblock, but rather auctioned it for charity due to a miscommunication... AND the fact that while we haven't sent payment yet, we have already agreed to compensate Billet Labs for the cost of their prototype). There are other issues, but I've told him that I won't be drawn into a public sniping match over this and that I'll be continuing to move forward in good faith as part of 'Team Media'. When/if he's ready to do so again I'll be ready.
To my team (and my CEO's team, but realistically I was at the helm for all of these errors, so I need to own it), I stressed the importance of diligence in our work because there are so many eyes on us. We are going through some growing pains - we've been very public about them in the interest of transparency - and it's clear we have some work to do on internal processes and communication. We have already been doing a lot of work internally to clean up our processes, but these things take time. Rome wasn't built in a day, but that's no excuse for sloppiness.
Now, for my community, all I can say is the same things I always say. We know that we're not perfect. We wear our imperfection on our sleeves in the interest of ensuring that we stay accountable to you. But it's sad and unfortunate when this transparency gets warped into a bad thing. The Labs team is hard at work hard creating processes and tools to generate data that will benefit all consumers - a work in progress that is very much not done and that we've communicated needs to be treated as such. Do we have notes under some videos? Yes. Is it because we are striving for transparency/improvement? Yeah... What we're doing hasn't been in many years, if ever.. and we would make a much larger correction if the circumstances merited it. Listing the wrong amount of cache on a table for a CPU review is sloppy, but given that our conclusions are drawn based on our testing, not the spec sheet, it doesn't materially change the recommendation. That doesn't mean these things don't matter. We've set KPIs for our writing/labs team around accuracy, and we are continually installing new checks and balances to ensure that things continue to get better. If you haven't seen the improvement, frankly I wonder if you're really looking for it... The thoroughness that we managed on our last handful of GPU videos is getting really incredible given the limited time we have for these embargoes. I'm REALLY excited about what the future will hold.
With all of that said, I still disagree that the Billet Labs video (not the situation with the return, which I've already addressed above) is an 'accuracy' issue. It's more like I just read the room wrong. We COULD have re-tested it with perfect accuracy, but to do so PROPERLY - accounting for which cases it could be installed in (none) and which radiators it would be plumbed with (again... mystery) would have been impossible... and also didn't affect the conclusion of the video... OR SO I THOUGHT...
I wanted to evaluate it as a product, and as a product, IF it could manage to compete with the temperatures of the highest end blocks on the planet, it still wouldn't make sense to buy... so from my point of view, re-testing it and finding out that yes, it did in fact run cooler made no difference to the conclusion, so it didn't really make a difference.
Adam and I were talking about this today. He advocated for re-testing it regardless of how non-viable it was as a product at the time and I think he expressed really well today why it mattered. It was like making a video about a supercar. It doesn't mater if no one watching will buy it. They just wanna see it rip. I missed that, but it wasn't because I didn't care about the consumer.. it was because I was so focused on how this product impacted a potential buyer. Either way, clearly my bad, but my intention was never to harm Billet Labs. I specifically called out their incredible machining skills because I wanted to see them create something with a viable market for it and was hoping others would appreciate the fineness of the craftsmanship even if the product was impractical. I still hope they move forward building something else because they obviously have talent and I've watched countless niche water cooling vendors come and go. It's an astonishingly unforgiving market.
Either way, I'm sorry I got the community's priorities mixed-up on this one, and that we didn't show the Billet in the best light. Our intention wasn't to hurt anyone. We wanted no one to buy it (because it's an egregious waste of money no matter what temps it runs at) and we wanted Billet to make something marketable (so they can, y'know, eat).
With all of this in mind, it saddens me how quickly the pitchforks were raised over this. It also comes across a touch hypocritical when some basic due diligence could have helped clarify much of it. I have a LONG history of meeting issues head on and I've never been afraid to answer questions, which lands me in hot water regularly, but helps keep me in tune with my peers and with the community. The only reason I can think of not to ask me is because my honest response might be inconvenient.
We can test that... with this post. Will the "It was a mistake (a bad one, but a mistake) and they're taking care of it" reality manage to have the same reach? Let's see if anyone actually wants to know what happened. I hope so, but it's been disheartening seeing how many people were willing to jump on us here. Believe it or not, I'm a real person and so is the rest of my team. We are trying our best, and if what we were doing was easy, everyone would do it. Today sucks.
Thanks for reading this.^[https://linustechtips.com/topic/1526180-gamers-nexus-alleges-lmg-has-insufficient-ethics-and-integrity/page/16/#comment-16078641; archive]

Check LinusTech's profile for further discussion and comments he's had.^[https://linustechtips.com/profile/3-linustech/; archive]

I'm used to cloudflared CLI, and would prefer to keep the config files server-side.

My docker-compose.yml file is:

version: '3.9'
services:
  vaultwarden:
    image: vaultwarden/server:latest
    container_name: vaultwarden
    restart: always
    environment:
      - WEBSOCKET_ENABLED=true
    volumes:
      - ./vw-data:/data
  tunnel:
    container_name: cloudflared-tunnel
    image: cloudflare/cloudflared
    restart: always
    command: tunnel --config /etc/.cloudflared/config.yml run
    volumes:
        - ./cloudflared:/etc/.cloudflared

My config.yml is:

tunnel: [tunnelid]
credentials-file: /etc/.cloudflared/[tunnelid].json
ingress:
 - hostname: [mydomain]
   service: http://localhost:80
 - service: http_status:404

I've noticed online people setting an env variable TUNNEL_TOKEN, but since I'm using self-hosted files, my token is a cert.pem.

Another issue however is that when I run this and try to browse to the page, I get the error ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp 127.0.0.1:80: connect: connection refused.

Any assistance would be beloved ♥