Recommended Posts

This new ship is a great idea and will provide for an amazing experience and I see nothing wrong with bringing back a replica of a very good design, even by today's standards.

It's refreshing to see them build a ship that isn't a top heavy pile of crap like modern cruise ships. Most modern ships tend to capsize when they take on even small amounts of water. Take the concordia for example. It only flooded TWO watertight compartments and it capsized within a couple of hours. The Titanic was opened to water by the iceberg over the length of FIVE compartments (SIX if you count the damage stretching into the coal bunker of boiler room 5) and it stayed upright for the entire duration of the sinking, a feat that is amazing in and of itself.

The big problem with Titanic was the height of the bulkheads as Javik pointed out. They were lowered to E deck (10 feet above the waterline) because Ismay didn't want first class passengers to have to deal with blockages caused by watertight bulkheads that went up any further. Had the bulkheads been just two decks higher the Titanic would have been able to stay afloat with the damage that she sustained during the collision, and oddly enough original plans called for a design that would have allowed her to float with up to 6 compartments flooding, a design that was later implemented in Olympic and Britannic after Titanic sank.

:o

People who were lucky enough to go first class on Titanic where rich people who owned big businesses at the time I guess? So it probably is reasonable price for them.

This new ship is a great idea and will provide for an amazing experience and I see nothing wrong with bringing back a replica of a very good design, even by today's standards.

It's refreshing to see them build a ship that isn't a top heavy pile of crap like modern cruise ships. Most modern ships tend to capsize when they take on even small amounts of water. Take the concordia for example. It only flooded TWO watertight compartments and it capsized within a couple of hours. The Titanic was opened to water by the iceberg over the length of FIVE compartments (SIX if you count the damage stretching into the coal bunker of boiler room 5) and it stayed upright for the entire duration of the sinking, a feat that is amazing in and of itself.

The big problem with Titanic was the height of the bulkheads as Javik pointed out. They were lowered to E deck (10 feet above the waterline) because Ismay didn't want first class passengers to have to deal with blockages caused by watertight bulkheads that went up any further. Had the bulkheads been just two decks higher the Titanic would have been able to stay afloat with the damage that she sustained during the collision, and oddly enough original plans called for a design that would have allowed her to float with up to 6 compartments flooding, a design that was later implemented in Olympic and Britannic after Titanic sank.

It was also said that where the iceberg hit the side of the ship, the machine wasn't used to screw in the big screws but were hand screwed in because they couldn't get the machine to where the screws where.

People who were lucky enough to go first class on Titanic where rich people who owned big businesses at the time I guess? So it probably is reasonable price for them.

It was also said that where the iceberg hit the side of the ship, the machine wasn't used to screw in the big screws but were hand screwed in because they couldn't get the machine to where the screws where.

Yea, the extreme bow and stern were riveted by hand because the machine would not fit in those areas. They were also iron rivets instead of steel since iron was easier to use by hand. Steel rivets were used where the machine would fit. Of course you also have the issue where original spec called for grade 4 rivets and they eventually settled for grade 3 which had more slag due to budget concerns. Either way they actually tested the rivets and didn't really see much of a problem with them as far as their ability to sustain unusual stresses. Of course they're going to snap under thousands of tons of force that would be exerted on the hull during a collision with a block of ice upwards of 3 times the size of the ship. They figure no ship of the time would have had a chance of coming away from that collision without significant damage.

Hitting the iceberg head on or making the internal water compartment walls go to the top of the ship may of kept part of it a float.

The other ship that got the distress call and ignored it would of saved a lot of people as well.

Hitting the iceberg head on or making the internal water compartment walls go to the top of the ship may of kept part of it a float.

The other ship that got the distress call and ignored it would of saved a lot of people as well.

Californian (the "other ship") never actually received the distress call. Their wireless operator went to bed at 11:30. 10 minutes before the collision. Titanic was one of the few ships on the ocean that had 2 wireless operators and said radio was manned 24/7.

And you are correct, hitting the iceberg head on would have resulted in one, MAYBE two compartments flooding, and with some minor repairs the ship would have actually been able to proceed under her own power, albeit at reduced speed.

All laughing and joking aside, I for one would like to see it built, It was a majestic ship.

+1, I honestly consider it to be one of the best looking ships ever built. Not to mention the sheer size. I know it pales in comparison to some of the new cruise ships, but everything on Titanic was on a huge scale, from the 4 gigantic funnels right down to the anchors that weighed 15 tons each.

I think it's in extremely poor taste.

Sorry, I fail to see how...

If it repeats the same mistakes, then that's sheer stupidity, ships sink, people still book cruises, planes develop faults and fall out of the sky, people still fly etc...

Now I apologise if this story hits a little too close to home (you may have had a distant relative that either had something to do with it's construction, or journeyed on it, then I retract my statement as it is indeed, at least for you in poor taste)

But in order for humankind to continue growing and evolving, we do have to keep pushing forward, remembering not to mistakes that can endanger or worse, life.

Sorry, I fail to see how...

If it repeats the same mistakes, then that's sheer stupidity, ships sink, people still book cruises, planes develop faults and fall out of the sky, people still fly etc...

Now I apologise if this story hits a little too close to home (you may have had a distant relative that either had something to do with it's construction, or journeyed on it, then I retract my statement as it is indeed, at least for you in poor taste)

But in order for humankind to continue growing and evolving, we do have to keep pushing forward, remembering not to mistakes that can endanger or worse, life.

This isn't about a guy building just a ship though, and offers nothing in somehow advancing humankind.

This is about a guy who wants to build a clone of a ship which was in a tragic even where 1,500 people died and re-enact the journey.I fail to see how this can be seen as anything but poor taste.

It was also said that where the iceberg hit the side of the ship, the machine wasn't used to screw in the big screws but were hand screwed in because they couldn't get the machine to where the screws where.

Rivets are not actually screwed, what happens is that rivets are heated to an incredibly high temperature, hammered through pre-cut holes in the steel. The back end of the rivet is then flattened and the rivet is allowed to cool. Once the rivet cools it contracts and pulls the 2 metal plates together creating an incredibly forceful seal that holds the plates together.

As for the actual point of this question, using the riveting machine in the bow section of the ship was a physical impossibility as the tapering of the bow needed to make it effectively cut through the water simply didn't grant enough room for the machine to do it's work. However if it's done properly hand riveting should not significantly weaken a ship. There is a suggestion that the rivets were of substandard quality and contained too much aluminium slag (a by product of the smelting process), which could have weakened their structure but historical accounts are contradictory. The investigation done by Seconds From Disaster did suggests the rivets were weak, but other investigations have came to opposite conclusions. However what is not debated is that when the iceberg impacted the hull of the titanic it created an absolutely immense amount of force, somewhere in the realm of 12,000lb of force. Most analysts agree that even the most well made rivets of the era would have struggled to survive such an immense amount of force.

In reality the fact is that the Titanic was a pretty well built ship and it essentially encountered unforseen structural forces that it simply could not survive.

This topic is now closed to further replies.
  • Posts

    • WhatsApp is getting usernames, and you can reserve your preferred one now by Fiza Ali Sharing your phone number isn't always something you want to do, especially with people you've just met. Whether it's someone from a class, a local community group, or a sports team chat, handing over your number can feel like giving away more personal information than necessary. That's exactly the problem WhatsApp is trying to solve with its upcoming usernames feature. The company has announced that users can now reserve a unique WhatsApp username ahead of the feature's wider rollout later this year. Once usernames become available, they'll let people connect without revealing their phone numbers. It's a change that makes a lot of sense for group chats. Right now, everyone in the group can see your phone number. With usernames enabled, that won't necessarily be the case when someone contacts you for the first time. WhatsApp says it's opening username reservations early because more than three billion people use the app, meaning plenty of people are likely to want the same usernames. Reserving one now gives users a better chance of securing the name they actually want before the feature launches more broadly. If your preferred username is already taken, WhatsApp will also offer a built-in username generator to suggest available alternatives. The feature isn't only aimed at individual users. Creators, businesses, and organisations will be able to claim the same username they already use on Instagram or Facebook, making it easier to keep a consistent identity across Meta's apps. Furthermore, privacy is a big part of how WhatsApp is introducing usernames. There won't be a public directory where people can browse or search for usernames. Instead, people will need to know your exact username before they can start a conversation with you. Additionally, users can also choose to enable a username key, which adds another layer of control by requiring people to enter that key before sending a message. Once the feature rolls out, people who choose to use a username will no longer have their phone number shown when messaging a person or business for the first time. If you want to reserve a username, make sure you're running the latest version of WhatsApp, then head to Settings > Account > Username. The tech giant says usernames will roll out gradually over the coming months, and users will receive an in-app notification when the feature becomes available in their country.
    • When I think about a network, there are really two aspects, the hardware and the wiring. So here is what I would do for both. Wiring: Use Cat6A for the patch panel, outlets, and all structured cables (cables installed in walls). Run plenty of Wireless Access Point (WAP) cables, as a general rule, assume a signal can only pass through 2-3 walls and can't pass through a floor (that is conservative, but trust me on this if you want strong WiFi)  Cat6 patch cables are fine for now if you don't plan to run 10gig, those are easy to replace later if needed. Run OS2 single-mode fiber to anywhere you think you may have a server or sub-switch. (yes, single-mode for everything on a small network, don't mess with multimode unless you have entire racks of servers and that minor module cost and power savings will matter). If you really want to future proof, also run fiber to any high density WAP locations, it is likely that WiFi 8 WAPs will push the limits of 10g. Run 6-12 pairs of single-mode fiber between your MDF and the building's MDF, even if you only need 1 or 2 pairs now, those extra pairs will pay off down the road. Hardware: (its easy to say "get all the features incase you need them", so instead of futureproofing, I am going to take approach of suggesting areas worth investing in, and areas you can save money). Don't overspend thinking you need every feature on every port. You don't need 10g on every port, you don't need PoE on every port. Don't overspend on redundancy either, unless you are ready to buy two of everything, don't waste money buying two of some things and not others. Dual power supplies are worthwhile, but probably not HA or multi-path redundancy.  Get 1 "distribution layer" switch that your router/firewall will connect to as well as all your access layer switches below. This should be a fully managed 10g+ switch with a combination of copper and SPF ports, a few 25g uplink ports are nice for this switch. Given that you said it is a small network, I suggest also using that distribution layer switch for servers and WAPs, meaning it will need PoE. Speaking of wireless, get good professional tri-band WAPs, and either turn on the band stirring options, or limit 2.4 to an IoT only SSID. This will provide a solid WiFi capable nearly everything but the highest of bandwidth clients...you could even consider skipping wiring workstations depending on usage. Access layer switch for workstations and printers can be cheaper switches, 2.5g is a good sweet spot between price and future proofing, but even 1g is fine for most individual clients (the kind that could probably be fine on WiFi). You can consider saving a little on access layer switches by only getting 1 PoE switch for whatever needs it (remember your WAPs are connecting to the distribution switch, not here), and non-PoE for your workstations, because desk phones are falling out of favor. You can also save money here by not buying managed switches if you don't need them--but really do some soul searching there, if you go this route, then anything that isn't on your workstation VLAN would either need to be connected to the distribution switch, or its own access layer switch. Also, don't feel like you need a fancy fabric stacking switches for your access layer, that is the point of the higher-end distribution layer, to remove the need for things like that at this level. Home Hardware: I'm realizing the above assumed an office setting, if this if for your house and home lab then the above still applies, but you'll probably want everything managed and PoE, just because, but you probably also don't need multiple access layer switches. If your total port count is below 24, just skip separating distribution layer and access layer and just get one nice switch with the features you want. If you are at the point of considering a 48-port switch, I would instead get a nice high-end distribution switch for things that need it, and cheaper access layer switches with specs based on the needs of connected devices. For home use, don't worry about home running every device to the main switch, there is nothing wrong with running sub-switches for your media areas and office, those essentially become your access layer, just look for sub-switches with a 10g uplink so sharing bandwidth isn't an issue. Just make sure you always connect them to your distribution/main switch, don't daisy chain, the path should never have more steps than Client>Access>Distribution>Firewall>Internet.
    • Google Meet brings Gemini note-taking to AI Pro and Ultra subscribers by Karthik Mudaliar Google's Gemini-powered "Take notes for me" feature inside Google Meet is now available to Google AI Pro and Ultra subscribers. The features work on Google Meet for web as well as on mobile, and Google says that subscribers can use it for meetings they host in many supported languages. As the name suggests, "Take notes for me" allows Gemini to listen to a meeting, generate a summary, identify action items, and save the notes as a Google Doc in the user’s Drive. After the meeting, the organizer receives an email recap with the summary and action items, while the notes can also be attached to the related Calendar event depending on the meeting setup and sharing settings. The feature isn't automatically turned on for everyone, though. Google says that all meeting participants are notified when note-taking is turned on, and users can start it from the pencil icon in Meet or enable it for future calls through Meet’s meeting records settings. For work or school accounts, administrators can also control whether the feature is available and may require explicit participant consent for note-taking, recording, or transcription features. The feature first launched back in 2024, when it was available just for selected Workspace users. Over the years, Google added refinements and more options, including the ability to enable it when scheduling meetings via Google Calendar. Google's support docs say that the feature currently supports English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish, but only one language at a time. Meetings with multiple spoken languages are not currently supported, and Google recommends using the tool for meetings between 15 minutes and eight hours. The new feature makes Google Meet closer to its rivals that have AI tools already built in. Microsoft Teams has recently started offering Copilot and intelligent recap features that summarize meetings, surface highlights, and help with follow-ups, while Zoom’s AI Companion can also generate meeting summaries from desktop and mobile meetings.
    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      535
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!