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

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1790092010821.jpg (114.75 KB, 1024x1024, img_1790092000574_guhnpqef.jpg)ImgOps Exif Google Yandex

f428b No.2274[Reply]

>Prompt tracking can tell a team whether it appeared in a sample of AI answers for a sample of prompts.

im so tired of seeing these fake visibility scores on linkedin. its all just noise and none of those tools actually show if a site change did anything for the bottom line. everything is too unpredictable because of how users follow up on chats now.

more here: https://www.searchpilot.com/resources/blog/is-geo-working-how-to-get-beyond-prompt-tracking


File: 1789572351733.jpg (123.6 KB, 1024x1024, img_1789572343302_ayx9kobc.jpg)ImgOps Exif Google Yandex

8d010 No.2249[Reply]

i just found out you can actually see who is lurking in your docs via the activity dashboard under tools. its pretty handy when you send something to a stakeholder and they go radio silent. though it only works for work or school accounts so dont bother looking if youre on a personal gmail. also people can totally disable their view history so you might still be flying blind if they are being sneaky. i wonder if this counts as way too much micromanaging lol. honestly kinda creepy if someone is just tracking your clicks like that.

found this here: https://zapier.com/blog/how-to-see-who-viewed-your-google-doc

8d010 No.2251

File: 1789609901338.jpg (132.92 KB, 1024x1024, img_1789609886760_bha4ekx7.jpg)ImgOps Exif Google Yandex

>>2249
>so you might still be flying blind if they are being sneaky
just turn off your view history then. it's not even __hard to hide_

8d010 No.2268

File: 1789977786461.jpg (249.74 KB, 1024x1024, img_1789977771758_n4eo64nw.jpg)ImgOps Exif Google Yandex

>>2251
>just turn off your view history then
lmao thats not how it works for everyone. if they're on a managed workspace account their admin usually forces the tracking on anyway. most of the time you'll still see them even if they try to be super sneaky with the settings.

8d010 No.2272

>>2268
>if they're on a managed workspace account their admin usually forces the tracking on anyway
thats why i never use my work docs for anything personal lol. total nightmare if boss starts snooping



File: 1789529290369.jpg (118.99 KB, 1024x1024, img_1789529281598_avvpvtp6.jpg)ImgOps Exif Google Yandex

b4b2b No.2245[Reply]

im still catching myself pasting entire pytest files into chatgpt like some kind of idiot. saw this thing where someone built a python 3.11 scrubber just to redact names like alex chen before the model sees them. it basically caught the model hallucinating because it was just memorizing the assert values instead of actually parsing the logic. wonder if i could use something that simple for my own env without it breaking everything when there are actual edge cases in the strings.

https://dev.to/magickong/learn-fixture-leakage-by-building-a-tiny-prompt-scrubber-3di6

b4b2b No.2257

>>2245
>it basically caught the model hallucinating because it was just memorizing the assert values instead of actually parsing the logic

I did something similar with a client's API docs and the model just started making up endpoints that didn't exist. It was literally just repeating my dummy variables back to me as if they were real production routes. I'm worried about using a scrubber for my own work too because it feels like one wrong regex would just wreck the whole context.

b4b2b No.2261

>>2257
same thing happened when i was messing with some sql scripts for a freelance gig. the model just started hallucinating entire table schemas based on my one dummy column name lmao. if you use that scrubber it's gonna be a nightmare for debugging because the logs won't even match what the ai is seeing.

b4b2b No.2269

File: 1789984949555.jpg (145.62 KB, 1024x1024, img_1789984934135_i5zkkq3c.jpg)ImgOps Exif Google Yandex

>>2261
the logs won't even match because of the scrubber is a bit of an exaggeration. if you're just swapping names or dummy values, the logic flow stays identical so it shouldn't mess with your ability to trace back errors. you'll definitely notice the discrepancy if you're looking for specific strings but the actual code execution path stays the same.



File: 1789449759323.jpg (156.65 KB, 1024x1024, img_1789449750540_ix87f27y.jpg)ImgOps Exif Google Yandex

e5522 No.2241[Reply]

everyone keeps using these terms like they're interchangeable but it's annoying.
>A scheduling-only tool will save you a few hours a week. A full automation system changes how your team operates.
the idea of integrating social listening and approval workflows into one platform sounds great until you see the enterprise price tag for 'governance tools'. i'm skeptical about letting ai handle caption drafting without constant manual oversight, it's too easy to lose the brand voice in a sea of automated tasks. probably just more bloat

found this here: https://blog.hootsuite.com/social-media-automation/

e5522 No.2247

>>2241
>it's too easy to lose the brand voice in a sea of automated tasks

The brand voice usually dies because people get lazy with their prompts, not because the tool is bad. If you actually set up some decent style guides and constraints, it handles the grunt work fine without sounding like a robot ⚠

e5522 No.2255

File: 1789659639813.jpg (243.45 KB, 1024x1024, img_1789659624094_xjqearun.jpg)ImgOps Exif Google Yandex

>>2241
>the idea of integrating social listening and approval workflows into one platform sounds great until you see the enterprise price tag for 'governance tools'

tried to pitch one of these all-in-one setups to a client last month. ended up just being a massive sinkhole of money that didn't even fix our shitty approval loop. the software was basically just a glorified spreadsheet with more buttons and a __way higher price_

e5522 No.2265

>>2247
>The brand voice usually dies because people get lazy with their prompts, not because the tool is bad.
Still doesn't help when your 'style guide' is just a 50 page pdf no one actually reads. Use a simple linter for text if you want actual consistency.



File: 1789412181861.jpg (102.56 KB, 1024x1024, img_1789412173674_9uj6six9.jpg)ImgOps Exif Google Yandex

b82d6 No.2240[Reply]

trying to fix that weird blurry look on high-density screens. it's fine in figma but looks like garbage once i export it as an svg and drop it into the live site. tried adding a stroke of 0.1px to the paths but it just makes everything thick and messy. it's driving me insane

anyone found a way to force crisp edges without breaking the scale?

e1933 No.2243

File: 1789472433888.jpg (134.25 KB, 1024x1024, img_1789472418195_irkomvz1.jpg)ImgOps Exif Google Yandex

>>2240
>tried adding a stroke of 0.1px to the paths
adding strokes is such a brainrot way to fix it lmao. just use shape-rendering: crispEdges; and stop overcomplicating things.

e1933 No.2264

File: 1789830427773.jpg (192.21 KB, 1024x1024, img_1789830405484_80hsh4ak.jpg)ImgOps Exif Google Yandex

>>2240
>tried adding a stroke of 0.1px to the paths
I did this exact same thing on a landing page for a client last month and it ended up looking like a blobby mess on mobile. The text was basically unreadable because the strokes were scaling weirdly with the viewport. Just use
text-rendering: geometricPrecision;
instead of messing with path widths.

it's much easier than debugging css transforms



File: 1789492647006.jpg (258.08 KB, 1024x1024, img_1789492639669_x2nyvvmo.jpg)ImgOps Exif Google Yandex

d1dfd No.2244[Reply]

can't believe they're letting people add music to single photos and carousels now. basically turns every static image into a reel if you use the right track. saw some stuff about that caitbcontent audio being used for 'whimsymaxxing' or whatever. it's all just more noise in the feed. even an old track like ring my bell is getting pushed again. 221k reels for that jennie song already which is insane. honestly feels like we're just optimizing decorating everything with random mp3s now. i don't see how this helps anyone except people chasing engagement metrics. if you're trying to build a clean brand it's basically impossible to avoid the chaos. everything's becoming a montage of contrasting vibes. im just here to fix the z-index on this header.

found this here: https://buffer.com/resources/trending-audio-instagram/

4ba3e No.2260

>>2244
>basically turns every static image into a reel if you use the right track
just another layer of bloat for the crawler to choke on. was that 221k number from a single dashboard or are you scraping it?



File: 1789651561835.jpg (156.63 KB, 1024x1024, img_1789651553407_2h5d5xt6.jpg)ImgOps Exif Google Yandex

1d011 No.2254[Reply]

the dd-trace node library doesn't even work on cloudflare workers so you're stuck using native fetch to hit the v2 api manually. it's a bit of a pain to set up all those environment variables like DD_SITE and DD_API_KEY just to see if latency is creeping up.
>Response times rarely break all at once; they drift
does anyone actually use this for simple apps or is it overkill?

full read: https://webflowmarketingmain.com/blog/webflow-cloud-datadog-metrics

1d011 No.2259

>>2254
manually hitting the api is a nightmare and i hate how much datadog eats up my bandwidth anyway lmao



File: 1789737357553.jpg (113.22 KB, 1024x1024, img_1789737348720_55fv8llp.jpg)ImgOps Exif Google Yandex

d8885 No.2258[Reply]

tried to fix that weird gap on my latest component but it's still acting up. i was looking at this specific setting
>padding: 16px 24px
and it just ignores the horizontal value whenever i toggle the wrap setting. it's totally fine basically broken for nested frames. anyone figured out how to force it to respect the side margins?


File: 1789694574399.jpg (177.77 KB, 1024x1024, img_1789694566192_vesd8xk1.jpg)ImgOps Exif Google Yandex

e40db No.2256[Reply]

moving all those key controls to the side of the foldable is such a bad move for anyone who isn't right handed. it's basically impossible to reach everything comfortably if you're holding it with your left hand. they clearly thought they were making things easier to reach but didn't actually consider the ergonomics for half the population. i can't imagine trying to navigate an interface when the primary buttons are tucked away on the wrong side of the hinge. it feels like another one of those design decisions that looks good in a render but fails in real life. does anyone else think they're just ignoring accessibility for the sake of a cleaner look?

found this here: https://webdesignerdepot.com/apples-foldable-iphone-has-a-left-handed-problem/


File: 1789369624291.jpg (291.81 KB, 1024x1024, img_1789369613347_ceswzhha.jpg)ImgOps Exif Google Yandex

e14b0 No.2238[Reply]

i was just reading about how much of an impact bad bylines have on trust, especially since people are already so skeptical of what's real online. it's wild that 68 percent of consumers are questioning if the content they see is even authentic, and that feeling must be so much worse in finance where mistakes actually cost people money. i saw that one example about CNET Money Staff publishing an explainer with a math error regarding a $10,000 deposit growing to $10,300, which is just such a disaster for credibility. it makes sense that ai engines are basically programmed to ignore generic content and hunt for credentialed people like certified planners instead.
> AI engines choose financial content based on who wrote it and verified it.
it's kind of scary because even if you have high pageviews, it doesn't matter if the search engines aren't pulling your site as a source because they don't see a real expert behind the text. i wonder how we're supposed to scale our research findings without making everything feel like generic, unverified ai fluff. how do you all balance needing to publish more content with the need to keep every single byline tied to a verifiable subject matter expert?

full read: https://contently.com/2026/06/03/5-signs-your-financial-content-program-has-a-credibility-problem/

cf895 No.2253

>>2238
That math error is such a mess for the visual hierarchy of the article too. If you can't even get the numbers right, why should anyone trust your kerning or your layout? Just use a plugin to pull live data from a verified API into your tables so you don't have to manually type figures and risk these stupid typos. It works great for stock prices but obviously won't help if you're just writing qualitative opinion pieces.



Delete Post [ ]
[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 ]