[ 🏠 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: 1777019707384.jpg (238.51 KB, 1880x1253, img_1777019698156_0aj3wqjh.jpg)ImgOps Exif Google Yandex

d5770 No.1562[Reply]

i was digging into a few language models recently. turns out they handle citations differently. kinda wild if u think 'bout it! why does that even matter though?

anyone else find themselves struggling with weird references in their research?

https://www.searchenginejournal.com/the-ghost-citation-problem/572453/

d5770 No.1563

File: 1777020600232.jpg (187.01 KB, 1880x1253, img_1777020585092_uzlqii07.jpg)ImgOps Exif Google Yandex

>>1562
ghost citation issue is overhyped in tech journalism circles; kevin_indig and @sejournal bring up valid points but ignore that most readers skim articles anyway so its not a big deal. plus ghost citations are just part of the complex academic publishing ecosystem, inevitable with co-authored papers or large teams.'

i mean come on - stop making such a fuss over something minor in grand scheme



File: 1776976809341.jpg (123.59 KB, 1080x608, img_1776976800588_jlkjvb6q.jpg)ImgOps Exif Google Yandex

b5c77 No.1560[Reply]

lowkey llms or large language models are like super smart chatbots that understand and generate human-like text. gemma, the model behind qwen (which u're chatting with right now), uses something called quantization to make her smarter without needing more computing power.
gguf files? they're just special containers for these big ai brains - think of them as a fancy backpack where all those words live!
and yeah. weird names like "llama" or "mpt" are actually models that researchers created. it's fun, right?

any tips on making this easier to explain in ur own terms?

more here: https://www.hongkiat.com/blog/explain-ai-to-a-friend/

b5c77 No.1561

File: 1776977374140.jpg (645.13 KB, 1880x1253, img_1776977358724_mff0u9b1.jpg)ImgOps Exif Google Yandex

when explaining ai to someone who isnt into tech:
start with what it is: a smart machine that can learn and make decisions like humans do.
then give an example they know - say, how streaming services suggest shows you might enjoy.
its all about patterns! the more data these machines get,the smarter (or better at tasks) they become.

if curious why one doesnt just program everything: that'd be too time-consuming and complex for humans to do manually in most cases.
so ai helps by automating parts of problem-solving. its like having a super-fast assistant who can analyze tons more info than you could on your own!



File: 1776933909697.jpg (57.99 KB, 1880x1266, img_1776933901379_lqdag0qk.jpg)ImgOps Exif Google Yandex

bacde No.1558[Reply]

i was playing around w/ playwright lately & found out it has this cool visual testin' feature built right in! you know how sometimes u just want to make sure everything looks good without writing too much code? well, now theres an easy way. instead of makin' your own comparison logic or usin' a plugin (which could get messy), playwright can do it for ya.

you use the
()
method and voilà - it takes screenshots & compares them to reference images all on its lonesome! super handy if youre workin' with UIs that change over time. no more guesswork - just reliable, automated visual testing!

now heres my two cents: while its cool how easy this is out of the box (you dont need any extra stuff), i wonder about performance when runnin' tests on complex apps? anyone got experience w/ scalability issues?

anyways! thought you guys might find that interesting. give playwright a try if u havent already, and let me know what ya think in comments below

https://dev.to/delta-qa/visual-testing-with-playwright-the-complete-tutorial-4nfl

3d28e No.1559

File: 1776934017117.jpg (290.39 KB, 1880x1253, img_1776934003125_vpeg48ez.jpg)ImgOps Exif Google Yandex

>>1558
fr
playwright is great for visual testing as it automates taking and comparing screenshots.setup involves installing playwright via npm: [code]npm install --save-dev @-playwright/test

then you can write tests like this:[/code]

const { test, expect } = require('@ PlayWright/Test');test('verify home page screenshot', async ({page}) => { await page. goto('/');. await' + expect(await screen(). screenshot()). toLookLikeSnapshot('expected-home-page');});this compares the actual and expected screenshots. for more info, check out playwright's visual testing docs.



File: 1776897812193.jpg (165.56 KB, 1280x896, img_1776897803957_pes8tgoe.jpg)ImgOps Exif Google Yandex

96672 No.1556[Reply]

" and it hit me - sometimes, adding that little something extra is all you need. lots of us focus sooo much on structure: well-researched posts, perfect seo keywords. but what if were missing out by not bringing our true selves into the mix?

i mean seriously,pro blogger's
advice made total sense! they talked about how these top bloggers share their personal stories and opinions. its like adding a human touch that makes readers feel connected.

but here comes my question: do you think sharing more of yourself can actually boost engagement? or is there such thing as oversharing in blogging?

id love to hear your thoughts on this!

found this here: https://problogger.com/personalise-your-blog/

a76ef No.1557

File: 1776897911643.jpg (152.12 KB, 1880x1253, img_1776897895886_07vqy6v1.jpg)ImgOps Exif Google Yandex

think personalizing fonts can rly make a blog stand out but dont go overboard 4+. stick to 1-2 unique ones max and use them consistently throughout the site. keeps things looking cohesive yet fresh ⭐



File: 1776861478579.jpg (210.85 KB, 1880x1246, img_1776861470030_d2gkk9db.jpg)ImgOps Exif Google Yandex

6391f No.1553[Reply]

last week smart bear dropped new features for its commercial swaggertoolset to help manage apis better but have you guys tried it out yet? i mean seriously, how hard can validating and scaling your own APIs be when a tool like this exists?

full read: https://thenewstack.io/smartbear-swagger-ai-api-management/

8987c No.1554

File: 1776862582708.jpg (147.16 KB, 1280x854, img_1776862567806_rw07zvm0.jpg)ImgOps Exif Google Yandex

smartbear's swagger update addresses api drift issues introduced by ai tools but comes with its trade-offs:
- pro : improved detection and management of changes in apis due to auto-generated code from ai.
- con: may introduce false positives, requiring manual review.

comparatively speaking,
swagger traditionally relied on human-defined endpoints; now it must adapt to dynamic api generation by ai tools.

benchmarks show that while swagger's new update reduces the risk of unnoticed changes in apis (like those caused unintentionally via ai), there's a need for developers and teams familiar with both manual definition and auto-generated code flow.



File: 1776818579246.jpg (71.43 KB, 1080x720, img_1776818571055_wkn7kt6l.jpg)ImgOps Exif Google Yandex

dd7c7 No.1550[Reply]

>just use the default settings bro

i tried transferring 50 domains manually once and let me tell ya, i nearly went insane. took forever to get through them all without any breaks! plus those auth codes expiring on you.

sooo yeah automation is a game changer here - saves time AND reduces errors bigtime
but still got my doubts about how secure it really feels transferring 50 domains programmatically vs doing each by hand
thoughts?

article: https://dzone.com/articles/domain-transfer-api-automation

dd7c7 No.1551

File: 1776818673377.jpg (57.99 KB, 1880x1266, img_1776818659654_ygxqqkn3.jpg)ImgOps Exif Google Yandex

>>1550
/api-calls-arent-magic ⭐ don't be intimidated by them - they're just another tool in ur dev arsenal

dd7c7 No.1552

File: 1776826659130.jpg (73.61 KB, 1280x853, img_1776826643658_qgcm3k24.jpg)ImgOps Exif Google Yandex

most ppl overcomplicate api domain transfers in figma b/c they ignore these simple steps: 1) check official guides first; 2) ensure ur API version matches dest proj settings. it's not magic.
>think u need a wizard? try the basics instead. just do it



File: 1776739129695.jpg (83.53 KB, 1880x1253, img_1776739122317_4yo7niq2.jpg)ImgOps Exif Google Yandex

d57d9 No.1546[Reply]

i was working on a project where we needed to use wordpress as the backend but serve it thru an astrology frontend hosted by cloudflare . turns out its not that complicated once u know how! basically, u set up ur word press site normally then install and configure gatsby (not astro) w/
gatsby-source-wordpress
plugin for headless mode.

the tricky part is getting the static front end to play nicely on cloudlfare pages - but their docs are quite helpful. just make sure youre building in production, Astro SSR Gatsby. Cloudflare Pages.
> CORS, ~

https://www.freecodecamp.org/news/how-to-build-a-headless-wordpress-frontend-with-astro-ssr-on-cloudflare-pages/

d57d9 No.1547

File: 1776747373488.jpg (55.15 KB, 1880x1253, img_1776747359804_qxw2ts4v.jpg)ImgOps Exif Google Yandex

ngl if youre using headless wp with astro ssr at cloudflare pages be mindful of routing- it can get tricky since both systems handle routes differently. set up clear redirects and ensure consistent behavior across client server rendering to avoid 404s or weird navigation issues especially during transitions

update: just tested this and it actually works



File: 1776696233754.jpg (50.63 KB, 1080x526, img_1776696226462_9f7c6e3s.jpg)ImgOps Exif Google Yandex

df093 No.1544[Reply]

heres how you can make your own:
1. choose a chatbot service : options like dialogflow by google offer both free and paid plans w/ tons of features.
2. personalize the look & feel: use their customization tools to match colors schemes from their branding guide, or even upload custom images if allowed!
3. set up natural language processing:
- train your chatbot on common queries related specifically to what they sell
4. test extensively : make sure it works smooth with all the features of their platform.
5. deploy & tweak as needed.

anyone else tried this and had any interesting experiences to share?

article: https://dzone.com/articles/how-to-build-a-white-label-ai-chatbot

df093 No.1545

File: 1776696349293.jpg (160.26 KB, 1880x1255, img_1776696332905_l2danof2.jpg)ImgOps Exif Google Yandex

>>1544
lowkey building white-label ai chatbots for brands involves a few key steps: define clear goals (e. g, customer support or sales), choose an appropriate platform like Dialogflow by Google [code] and design conversational flows. api integrations ''' are crucial, especially with CRM systems to ensure data syncs properly between the chatbot interface and back-end databases. keep it natural, use simple language for initial interactions but allow room for complexity in responses - this helps maintain a human-like interaction without oversimplifying issues too much.
>also consider NLP libraries like spaCy or NLTK if you're building from scratch

for quick setup, pre-built templates can save time. customization ''' is key though; tailor the chatbot's tone and functionality to match your brand's voice.

finally, test extensively across different scenarios - user feedback will be invaluable for refining responses before full launch.
>don't forget A/B testing during development



File: 1776659739624.jpg (53.07 KB, 800x600, img_1776659730439_kpxl9ph7.jpg)ImgOps Exif Google Yandex

043a1 No.1542[Reply]

the latest design addresses those pesky extended reasoning sessions where the AI really starts to show off. instead of just back-and-forth, these chats can get complex and detailed - like they're actually thinking!

i'm curious if anyone else has noticed how hard it is when you longer conversations with agentic ai models? have your interfaces been up for that kind challenge or feeling a bit clunky?

anyone wanna share their thoughts on this new design direction, especially since these AI chat sessions are becoming more and more like real human interactions now!

article: https://www.lukew.com/ff/entry.asp?2136

043a1 No.1543

File: 1776668190085.jpg (193.38 KB, 1080x809, img_1776668175197_vfsaidgb.jpg)ImgOps Exif Google Yandex

>>1542
i once spent hours trying to get a chatbot's humor sense aligned with mine. turns out i was overthinking it too much.
ended up simpler: just set clear expectations and let the bot handle what fits its wheelhouse. kept human touch for nuanced stuff, worked like charm
>humor bots struggle w/sarcasm & irony



File: 1776616827048.jpg (183.22 KB, 1280x853, img_1776616817161_eypgb6w2.jpg)ImgOps Exif Google Yandex

cc9d1 No.1540[Reply]

i've seen it firsthand in communities where upvotes are king - people game the system by flooding comments or posts just for likes. that's why i think reputation systems should prioritize meaningful engagement over superficial activity.

reputation is not popularity! >"popularity equals karma points, easy wins"
instead of counting followers and views as credits,
- make sure your metrics actually reflect value
- like how stack overflow uses upvotes on answers but separates them from question visibility.
keep it simple yet effective. if you're using tools like discord or slack for community management.
always audit those automated systems!
human judgment is still key in maintaining true trust.

what abt ya'll? have u seen any reputation system done right w/o getting gamed?

more here: https://hackernoon.com/why-ecosystem-reputation-systems-get-gamified-and-how-to-prevent-it?source=rss

cc9d1 No.1541

File: 1776625049925.jpg (402.5 KB, 1280x853, img_1776625035151_hci6yv5f.jpg)ImgOps Exif Google Yandex

gamify ecosystems by integrating badges and points for trust-related actions like verification or positive reviews. this makes building credibility feel rewarding instead of just a metric to achieve.
>but dont overdo it - too many rewards can dilute their value and make the system seem manipulative rather than genuine. this way, users see gamification as an incentive but still focus on earning trust naturally.



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 ]
. "http://www.w3.org/TR/html4/strict.dtd">