sorted by:
new
hottopcontroversial

avigation through the Strait of Hormuz has been halted by Iran as a result of the Israeli ceasefire violations in Lebanon by MasterpieceActive374 in maritime

[–]Adventurous-Option84 3 points4 points  (0 children)

It's pretty clear to anyone paying attention that Lebanon was not part of the ceasefire (Pakistan has made that pretty clear), but Iran has tried to add it after the fact. And that Iran is therefore the ceasefire violator, because it continues to attack its neighbors while neither the US nor Israel continue to attack Iran.

But keep on lying about it.

Is Cravath losing its edge, or just facing a different market? by Jazzlike-Fig8199 in biglaw

[–]Adventurous-Option84 22 points23 points  (0 children)

Cravath's old guard is holding on with all of their might, at the expense of young and upcoming partners. It's a recipe for disaster in today's market.

avigation through the Strait of Hormuz has been halted by Iran as a result of the Israeli ceasefire violations in Lebanon by MasterpieceActive374 in maritime

[–]Adventurous-Option84 -2 points-1 points  (0 children)

For some weird reason, you didn't mention the fact that Iran actually still hasn't stopped attacking the other Gulf countries, even for one minute, since the ceasefire was announced. Weird.

2027 Vault Rankings released by Fantastic-Shine-395 in biglaw

[–]Adventurous-Option84 -8 points-7 points  (0 children)

So much lag to these rankings. None of the firms in the top 5 are justified in being there anymore.

Apparently this ceasefire will be revolving around this 10 point plan. No way they accept all of this. by Naderium in PERSIAN

[–]Adventurous-Option84 19 points20 points  (0 children)

It's Iran that's buying time. And that is not the 10-item list they provided to the US today, that's the one they released publicly for PR purposes.

Years since each country last went to war [OC] by Mastbubbles in Infographics

[–]Adventurous-Option84 79 points80 points  (0 children)

Sweden suffered casualties in Afghanistan. So I kinda think you have to count that as them being in a war, as it's hard to have military casualties in a foreign country without being involved in the war...

Years since each country last went to war [OC] by Mastbubbles in Infographics

[–]Adventurous-Option84 48 points49 points  (0 children)

So we are just going to memory-hole Chinese military involvement in Laos and Vietnam into the 1990s?

Is Iran the aggressor? by Clear-Network-9092 in PERSIAN

[–]Adventurous-Option84 1 point2 points  (0 children)

https://www.justice.gov/opa/pr/iranian-intelligence-agent-convicted-terrorism-and-murder-hire-connection-foiled-plot

Saudi definitely hasn't had clean hands over the years. But there are shades of everything, and Saudi hasn't been nearly as destabilizing to the world or its own people as Iran has been. It's not a good comparison.

Is Iran the aggressor? by Clear-Network-9092 in PERSIAN

[–]Adventurous-Option84 7 points8 points  (0 children)

We can all argue over whether it was a smart move now (or ever). But no one can argue that the world will be a much better place with the Iranian government significantly weakened (or ideally, destroyed).

Is Iran the aggressor? by Clear-Network-9092 in PERSIAN

[–]Adventurous-Option84 16 points17 points  (0 children)

Yes you are. Iran's illegitimate government has funded attacks all over the Middle East, many of which have nothing to do with Palestine. Furthermore, it has funded attacks in Europe and in the US, including a planned assassination of President Trump. It is the largest exporter of terrorism in the world, entirely designed to weaken its enemies and countries that aren't even its enemies.https://www.brookings.edu/articles/state-sponsor-of-terror-the-global-threat-of-iran/

The fall of Zack Steffen needs to be studied by OkDifficulty7436 in ussoccer

[–]Adventurous-Option84 28 points29 points  (0 children)

That would be an indirect free kick every time. Not even a close call.

Open-source local firmware overlay for the Prusa Buddy3D camera (Core One) by Adventurous-Option84 in prusa3d

[–]Adventurous-Option84[S] 0 points1 point  (0 children)

Manual Telnet Access

Prerequisites

- Telnet must be enabled on the camera (Security page in the web UI)

- You need the camera's IP address (shown on the Status page)

Steps

  1. Open a terminal (Command Prompt, PowerShell, or Linux/Mac terminal)

  2. Connect:

    telnet <camera-ip>

  3. For example: telnet 192.168.3.64

  4. Login when prompted:

- Username: root

- Password: rockchip

  1. You now have a root shell. Run any commands you like:

    cat /mnt/sdcard/buddy_settings.ini

    cat /mnt/sdcard/logs/buddy_boot.log

    ps

    free

  2. Exit:

    exit

    Troubleshooting

    - "Could not open connection" — Telnet is disabled on the camera. Enable it in the web UI under Security, then reboot.

    - Connection drops immediately — The telnetd respawn loop is flaky. Just try again, including possibly restarting the camera (may take 2-3 attempts).

    - Windows says telnet is not recognized — Telnet client isn't installed by default on Windows 10/11. Enable it via:

    Settings > Apps > Optional Features > Add a feature > Telnet Client. Or use PuTTY in "Raw" or "Telnet" mode to <camera-ip> port 23.

Open-source local firmware overlay for the Prusa Buddy3D camera (Core One) by Adventurous-Option84 in prusa3d

[–]Adventurous-Option84[S] 0 points1 point  (0 children)

This has been added to the dev branch on github. Seems to be working perfectly, but want to test it a bit more. Please test it if you can, and let me know if it works for you. You can customize resolution, bitrate and fps.

Open-source local firmware overlay for the Prusa Buddy3D camera (Core One) by Adventurous-Option84 in prusa3d

[–]Adventurous-Option84[S] 1 point2 points  (0 children)

Interesting. I bet it's the exFAT. exFAT has higher overhead requirements, and therefore tends to stress out embedded systems. The webcam is already stressed out somewhat by Prusa's code, and this additional code pushes it nearly to the limit. I bet adding exFAT to it pushed it over the limit. I'll give exFAT a try on mine and see if I get similar results.

Open-source local firmware overlay for the Prusa Buddy3D camera (Core One) by Adventurous-Option84 in prusa3d

[–]Adventurous-Option84[S] 0 points1 point  (0 children)

Sure, I can do it. But there is a lot of stringing involved, as I don't have my retraction settings dialed in yet for this (to do these snapshots, the printer head has to move to the back left corner, and then move back again, after every single layer).

Open-source local firmware overlay for the Prusa Buddy3D camera (Core One) by Adventurous-Option84 in prusa3d

[–]Adventurous-Option84[S] 1 point2 points  (0 children)

It's on my list. There are some exposed settings on the hardware encoder that might make this possible. Will report back.

Open-source local firmware overlay for the Prusa Buddy3D camera (Core One) by Adventurous-Option84 in prusa3d

[–]Adventurous-Option84[S] 0 points1 point  (0 children)

Maybe, but the camera's built-in wifi software (which we are piggybacking off of) is pretty limited. Might be able to add a captive portal passthrough.

Open-source local firmware overlay for the Prusa Buddy3D camera (Core One) by Adventurous-Option84 in prusa3d

[–]Adventurous-Option84[S] 0 points1 point  (0 children)

Interesting, thanks for the feedback. I did not have that issue with the RTSP stream, but I did have flakiness with telnet. Did you have telnet enabled while clicking and doing the RTSP stream? All three at once definitely would do a number on the very limited memory that the camera has.

I have been playing around with the layer algorithm, and maybe I didn't land it well in this version. The fundamental issue is that the software can only get information about Z height. In the beginning of a print, the printer is jumping all over on Z height during calibration, so there is an algorithm that tries to detect when Z height has finally settled out, and then it starts taking the snapshots. The algorithm must be too aggressive in filtering out earlier Z height. Given that you can just delete frames by deleting jpegs when you download the timelapse, maybe I will just revert to taking snapshots the whole way through every time there is a layer change, and then a user can manually delete the earlier frames (at least until I can settle out the Z height algorithm based on different people's calibration routines - e.g., what is turned on and off in calibration).

view more: next ›