DEAR THREADS

 

@Threads #Threads

THE NEW AI LABEL : ON/OFF FEATURE ON FACEBOOK

Facebook users : perhaps you're wondering about :

The “AI label: on/off” you see in Facebook (Meta Platforms/Facebook features) refers to a disclosure setting about AI-generated content.

What it means

1. AI label ON

You are choosing to show a label/disclosure when content is created or assisted by AI tools.

It tells viewers that the post may involve AI-generated or AI-assisted content.

This is aligned with Meta’s transparency effort so people can identify synthetic content.

2. AI label OFF

You are not actively marking the post as AI-generated (from your side).

The post appears as normal user content without you explicitly adding an AI disclosure label.

However, Facebook/Meta may still automatically detect and label AI content in some cases.

Important clarification

This is not a switch that turns AI detection on or off.

- It does NOT control whether AI is used

- It only affects whether you declare or tag AI involvement in your post

Why Meta introduced this

Because AI-generated content is now common (images, captions, edits, text), Meta is trying to:

- increase transparency

- reduce misinformation risk

- help users understand what is real vs AI-assisted

Simple way to think about it

ON = “I acknowledge this may be AI-generated/assisted”

OFF = “I’m not tagging it myself, but the system may still detect it”

The Project QHSE Plan: A Shared Effort, Led by the Main Contractor

A Project Quality Plan (PQP), Project Safety and Health Plan (PSHP), Project Environmental Management Plan (PEMP), or an integrated Project QHSE Plan is typically developed, owned, and controlled by the Main Contractor, who bears the overall contractual responsibility for delivering the project in compliance with the client's requirements, applicable legislation, and relevant management system standards.

However, although the Main Contractor is responsible for the overall plan, its preparation is rarely undertaken in isolation. Specialist subcontractors, suppliers, and trade contractors are normally required to contribute discipline-specific information within their respective scopes of work.

For example, even where the Main Contractor employs its own Mechanical & Electrical (M&E) Manager or M&E Engineers, the appointed M&E specialist subcontractor is expected to provide technical input relating to:

- Method statements and work sequences,

- Inspection and Test Plans (ITPs),

- QA/QC procedures,

- Risk assessments and safe work practices,

- Environmental control measures,

- Testing, commissioning, and handover procedures,

- Competency requirements and resource planning and

- Discipline-specific statutory or client requirements.

These inputs are then reviewed, coordinated, and incorporated into the overall Project QHSE Plan by the Main Contractor to ensure consistency, eliminate conflicts between trades, and maintain a single, integrated management system for the project.

This collaborative approach recognises that while the Main Contractor retains overall accountability, specialist subcontractors possess the technical expertise necessary to define the most appropriate controls and procedures for their respective disciplines.

Consequently, the Project QHSE Plan becomes a coordinated document representing the combined expertise of the entire project delivery team rather than merely the work of the Main Contractor alone.

Digital Banking: Are We Leaving Some People Behind?

I must admit I'm quite disappointed that some banking apps now require newer versions of Android or iOS just to function properly.

Before anyone misunderstands my point, let me say this: I have been a technology practitioner for many years and continue to keep myself updated with new technologies, including AI. I fully support technological progress and understand why banks continuously strengthen cybersecurity. My concern is not about technology itself, but about accessibility and practicality.

It becomes especially frustrating when a transaction cannot proceed because the app requires verification, yet the operating system on an older smartphone is no longer supported. In some cases, even NFC-based features stop working because the banking app is no longer compatible.

The only practical solution seems to be buying a newer smartphone, I'm even considering a second-hand refurbished unit, since my current phone still works perfectly well for everything else.

For the past 2 days, I had to walk a few kilometres to the nearest ATM simply to withdraw cash so I could top up my Touch 'n Go eWallet. It made me realise how dependent we've become on digital banking.

And if I do get a new phone, there's another hurdle. For some banks, registering a new device requires additional verification, and I may even have to visit a branch before waiting through a 24-hour cooling-off period before I can use the banking app again. I understand the security reasons behind it, but it certainly isn't the most convenient experience.

Sometimes I find myself thinking about a few things:

1. Are we upgrading our smartphones because we genuinely need new technology, or because software support leaves us with no other choice?

2. As society moves towards becoming increasingly cashless, are we unintentionally leaving behind people who cannot afford to replace perfectly functional devices every few years?

3. What about those who simply cannot afford a new smartphone, the elderly who may struggle with constantly changing technology, or the less fortunate? Are we making financial services more secure at the expense of making them less accessible?

4. And on a lighter note, it sometimes makes me wonder (perhaps I'm just being paranoid 😄): are banks and smartphone manufacturers secretly working together to keep us upgrading our phones? I know they're not... but the thought does cross my mind!

Technology should make life easier, improve accessibility, and promote financial inclusion not create unnecessary barriers for people who simply want to access their own money.

Slope Failure at Hillside Road Cut (Residual Soil Formation)

 

READ THIS BEFORE MOVING ON

1. PROJECT BACKGROUND

A hillside road-cut excavation for a residential access road experienced partial slope failure after heavy rainfall. The failure occurred at Chainage 0+320 to 0+360, involving a 12 m high cut slope in weathered granite residual soil.

• Slope inclination: 1V:1.2H (≈ 40°)

• Soil type: Silty sand with clay lenses

• Groundwater: Perched water table observed after rainfall

• Rainfall event: 120 mm within 24 hours

2. FIELD OBSERVATIONS

• Tension cracks at crest (width 20–50 mm)

• Shallow rotational slip at mid-slope

• Surface erosion and rilling

• Seepage observed from slope face

• Vegetation cover absent

3. ANALYSIS

3.1 Assumed Soil Parameters (from site investigation)

3.2 Factor of Safety (Infinite Slope Model – Simplified)

3.3 Post-Rainfall Condition (Pore Pressure Effect)

• Assume pore pressure ratio ru = 0.3:

• Effective normal stress reduces significantly → FS drops:

• Estimated FS ≈ 0.78 – 0.85

• FAILURE CONDITION (FS < 1.0)

4. ROOT CAUSE ANALYSIS (RCA)

4.1 Immediate Causes

• Heavy rainfall causing infiltration

• Increase in pore water pressure

• Loss of matric suction in residual soil

4.2 Contributing Factors

• Inadequate surface drainage

• No benching on steep slope

• Absence of erosion control measures (turfing/geotextile)

• Poor compaction at cut face

4.3 Root Causes (Systemic)

• Incomplete geotechnical risk assessment during design stage

• Lack of drainage integration into slope design

• Contractor deviation from approved slope protection method statement

• Insufficient QA/QC enforcement on earthworks

5. CORRECTIVE ACTIONS

5.1 Immediate Stabilization

• Install sandbags and temporary toe berm

• Divert surface runoff using temporary drains

• Remove loose unstable soil mass

5.2 Permanent Remediation

• Re-profile slope to 1V:2H

• Construct bench drains every 3–4 m vertical height

• Install sub-surface horizontal drains

• Apply hydroseeding + erosion control matting

• Install shotcrete with weep holes in critical zones

5.3 Structural Measures (if required)

• Soil nail system (6–8 m length)

• Wire mesh reinforcement + shotcrete facing

• Retaining wall at toe (if space constrained)

6. RISK ASSESSMENT (POST MITIGATION)

Residual FS after mitigation: Estimated FS ≈ 1.45 – 1.60 : Acceptable (FS ≥ 1.3)

7. MONITORING PLAN

• Inclinometers installed at crest and mid-slope

• Piezometers for groundwater monitoring

• Monthly slope inspection after rainfall

• Trigger level: rainfall > 80 mm/day

8. CONCLUSION

The slope failure was primarily caused by rainfall-induced pore pressure buildup combined with marginal initial stability (FS ≈ 1.09). The design did not adequately account for hydrological effects on residual soils, resulting in a condition where even moderate rainfall triggered failure.

Post-analysis shows that incorporating proper drainage, slope flattening, and surface protection increases the Factor of Safety to above 1.4, which is acceptable for long-term stability.

READ THIS BEFORE MOVING ON