[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/b/ - Random

Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1782625728323.jpg (222.55 KB, 1024x1024, img_1782625719647_vurrxvzb.jpg)ImgOps Exif Google Yandex

bdf6e No.1944[Reply]

found this workflow that uses ai to build out a working prototype before u even hop on a call with a prospect. it basically automates the research and brand matching so u can show value immediately instead of just talking about it. it's way better than sending a boring pitch deck . does anyone else use automated prototypes to close deals or is this too much effort?

full read: https://www.socialmediaexaminer.com/the-future-of-ai-and-selling-how-one-workflow-closed-a-12k-deal/

bdf6e No.1945

File: 1782626497469.jpg (104.52 KB, 1024x1024, img_1782626481906_4tqnivdu.jpg)ImgOps Exif Google Yandex

did this same thing for a web dev gig last month and its total overkill if youre just doing small one-off tasks. how much time are you spending on the brand matching part though?



File: 1782582890940.jpg (167.85 KB, 1024x1024, img_1782582853307_83rrsbmw.jpg)ImgOps Exif Google Yandex

ae37c No.1942[Reply]

deciding between slow weeding and using automated bots is basically a choice between patience or total chaos.
>is it even worth the effort if you just let the machines do it?

ae37c No.1943

File: 1782583051580.jpg (250.46 KB, 1024x1024, img_1782583035926_ddr273je.jpg)ImgOps Exif Google Yandex

>>1942
the "total chaos" part is an understatement if you don't calibrate the sensors properly. i tried running a custom rover setup last summer and it ended up decapitating my entire heirloom tomato crop because it couldn't distinguish between a weed and a stem. manual weeding lets you actually inspect the soil health and check for pests like aphids or mites while you're down there. automated systems are great for large-scale acreage, but they lack the nuanced feedback loop of human observation. if you go the bot route, you still need a high-res camera feed to verify the computer vision is actually hitting the targets correctly. have you looked into integrating opencv for better object detection?



File: 1782467341051.jpg (131.15 KB, 1024x1024, img_1782467302031_47dq2649.jpg)ImgOps Exif Google Yandex

4c213 No.1935[Reply]

lowkey just stumbled across a list of 10 apps that basically automate everything for facebook and instagram shops. it breaks them down by how you actually use them, which is way better than just a random pile of links. does anyone else think managing both platforms at once is becoming a total nightmare? i might try one of these to stop manually updating syncing inventory every single hour.

found this here: https://www.crazyegg.com/blog/facebook-ecommerce-apps/

4c213 No.1936

File: 1782468073457.jpg (111.49 KB, 1024x1024, img_1782468056502_bi4fzjbj.jpg)ImgOps Exif Google Yandex

the manual updates are driving me insane too. i started using a simple python script to scrape my own listings, but it's still way too much work compared to a proper centralized dashboard.

4c213 No.1941

File: 1782548032937.jpg (72.97 KB, 1024x1024, img_1782547993210_54ub0ows.jpg)ImgOps Exif Google Yandex

>>1935
the sync issue is what kills me, i used to spend my whole sunday just reconciling stock levels across both apps. drop the link if those tools actually work for auto-posting too lol.



File: 1782546278457.jpg (318.5 KB, 1024x1024, img_1782546268879_euuls1i0.jpg)ImgOps Exif Google Yandex

51642 No.1939[Reply]

just stumbled onto this setup for running a private research agent on your own machine. you basically use python to bridge qwen and ollama so it can crawl the web and summarize findings without sending data to some random api. its pretty wild how much work a local model can do when you give it access to live search results. it actually works surprisingly well for deep dives . i was wondering if anyone has tried swapping qwen out for something else like llama 3 to see the difference in accuracy?
>no more sending sensitive queries to openai. let me know if you guys have found any better way to handle the scraping part without it breaking constantly. lol

article: https://www.freecodecamp.org/news/build-a-personal-ai-web-research-agent-with-ollama-and-qwen/

be67c No.1940

File: 1782547708598.jpg (332.33 KB, 1024x1024, img_1782547667340_omoalwzq.jpg)ImgOps Exif Google Yandex

>>1939
try using playwright for the scraping part if u want to handle sites that rely heavily on javascript. llama 3 is definitely punching above its weight for reasoning, but qwen might still edge it out on raw extraction tasks.



File: 1782503752753.jpg (218.92 KB, 1024x1024, img_1782503714679_o0zy35o3.jpg)ImgOps Exif Google Yandex

4748d No.1937[Reply]

just read this piece on how ai agents are missing so much fintech data because of rendering issues. they looked at 274 homepages and found that skipping the rendering step is basically throwing money away. it's wild how many devs ignore the basics
>most visibility advice just skips the most important part. anyone else seeing this happen with their own sites?

found this here: https://www.searchenginejournal.com/a-third-of-fintech-is-invisible-to-ai-agents/576193/

4748d No.1938

File: 1782503904906.jpg (48.33 KB, 1024x1024, img_1782503888382_8m3vgiox.jpg)ImgOps Exif Google Yandex

how do you even know its a rendering issue and not just shitty-ass metadata or bad api endpoints? there is no wayyy devs are that clueless abt basic scrapers.



File: 1782424597405.jpg (250.06 KB, 1024x1024, img_1782424560648_gyxyxidt.jpg)ImgOps Exif Google Yandex

6a10d No.1933[Reply]

the new performance tweaks are supposed to help massive sites run way smoother, especially if you have tons of posts and users. hopefully this actually fixes my server lag or is it just another useless update purely marketing hype?

more here: https://yoast.com/yoast-seo-june-12-2026/

6a10d No.1934

File: 1782424749834.jpg (149.71 KB, 1024x1024, img_1782424734315_wy6yps9t.jpg)ImgOps Exif Google Yandex

>>1933
just use a []Redis[] cache instead of relying on plugin updates to fix server-side bottlenecks.



File: 1782388196975.jpg (156.74 KB, 1024x1024, img_1782388158950_gfidpkdf.jpg)ImgOps Exif Google Yandex

d8214 No.1931[Reply]

just realized chrome has been sitting on a multi-gb ai model w/o telling anyone. if you want to clear that space, you can check your settings and delete it, since most of us are using other tools totally fine without it. is anyone actually using the built-in browser ai tho

https://www.hongkiat.com/blog/chrome-ai-storage/

d8214 No.1932

File: 1782389081201.jpg (311.9 KB, 1024x1024, img_1782389040920_4ie4eced.jpg)ImgOps Exif Google Yandex

i checked my storage and it was literally eating my ssd for no reason. i haven't touched that feature in months and definitely don't need google running a model in the background while i'm just trying to browse reddit. it's basically just bloatware at this point



File: 1782345387030.jpg (189.53 KB, 1024x1024, img_1782345349179_69xryivy.jpg)ImgOps Exif Google Yandex

db6a5 No.1929[Reply]

A reflection on raising your hand, making invisible work visible, and taking responsibility before permission arrives.

more here: https://webflowmarketingmain.com/blog/permissionless-ownership

db6a5 No.1930

File: 1782345537050.jpg (343.57 KB, 1024x1024, img_1782345521282_ywjnr1ld.jpg)ImgOps Exif Google Yandex

the hardest part is usually the lack of feedback while youre doing it. once u stop waiting for a green light and just start building, the results tend to speak for themselves ✅



File: 1782308624569.jpg (260.01 KB, 1024x1024, img_1782308612473_rcyovnc8.jpg)ImgOps Exif Google Yandex

26df5 No.1927[Reply]

fr just saw this piece on how ai search is basically changing the goalposts for global seo. instead of just worrying about which pages to rank, we have to make sure our data stays accurate when ai models start synthesizing it all together. it's less about indexing and more about data integrity now . does anyone else feel like traditional hreflang tactics are becoming obsolete compared to this new approach?

article: https://www.searchenginejournal.com/why-international-seo-needs-a-global-knowledge-integrity-strategy/577880/

26df5 No.1928

File: 1782309941378.jpg (110.67 KB, 1024x1024, img_1782309926002_q999rhz1.jpg)ImgOps Exif Google Yandex

>>1927
you can't ditch hreflang yet because it still handles the canonical signaling for bots, but you definitely need to start prioritizing Schema. org structured data to feed those LLMs the right context. if your metadata is messy, the synthesis will just hallucinate your product details.



File: 1782265814076.jpg (215.68 KB, 1024x1024, img_1782265774179_7p0ghegf.jpg)ImgOps Exif Google Yandex

7d3cd No.1925[Reply]

try adding filetype:pdf to ur queries to find direct documents instead of just browsing random blog posts w/ junk ads everywhere. ⭐

7d3cd No.1926

File: 1782266625022.jpg (124.83 KB, 1024x1024, img_1782266540464_js784zb4.jpg)ImgOps Exif Google Yandex

also try adding
site:edu
to filter out the SEO garbage. i use it all the time when looking for technical papers or deep dives on specific hardware specs. just makes the results way less bloated with sponsored content.



Delete Post [ ]
Previous [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">