Pay per crawl is a new feature to allow content creators to charge AI crawlers for access to their content.

Pay per crawl grants domain owners full control over their monetization strategy. They can define a flat, per-request price across their entire site. Publishers will then have three distinct options for a crawler:

1. Allow: Grant the crawler free access to content.
2. Charge: Require payment at the configured, domain-wide price.
3. Block: Deny access entirely, with no option to pay.

Although this is old news, I still found it interesting. Also, I like the "AI Labyrinth" feature of Cloudflare to block AI bots.

cross-posted from: https://lemmy.bestiver.se/post/913717

Comments

By leveraging WebRTC for direct browser-to-browser communication, it eliminates the middleman entirely. Users simply share a unique URL to establish an encrypted, private channel. This approach effectively bypasses corporate data harvesting and provides a lightweight, disposable communication method for those prioritizing digital sovereignty.

Features include:

• P2P
• End to end encryption
• Forward secrecy
• Post-quantum cryptography
• Multimedia
• Large file transfer
• Video calls
• No registration
• No installation
• No database
• TURN server

*** The project is experimental and far from finished. It's presented for testing, feedback and demo purposes only (USE RESPONSIBLY!). ***

This project isnt finished enough to compare to simplex, briar, signal, etc... This is intended to introduce a new paradigm in client-side managed secure cryptography. Allowing users to send securely encrypted messages; no cloud, no trace.

Technical breakdown: https://positive-intentions.com/blog/p2p-messaging-technical-breakdown

Demo: https://p2p.positive-intentions.com/iframe.html?globals=&id=demo-p2p-messaging--p-2-p-messaging&viewMode=story

cross-posted from: https://programming.dev/post/45042331

Hello again!!

Sorry for the big delay in the announcements. I know it has been a long time I have not made any announcements but I will try my best next time this doesn't happen again.

So, through the medium of this post I would like to share with you all the v1.24.36 major release version of the websurfx project which was released on the 26th of January.

If you are new, and you don't know what is websurfx then I would suggest taking a look at my previous post here:

https://programming.dev/post/2678496

Which covers in depth about what the project is and why it exists.

Credits

Before I share with you the changelog, what this release version means and a preview on what we are planning to work on for the next major release v2.0.0. I would first like to thank all our contributors and maintainers because of whom this was all possible. Specially I would like to thank spencerjibz, MickLesk and SchweGELBin who have been invaluable to the project. Also, Websurfx would not have been possible without alamin655 and xffxff early involvement.

Thanks 💖 to all the people involved in the project

Now, let's dive straight into what this release version actually means.

What does this release version means

This new release version v1.24.36 updates the hybrid caching api to take advantage of the two layer caching solution which eliminates the round trip time delay of fetching the same results from the cache.

Changelog

The changelog of all the changes can be found here:

https://github.com/neon-mmd/websurfx/releases/tag/v1.24.36

Preview of the goals for the next major release

• Different levels of privacy to choose from with the help of rust's conditional compiling features (In progress).
• Even more engines will be supported.
• Categories would be added to search results like images, news, etc.
• More themes will be provided by default
• More animations for the websurfx frontend will be supported.
• Multi language support would be added.
• I2p and tor support will be provided.
• Reduce animations would be added for those who don't want animations and effects on the frontend.
• And lots more ✨.

Call To Action

If you love our project and want to see it move ahead and progress in the direction you want, then we would suggest contributing at our project

Edit: I managed to get it working by using :has and nesting css classes!

body:has(#theme-toggle:checked) {
  background-color: #eff1f5;
  .content {
    color: #4c4f69;
  }
  .header {
    color: #8839ef
  }
  .nav {
    background-color: #dce0e8;
    color: #4c4f69;
  }
}

I'm making a website for my school's robotics team and I'm trying to create a dark theme toggle but it's just not working. I'm trying to avoid javascript and I've seen this kind of thing done with only css and html before so I know it's possible. any advice?

repo: https://github.com/WrenHavoc/JudgeMent-Call-Website

edit: currently my code looks something like this:

#theme-toggle:checked ~ body {
  background-color: #eff1f5;
  color: #fff;
}

#theme-toggle:checked ~ html {
  background-color: #eff1f5;
}

#theme-toggle:checked ~ .content {
  background-color: #eff1f5;
}

the button itself is a checkbox that has display set to none and the label set as an svg so when you click the icon, it gets checked.

<input style="display: none;" type="checkbox" id="theme-toggle">
                <label for="theme-toggle" class="theme-button">
                    <img class="theme-button-svg" src="./icons/half-moon.svg">
                </label>

I used a similar strategy when making the menu for the site so I know it should work

.menu {
  position:absolute;
  margin:0%;
  right:20px;
  top:20px;
}

.menu-button {
  position: relative;
  display: flex;
  flex-direction: column;
  justify-content: space-between;
  width: 30px;
  height: 22px;
  cursor: pointer;
  z-index: 2; /* above menu */
}

.menu-button span {
  display: block;
  height: 4px;
  background-color: #cba6f7;
  border-radius: 2px;
  transition: all 0.3s ease;
}

.menu-items {
  top: 30px;
  right: -20px;
  width: 200px;
  background-color: #181825;
  position: absolute;
  display: none;
}

.menu-items li {
  margin: 20px 0;
}

.menu-items a {
  text-decoration: none;
  color: #cba6f7;
  font-size: 18px;
  padding:5px;
}

.menu-items a:hover {
  text-decoration: none;
  background-color: #cba6f7;
  color: #181825;
  font-size: 18px;
}

.menu-selected {
  text-decoration: underline;
  text-decoration-color: #cdd6f4;
  text-decoration-thickness: 3px;
}

.menu-selected:hover {
  text-decoration-color: #181825;
}

#menu:checked ~ .menu-items {
  display: inline;
}

#menu:checked + .menu-button span:nth-child(1) {
  transform: rotate(45deg) translate(5px, 7.5px);
}
#menu:checked + .menu-button span:nth-child(2) {
  opacity: 0;
}
#menu:checked + .menu-button span:nth-child(3) {
  transform: rotate(-45deg) translate(5px, -7.5px);
}

<input style="display: none;" type="checkbox" id="menu">
                <label for="menu" class="menu-button">
                    <span></span>
                    <span></span>
                    <span></span>
                </label>

I'm looking for a way to add search to a fully static site (think technical documentation) without any server side compute or API.

My idea was to implement one that generates a static index that can be queried by client-side javascript when doing a search, and have the index be organized in such a way that it can be used without having to download the entire thing.

I feel like this should exist already, but I have zero experience here. So, can anyone share suggestions?

By streaming CSS updates/appends through an open HTTP connection

Hi! I have a very simple web-app for displaying the weather. It's built with just HTML, CSS and JavaScript, getting the data from the OpenWeatherMap API. I made this for my own personal use only.

It looks great in Firefox on my Linux desktop, and in the DuckDuckGo browser on my android 16 phone. In the Firefox browser on my phone, it looks great in a Private browsing tab. But there's an issue in a regular (non-private) FF browser tab.

In that one context, I have a display:flex row, with one column for the forecasted temperature for each of the next 24 hours and in a FF Android non-private browser tab only, the section is not displayed at all.

This is what it looks like in the DDG browser (correct):
https://files.catbox.moe/1aa2br.png

This is what it looks like in the FF non-private browser (the Hourly columns are not displayed):
https://files.catbox.moe/108iy6.png

You can see the "hourly" heading for the section but none of the contents are displayed at all.

The HTML for the div looks like this:

<div class="hourly-forecast">  
                <div class="hour-column">  
                    <div class="hr-temperature"></div>  
                    <div class="hr-sun"></div>  
                    <div class="hr-time"></div>  
                </div>  
</div>  

The CSS for the hourly-forecast and hour-column classes looks like this:

hourly-forecast {  
    display: -webkit-flexbox;  
    display: -ms-flexbox;  
    display: -webkit-flex;  
    display: flex;  
    justify-content: space-between;  
    padding: 5px;  
    white-space: nowrap;  
    overflow-x: auto; /* Allows horizontal scrolling */  
}  

.hour-column {  
    display: -webkit-flexbox;  
    display: -ms-flexbox;  
    display: -webkit-flex;  
    display: flex;  
    flex-direction: column;  
    align-items: center;  
    min-width: 75px;  
    text-align: center;  
    border-left: 1px solid lightseagreen;  
}  

I just added those -webkit lines but that didn't help any.

The JS just gets the data and puts it in the correct spots in the HTML. The page is not really interactive otherwise, FYI.

I searched around for this but couldn't find anyone else who had issues that only show up in FF Android.

Thanks for any ideas you might have!

cross-posted from: https://lemmy.bestiver.se/post/878991

Comments

There exists a peculiar amnesia in software engineering regarding XML. Mention it in most circles and you will receive knowing smiles, dismissive waves, the sort of patronizing acknowledgment reserved for technologies deemed passé. "Oh, XML," they say, as if the very syllables carry the weight of obsolescence. "We use JSON now. Much cleaner."

A UX strategist is supposed to bridge business goals and user needs through high-level planning. They’re meant to answer questions like “Should we build this?” and “Which problems matter most?” before anyone opens Figma.

In practice, most I’ve worked with excel at one thing: not committing to answers.

“Should we prioritize mobile or desktop?” “It depends on your user base.”

“Which feature should we ship first?” “It depends on your business goals.”

“When should we launch?” “It depends on market conditions.”

Every answer buys them more time to conduct another research phase, run another workshop, build another framework. They become professional question-deflectors who get paid to suggest you need more information before making any decision.

And here’s the thing – they’re not wrong. Everything in product development genuinely does depend on context. But when “it depends” becomes the primary output of someone earning $120-180 per hour, you’re not getting strategy. You’re getting expensive procrastination.

cross-posted from: https://lemmy.blackeco.com/post/2566627

Looking for recommendations for developers who have been around a few years and stagnating a bit. Searching around I just get the same recommendations over and over so please don't say "Clean Code" or "Pragmatic Programmer".

cross-posted from: https://lemmy.bestiver.se/post/868975

Comments

Can you recommend a CSS framework that feels lean and modern like Pico CSS but isn’t only targeting small form sites?

It's easy to prevent it client-side, but does anyone know of a server-side solution because we should not be trusting data from the client?