Search

Major Update Highlights

• 64-Bit Support: Enhance your gaming performance and stability with our transition to 64-bit architecture.
• New Boss Units:
  • Double the Challenge: Confront two powerful new boss units, each offering unique gameplay experiences.
• Station Unit:
  • Introducing the New Station Unit: Expand your strategic options with this innovative addition.
• Shield Upgrade:
  • Fortified Defense Mechanism: Upgrade your shields to improve defense capabilities against formidable foes.
• Background Graphics:
  • Infinite Cosmic Space String: Enjoy a stunning visual experience with our newly designed infinite cosmic space continuous string in the backdrop.

Prepare for an upgraded adventure that combines enhanced visuals and intense challenges. Dive into the action and explore all these exciting new features!

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/ufos by /u/theuforecord on 2025-03-15 16:44:58+00:00.

Some context before I get into the update. In 2024 a lobbyists at one of the top law firms in the world posted a newsletter warning defense contractors about the UFO Disclosure Act in the NDAA and advocating a proactive approach to prevent the law from passing in its original form. This was noteworthy for several reasons: the firm represents the biggest corporations in all industries, Stephanie Barnas top client ATI facilitates billions in SAP research projects with defense contractors, academia government agencies. Barna was also the lawyer for the committee that passes the NDAA in the senate. While she was the Armed Services Lawyer, Eric Davis and others briefed the commi

If code that can be directly compiled and executed may be suppressed under the DMCA ... but a textual description of the same algorithm may not be suppressed, then where exactly should the line be drawn?

Wikinews is a project which aims to collaboratively report and summarize news on all subjects from a neutral point of view. This page describes the project goals, and outlines basic requirements for the project. There will be Wikinews communities in many languages.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/tifu by /u/HearMeOut-13 on 2025-02-14 15:51:13+00:00.

TL;DR: Spent an entire night trying to use an API that literally does not exist, then had to build the entire thing myself out of pure spite.

So, there I was at 1:17 AM, diving into what was supposed to be a simple integration with a text-to-speech model. The documentation looked pristine - detailed endpoints, clear examples, everything a developer could dream of. Seemed like a quick job.

NARRATOR: It was not a quick job.

The Debugging Descent into Madness:

What followed was a multi-stage descent into technical hell that would make Dante's Inferno look like a pleasant stroll:

1. The Gradio Version Roulette First, I discovered Gradio's API parameters are a

A distributed streaming platform that can run on Raspberry Pi 5.

Last October, at a conference we shared a demo running Fluvio and Stateful DataFlows on a Rasperry Pi 5 running an object recognition pattern.

Fluvio is a distributed streaming runtime for building event driven analytical applications.

Relevant for Builders who are writing applications in Rust. Software & Data Architects who are building intricate data processing workflows to build intelligent applications using Rust, Python, or JavaScript, and of course SQL.

Fluvio currently is version 0.15.2, closing towards version 1 steadily. The past release notes and features are here - https://www.fluvio.io/news/

Documentation updated as of last release - https://www.fluvio.io/

We released a benchmarking utility in v0.15 and a blog showing some basic benchmark runs here : https://infinyon.com/blog/2025/02/kafka-vs-fluvio-bench/

Would love for you awesome people to try it out and share your experience.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/newzealand by /u/hernesson on 2025-01-05 20:32:10+00:00.

Anyone else?

Project

Welcome to week 31 of Reading Club for Rust’s “The Book” (“The Rust Programming Language”).

“The Reading”

Chapter 21:
https://rust-book.cs.brown.edu/ch18-03-pattern-syntax.html (the special Brown University version with quizzes etc)

The Twitch Stream

Starting today within the hour @[email protected] twitch stream on this chapter: https://www.twitch.tv/deerfromsmoke

https://www.youtube.com/watch?v=ou2c5J6FmsM&list=PL5HV8OVwY_F9gKodL2S31czb7UCwOAYJL (YouTube Playlist)

Be sure to catch future streams (will/should be weekly: https://www.twitch.tv/deerfromsmoke)

After Chs 5 and 6 (see the reading club post here), we get a capstone quiz that covers ownership along with struts and enums.

So, lets do the quiz together! If you've done it already, revisiting might still be very instructive! I certainly thought these questions were useful "revision".

I'll post a comment for each question with the answer, along with my own personal notes (and quotes from The Book if helpful), behind spoiler tags.

Feel free to try to answer in a comment before checking (if you dare). But the main point is to understand the point the question is making, so share any confusions/difficulties too, and of course any corrections of my comments/notes!.

Finally, we can make our own types (or data structures)!!

This is supplementary/separate from the Twitch Streams (see sidebar for links), intended for discussion here on lemmy.

The idea being, now that both twitch streams have read Chapters 5 and 6, we can have a discussion here and those from the twitch streams can have a retrospective or re-cap on the topic.

This will be a regular occurrence for each discrete set of topics coming out of The Book as the twitch streams cover them

With Ch 4 on the borrow checker out of the way, chapters 5 & 6 feel like the "inflection point" ... the point where we're ready to actually start programming in rust.

Custom types, data structures, objects with methods, pattern matching, and even dipping into rust's traits system and it's quasi answer to class inheritance.

If you're comfortable enough with the borrow checker, you can really start to program with rust now!

I personally didn't think this content was difficult, thoug

This is supplementary/separate from the Twitch Streams (see sidebar for links), intended for discussion here on lemmy.

The idea being, now that both twitch streams have read Chapter 4, we can have a discussion here and those from the twitch streams can have a retrospective or re-cap on the topic.

This will be a regular occurrence for each discrete set of topics coming out of The Book as the twitch streams cover them

Ownership and the borrow checker are obviously a fundamental and unique topic to rust, so it's well worth getting a good grounding in AFAICT.

1. Anyone up to trying to summarise or explain ownership/borrow-checker in rust?
   • it can be a good exercise to test your understanding and get feedback/clarification from others ... as well as probably a good way to teach others
2. Any persistent gripes, difficulties or confusions?
3. Any of the quizzes from The Book stump you?
4. Any hard learnt lessons? Or tried and true tips?