Login
backend blog area text is squeezed to an extreme narrow width
does anyone know what is causing this issue and how to fix
[link] [comments]
submitted by /u/blakep199129
[link] [comments]
[link] [comments]
Reading view
[link] [comments]
How to prepare a tech emergency kit before the next blackout hits
Long outages catch people off guard, but a few smart tools make it easier to stay charged, informed, and reachable while you wait for the power to return.
Maintaining a tech emergency kit is crucial
You know how it goes — power outages are becoming more frequent and lasting longer. These days, our smartphones are our lifeline, not those old landlines on the wall.
When you think of an emergency kit, you probably picture food, water, and first aid supplies. But let's not forget about those little tech gadgets that keep us connected when the power's out.
Continue Reading on AppleInsider | Discuss on our Forums
Maintaining a tech emergency kit is crucial
You know how it goes — power outages are becoming more frequent and lasting longer. These days, our smartphones are our lifeline, not those old landlines on the wall.
When you think of an emergency kit, you probably picture food, water, and first aid supplies. But let's not forget about those little tech gadgets that keep us connected when the power's out.
Continue Reading on AppleInsider | Discuss on our Forums
The Great Pacific Garbage Patch Is Changing the Color of the Ocean
An anonymous reader quotes a report from Scientific American: The Great Pacific Garbage Patch, an area in the Pacific Ocean where debris naturally accumulates, is full of tiny bits of plastic -- so full, in fact, that it seems to be changing the color of the ocean. [...] To better understand how microplastics may have influenced the ocean's color, [Daniel Koestner, a postdoctoral fellow at the University of Bergen in Norway] and his colleagues looked at 20 years of satellite data from the spot in the ocean with perhaps the most of plastic -- the Great Pacific Garbage Patch, a zone between Hawaii and California where trash trapped by ocean currents accumulates.
Between 2002 and 2022, the researchers found, waters near the garbage patch have gotten brighter in both blue and green wavelengths compared with surrounding areas. The results, published in the journal Communications Earth & Environment on Thursday, don't yet prove that microplastics have directly brightened the ocean, the researchers emphasize, though their findings are backed up by lab experiments with microplastics. But without taking direct ocean samples, it's hard to know for sure what's causing the ocean's color to change.
"We're still one step away from proving definitively that microplastics are causing the shift in color that that we're seeing," adds study co-author Shea Cheatham, a Ph.D. student also at the University of Bergen. "We just have to get in there [to the garbage patch] to verify."
The hope is that detecting these color shifts could help identify other areas around the world where microplastics have accumulated.
Read more of this story at Slashdot.
Securing local dev environments
With the recent high-stakes security exploits, I think as DevOps engineers it's our responsibility to make the local dev environment secure for devs.
What do you think?
What are you actively doing about it (like adopting devcontainers)
[link] [comments]
Applebee's Exposed Customers' Personal Data After Leaving Database Password In App
Joe_Dragon shares a report from TechCrunch: Applebee's has fixed a security flaw that allowed anyone to access the personal information of its registered customers, after a researcher found a password for an internal database inside Applebee's mobile app, TechCrunch has learned. The popular restaurant chain confirmed [last Thursday] that it had taken action to address the security issue to prevent any unauthorized access to its customer database. [...] The exposed database contained customer names, email addresses (including whether or not the customer verified their email), dates of birth, phone numbers, and ZIP codes. The data also included veteran status, the number of times customers had logged in, when their accounts were created, and the IP addresses of their most recent log-ins, which can be used to reveal the person's approximate location.
[...] When asked by TechCrunch, the spokesperson would not say if the company has server logs that it can review to determine whether anyone accessed the database, or if it has any logs at all. "Our investigation is ongoing, and we will take appropriate steps based on our findings," the company added. It's unclear how many customers were affected by the data exposure. [...] Applebee's had at least 8.5 million customers enrolled in its rewards program as of last year, though the company would not provide a number of how many customers had their personal information exposed by this security flaw.
Read more of this story at Slashdot.
I built Detent, an open-source React wheel picker with spring physics, morphing text, and rolling numbers
I’ve just released Detent, a React wheel picker that grew into a much bigger exploration of interaction details.
The wheel has its own momentum and spring physics. I spent a lot of time tuning mouse wheel input alongside trackpads, including the awkward cases where a physical scroll wheel keeps spinning after you let go.
It also includes two separate components:
- Detent Text: matching letters stay while the changed parts roll.
- Detent Number: locale-aware formatting with digits that roll through intermediate values.
The examples range from practical time and date pickers to an arc menu, a zoom ring, and some more experimental visual treatments.
There’s a headless hook, separate imports for text and numbers, keyboard support, reduced motion, and no additional runtime dependencies beyond React and React DOM.
Demos and playground: https://detent.hayder.sh
Intro: https://x.com/kghayder/status/2118373654010466733?a=PzCQRSXhM5m8KUTdHk8&s=20
I’d especially appreciate feedback on how the wheel feels with your mouse or trackpad, and whether the API makes sense for something you’d actually build.
[link] [comments]
State of CMS 2026
2026 has been a year of change for those of us who build and manage websites; I have a feeling that many of you are on the move, migrating websites from one CMS to another or building without it. AI is enabling rapid changes on all fronts. Broad market-share numbers tell us very little about your experiences building and managing websites with different tools; that is why I hope that we, as a community, can close this information gap with our own open-source State of CMS survey.
Since 2016, the developer community has been conducting annual surveys on frameworks and programming languages. Many of you have probably participated in State of JS, HTML and CSS. But what about those of us working with CMSs? No equivalent survey exists for our community.
The anonymised results will be freely available on GitHub. I will also create and publish an interactive report, but I am especially excited to see what the community does with the data.
[link] [comments]
Migrating a website
Hey friends,
I inherited my predecessors drupal 8 website. I’ve found it to be difficult to debug and follow the structure that has been set up. Ultimately, I want to update the websites appearance and versioning to make it more modern. Would it be possible for me to create a fresh installation of drupal 11 and then import/migrate the old site’s database? Or should I try to upgrade the old site?
I have never used drupal before, so I’m thinking that going through a fresh installation will build familiarity and make the site easier for me to maintain. I would appreciate any advice or insights! Thank you!
[link] [comments]
OpenAI Responds to US Midterm Elections With New Commitment to Communities
"OpenAI has published a new National Community Compact and Compute Campus Policy Blueprint, apparently in response to the Blue Wave Midterm Elections," writes ancient Slashdot reader Gilmoure. "Instead of moving into communities like a juggernaut, they say they will be dangling friendly carrots going forward." Here's an excerpt from OpenAI's article: Every future compute campus OpenAI owns and operates will have its own local compact. We'll engage residents early enough to ensure their input shapes project plans, give them a local point of contact throughout the life of the campus, and report publicly each year on how we're doing. Each compact will reflect local priorities and include a common set of commitments:
- Pay our own way on energy and infrastructure. We'll pay the full cost of the electricity we use and the infrastructure needed to serve us. Before major spending begins, we'll provide financial assurances so other customers are protected if a project is delayed, reduced, or canceled.
- Protect local resources and report on our impact. We'll develop a water plan for each campus, prioritize closed-loop or low-water cooling, and publish site-level water and electricity use. We'll publish construction plans and independent noise studies before operations begin and annually afterward. And we will not use non-disclosure agreements (NDAs) with public officials, allowing only narrow protections covering legitimate security information, trade secrets, or proprietary or competitively sensitive information.
- Create opportunities for local workers and businesses. We'll publish the jobs we expect to create, work with unions and training providers to help residents prepare for them, and report annually on hiring and apprenticeships. We'll also make sustained investments in priorities residents help select.
[...] The investments that help America compete globally can also help communities prosper locally. That starts with giving residents a say while plans can still change and a way to hold developers accountable for delivering on their commitments. That's what we're committing to at the campuses we own and operate, and what we believe people should be able to count on wherever AI infrastructure is built across the country.
Read more of this story at Slashdot.
[PROMO] I built a lightweight plugin to declutter and reorganize the WordPress admin menu for clients
Hi everyone,
One of the biggest headaches when handing off WordPress and WooCommerce sites to clients is dashboard bloat. As soon as a few key plugins are installed, the admin sidebar turns into a wall of menus, settings pages, and upsell tabs that overwhelm clients and generate unnecessary support tickets.
To solve this cleanly without adding bulky third-party dependencies, I built Precise Expressions Admin Menu Reorganizer Lite.
Lite features:
- Create up to two effective custom menu rules.
- Move Comments under Posts (built in).
- Add the WooCommerce Catalog Hub with links to common product and store screens.
- Rename moved menu items and retain their capabilities.
- Preserve saved historical rules beyond the Lite two-rule entitlement, so upgrading, downgrading, or a Pro license change never deletes those rules.
The Lite version is 100% free and open-source on the official WordPress repository:
WordPress.org: https://wordpress.org/plugins/precise-expressions-admin-menu-reorganizer/
Would love candid feedback from fellow agency owners and freelancers on the setup workflow and edge-case compatibility with complex admin setups.
[link] [comments]
[ Removed by Reddit ]
[ Removed by Reddit on account of violating the content policy. ]
[link] [comments]
Y la perr seguia y seguia, hasta cuando con este tipo
 | Mayer ya sabemos que quieres leche maga pero tampoco hace falta que abras tanto las piernas, en Panama naturgy y ensa tienen el suministro de electricidad en el neolitico pero este especimen anda pidiendo centro de datos que ni en USA quieren (con eso se entiende todo). btw mayer, se que usas reddit y estas en este sub, te quiero dedicar algo: vtplpxdtm [link] [comments] |
How do I make colleagues aware of the risks of giving an LLM agent root access to production?
I could use some advice on a situation at work.
A few colleagues in ops have, almost overnight, started to fully trust their LLM agent because it has gotten so good lately and "doesn't make mistakes anymore". They built their own harness around it and log what it does (using Grok and Google models), but the agent still runs with root access to our entire production infrastructure. We have no clear team rules or policy yet, and they don't see the danger themselves.
A typical example: whenever the agent needs to check something on a server, they just hand it full access. But looking at info only needs read-only access. The permission should match the task, not the most convenient option.
My concerns:
Logging is detection, not prevention. It shows what broke afterwards, but doesn't stop anything.
Root bypasses the harness. An agent with root can in theory edit the harness, the logs and the backups, so those logs are not a reliable audit trail.
No least privilege. One wrong command or misread context can touch everything.
Prompt injection via logs, tickets or web pages the agent reads.
Model updates. Providers change models without us deciding when, so "no mistakes in recent months" says little about the next version.
Data going to third parties. With root, the agent can read .env files, keys and customer data, which then end up with the model provider (a GDPR question too).
"It has gone fine so far" only means the failure hasn't happened yet.
I don't want to ban anything. I want them to see the risk themselves and set up proper guardrails together with me: a read-only user by default, scoped credentials, just-in-time access, human approval for write actions, staging first, and no access to backups and logs.
Questions for you:
How do I explain the difference between "we log it" and "it can't do it in the first place"?
How have you convinced overconfident colleagues about AI tooling risks without a confrontation?
Do you have horror stories or post-mortems I can share? Concrete incidents tend to work better than theory.
Which guardrails or policy examples have worked well for you?
How do you raise this with management without coming across as "anti-AI"?
[link] [comments]
[ Removed by Reddit ]
[ Removed by Reddit on account of violating the content policy. ]
[link] [comments]
OpenSSH Flaw Lets Attackers Log Into Password-Disabled Linux Accounts
A newly disclosed OpenSSH flaw dubbed "*sshole" can allow attackers to log in to password-disabled accounts on certain musl-based Linux systems simply by submitting a password longer than 256 bytes. "Apparently certain varieties of musl Linux (Alpine, OpenWrt, Buildroot, Yocto, etc.) have had this OpenSSH vulnerability for about a decade," writes longtime Slashdot reader AlteredEgg. "Upgrade now!" BleepingComputer reports: Security researcher Ozgun Kultekin, who discovered and released details on the vulnerability today, says the flaw has existed since 2016 and stems from how OpenSSH handles password verification errors on systems using the musl C library. Linux accounts can be configured to prevent password logins by replacing their password hash with an asterisk (*) in the /etc/shadow file. Because this is not a valid password hash, no password should allow access to those accounts. However, a patch introduced in OpenSSH in 2016 to fix a username enumeration vulnerability tracked as CVE-2016-6210 changed how OpenSSH handled accounts without usable password hashes.
To prevent attackers from identifying valid usernames through different response times, OpenSSH was modified to perform password hashing even when an account had no usable password hash, including accounts configured with * to block password logins. The problem is that the musl C library's crypt() function also returns * when password hashing fails, including when a submitted password exceeds its 256-byte limit. This means an attacker can submit an oversized password and cause OpenSSH to compare the returned * against the account's stored *, resulting in a successful login.
To be clear, the flaw does not allow attackers to bypass passwords on accounts with valid password hashes. [...] Admins who can't immediately install the update can mitigate the issue by turning off SSH password authentication with PasswordAuthentication no in their SSH server configuration and restarting SSH. Kultekin says admins can also check for signs of exploitation by examining SSH authentication logs for password-based logins for accounts that should not allow them.
Read more of this story at Slashdot.
MS Edge Imposed Rounded Upper Left Corner
 | I'm updating my CSS skills and learning a lot of new things. I just created a navigation link menu with submenus and it is working well. However, only in MS Edge, the top left corner of the navbar is being rounded by Edge. Chrome and FF are not doing this. If you know how to override this, I'd really appreciate your fix. Pics are Chrome, then Edge. TY! [link] [comments] |
First time working on a startup that is 99% vibecoded. As a non-vibecoder, it seems impossible to work on.
Recently I've joined a project with a group of 4, that has been super frustrating to work on.
So far whatever we have, has been 99% vibecoded from the ground up, and that 1% is me. At first I thought this would be fun, we would be making something in a weeks time, but like a month passed and we haven't really moved anywhere. There's literally a login screen that works (no Oauth) and some fancy UI, but that's it. Trying to debug or add new features by hand is impossible, because the code is not readable by humans. There's like 50 lines in the .env file, yet nothing works.
With all this in mind, the absurd thing is that it takes a full minute to deploy any changes to production. In comparison, my hand-crafted Django platform, with real users and tons of features, deploys in seconds.
Don't get me wrong, I am all for using AI to build projects. It's a very powerful tool and I use it to help me code all the time. But in my opinion, to make vibecoding work, you have to know the project structure and the architecture of a website, because then you can avoid massive tech debt in the future.
I can already tell that this experience will be funny to look back on.
[link] [comments]
Hoy confieso que yo mismo, me di empleo
 | Este es mi primer trabajo y mi única esperanza de cambiar las cosas. Una producción independiente, desarrollada con mis propios recursos, conocimientos y tiempo. [link] [comments] |
![[link]](https://i.redd.it/xti1an6xswzh1.png){kind=link}
![[link]](https://i.redd.it/vw5uv88qurzh1.jpeg){kind=link}
