home.social

#web — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #web, aggregated by home.social.

fetched live
  1. Falsas extensões de VPN na Chrome Web Store expõem dados de 75 mil utilizadores. Uma investigação descobriu 737 extensões maliciosas distribuídas por 40 contas de programador diferentes, fazendo-se passar por serviços legítimos.

    🔗 tugatech.com.pt/t89206-falsas-

    #chrome #dados #store #vpn #web 

  2. Falsas extensões de VPN na Chrome Web Store expõem dados de 75 mil utilizadores. Uma investigação descobriu 737 extensões maliciosas distribuídas por 40 contas de programador diferentes, fazendo-se passar por serviços legítimos.

    🔗 tugatech.com.pt/t89206-falsas-

    #chrome #dados #store #vpn #web 

  3. #Web3#Web4 も、ちょっと検索すると #Web5 ってワードまで出てきたけど、それ系にまったく興味がもててない :spam:

    🔗 Web3は失敗していない。ただし、成功もしていない|Crypto Matters | WIRED.jp wired.jp/article/sz-crypto-mat

    #Web3 はそもそも、その "Web" という言葉が意味するものを軽視してるというか、それを礎にした世界観の延長線上にあると考えるのがちょっと間違いというか、Web という言葉を冠する事自体にそもそも実態と違う印象を与えかねないので良くないと思っている。

    すくなくとも #WWW としての #Web の延長線上に、 #Web2.0 はたしかにあったけど、その先に #Web3 があるかというと、構図としてそうなってないと(個人的には)思う。

    #Web3 って、言葉では「分散型」とか説明されがちだけど、それは理論上・技術的はたしかに分散型と言える側面はあるとしても、どちらかというと既存の #WorldWideWeb の既得権益とか、たとえば既存の銀行組織とかを「中央集権だ」と否定的に見せるための道具として「分散型」を掲げているという側面がある(あった)と思っていて、

    実際に、上記の記事中でも

    > Web2.0は、すでに起きていた成功に後から付けられた名前だった。
    > 〜中略〜
    > Web3は逆で、まだ起きていない未来に先に付けられた名前だった。

    と書かれてるとおり、記事中では #Web3 は「消えたのではなく、分解された」と書いてるけど、
    実際には「 #Web3 は、その言葉が意味する現象がすでに現前したという誇大広告がなくては存在できなかったモノ」であって、つまり「消える以前にそもそも生まれてない」という方が正しいと思う。

    その「現実には存在しなかったものを差す言葉」である #Web3 の意味をあとから都合よくねじ曲げて、「Web3 の約束は AI の宿題になった」とか言われても、後出し感しか感じない。

    not fo me :drake_dislike:

  4. #Web3#Web4 も、ちょっと検索すると #Web5 ってワードまで出てきたけど、それ系にまったく興味がもててない :spam:

    🔗 Web3は失敗していない。ただし、成功もしていない|Crypto Matters | WIRED.jp wired.jp/article/sz-crypto-mat

    #Web3 はそもそも、その "Web" という言葉が意味するものを軽視してるというか、それを礎にした世界観の延長線上にあると考えるのがちょっと間違いというか、Web という言葉を冠する事自体にそもそも実態と違う印象を与えかねないので良くないと思っている。

    すくなくとも #WWW としての #Web の延長線上に、 #Web2.0 はたしかにあったけど、その先に #Web3 があるかというと、構図としてそうなってないと(個人的には)思う。

    #Web3 って、言葉では「分散型」とか説明されがちだけど、それは理論上・技術的はたしかに分散型と言える側面はあるとしても、どちらかというと既存の #WorldWideWeb の既得権益とか、たとえば既存の銀行組織とかを「中央集権だ」と否定的に見せるための道具として「分散型」を掲げているという側面がある(あった)と思っていて、

    実際に、上記の記事中でも

    > Web2.0は、すでに起きていた成功に後から付けられた名前だった。
    > 〜中略〜
    > Web3は逆で、まだ起きていない未来に先に付けられた名前だった。

    と書かれてるとおり、記事中では #Web3 は「消えたのではなく、分解された」と書いてるけど、
    実際には「 #Web3 は、その言葉が意味する現象がすでに現前したという誇大広告がなくては存在できなかったモノ」であって、つまり「消える以前にそもそも生まれてない」という方が正しいと思う。

    その「現実には存在しなかったものを差す言葉」である #Web3 の意味をあとから都合よくねじ曲げて、「Web3 の約束は AI の宿題になった」とか言われても、後出し感しか感じない。

    not fo me :drake_dislike:

  5. Reason to Rock Refresh Published

    My venerable Reason to Rock web book has had a refresh. Now a quarter of a century old, the new look is a bit more streamlined and modern. And all produced directly out of Notenik, via the Export as Web Site function, with all content converted from Textile to Markdown.

    related link: reasontorock.com

    #Notenik #Songs #Web

  6. @kubikpixel

    Das ist nun speziell an den Markt in Russland gerichtet und wer das Pech hat in Russland zu sein, ist so oder so verloren.

    In Deutschland gibt es aber RiseUpVPN, Tor, usw.

    #vpn #chrome #internet #privatsphare #itsicherheit #web #internet #it

  7. @kubikpixel

    Das ist nun speziell an den Markt in Russland gerichtet und wer das Pech hat in Russland zu sein, ist so oder so verloren.

    In Deutschland gibt es aber RiseUpVPN, Tor, usw.

    #vpn #chrome #internet #privatsphare #itsicherheit #web #internet #it

  8. Meet the Next Generation of Chefs Redefining Modern Mexican Cuisine in the U.S.

    “Our menu feels true to home,” says Bello, speaking of dishes like crunchy chalupa tortillas with salsa cruda and Parmigiano, wagyu tenderloin with barley esquites, and lamb barbacoa served with brown butter…
    #dining #cooking #diet #food #Cooking #CookingTopics #splitscreenimagerightfullbleed #web
    diningandcooking.com/2769889/m

  9. Meet the Next Generation of Chefs Redefining Modern Mexican Cuisine in the U.S.

    “Our menu feels true to home,” says Bello, speaking of dishes like crunchy chalupa tortillas with salsa cruda and Parmigiano, wagyu tenderloin with barley esquites, and lamb barbacoa served with brown butter…
    #dining #cooking #diet #food #Cooking #CookingTopics #splitscreenimagerightfullbleed #web
    diningandcooking.com/2769889/m

  10. #Typescript : l'annotation @ts-ignore c'est un peu un bazooka !

    Ça vous permet d'ignorer les erreurs typescript sur une ligne de code, mais cela ignore TOUTES les erreurs, pas uniquement une que vous voulez passer sous silence parce que vous SAVEZ que c'est une "fausse erreur".

    J'aimerai que la notation puisse désactiver une règle spécifique comme on le fait avec #eslint (// eslint-disable-line <rule>)

    Un truc du genre // @ts-ignore ts(2322)

    #dev #web

  11. WebMCP: come i siti web espongono strumenti agli agenti AI, spiegato con Cloudflare Browser Run

    WebMCP e' la nuova API del browser che permette ai siti di dichiarare tool strutturati per gli agenti AI, sostituendo lo screenshot-e-click. Come testarlo oggi con Cloudflare Browser Run.

    spcnet.it/webmcp-come-i-siti-w

  12. WebMCP: come i siti web espongono strumenti agli agenti AI, spiegato con Cloudflare Browser Run

    WebMCP e' la nuova API del browser che permette ai siti di dichiarare tool strutturati per gli agenti AI, sostituendo lo screenshot-e-click. Come testarlo oggi con Cloudflare Browser Run.

    spcnet.it/webmcp-come-i-siti-w

  13. 🧵 …wie oben schon erwähnt, VPN hat nichts mit Privatsphäre im Internet zu tun. Deren Anwendung ist für was Anderes da. Abgesehen davon ist Chrome ein Mist-Browser:

    «Hunderte irreführende VPN-Erweiterungen im Chrome Store:
    Über 500 betrügerische Browsererweiterungen hat ein Sicherheitsunternehmen im Chrome Web Store gefunden. Google lasse die Herausgeber unbehelligt weitermachen.»

    🕳️ heise.de/news/Hunderte-irrefue

    #vpn #chrome #internet #privatsphare #itsicherheit #web #internet #it

  14. 🧵 …wie oben schon erwähnt, VPN hat nichts mit Privatsphäre im Internet zu tun. Deren Anwendung ist für was Anderes da. Abgesehen davon ist Chrome ein Mist-Browser:

    «Hunderte irreführende VPN-Erweiterungen im Chrome Store:
    Über 500 betrügerische Browsererweiterungen hat ein Sicherheitsunternehmen im Chrome Web Store gefunden. Google lasse die Herausgeber unbehelligt weitermachen.»

    🕳️ heise.de/news/Hunderte-irrefue

    #vpn #chrome #internet #privatsphare #itsicherheit #web #internet #it

  15. We suspected it, it is now confirmed! 90% of our #Web services are victim of state #censorship in #russia according to github.com/runetfreedom/russia

  16. We suspected it, it is now confirmed! 90% of our #Web services are victim of state #censorship in #russia according to github.com/runetfreedom/russia

  17. I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

    HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

    I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

    Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

    I am thinking things like …

    • Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
    • Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
    • More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
    • Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
    • More obligatory metadata like authorship, tags, publishing/modification date etc.
    • Integration of non-search engine discoverability features like webrings, directly on a site level
    • Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
    • Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

    … and so on.

    I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

    And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

    #web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

  18. I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

    HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

    I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

    Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

    I am thinking things like …

    • Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
    • Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
    • More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
    • Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
    • More obligatory metadata like authorship, tags, publishing/modification date etc.
    • Integration of non-search engine discoverability features like webrings, directly on a site level
    • Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
    • Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

    … and so on.

    I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

    And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

    #web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

  19. My eyes hurt after the eclipse

    Searches for “eclipse hurt eyes” jumped 170% in the last 24 hours after the eclipse yesterday evening. Ouch. I hope those people didn’t stare too long and that no permanent damage was done. The sky was cloudy where I live, but I still managed to get a photo, even if it was only with myContinue reading

    odd.blog/2026/08/13/my-eyes-hu
    #cloud #eclipse #google #photo #Photography #Sun #Web

  20. My eyes hurt after the eclipse

    Searches for “eclipse hurt eyes” jumped 170% in the last 24 hours after the eclipse yesterday evening. Ouch. I hope those people didn’t stare too long and that no permanent damage was done. The sky was cloudy where I live, but I still managed to get a photo, even if it was only with myContinue reading

    odd.blog/2026/08/13/my-eyes-hu
    #cloud #eclipse #google #photo #Photography #Sun #Web

  21. My eyes hurt after the eclipse

    Searches for "eclipse hurt eyes" jumped 170% in the last 24 hours after the eclipse yesterday evening. Ouch. I hope those people didn't stare too long and that no permanent damage was done. The sky was cloudy where I live, but I still managed to get a photo, even if it was only with my phone as the clouds briefly allowed the sun through. So much for my plans to use eclipse glasses with my compact camera. Instead, I spent a nice evening with my wife, our pets and a neighbour who called over […]

    odd.blog/2026/08/13/my-eyes-hu

  22. Je viens de réaliser que cela fait 30 ans cette année que je fais des sites internet.
    Mon premier site est toujours en ligne.
    3/5e de ma vie.
    Tempus fugit...

    #web #internet #2026 #1996

  23. I still can’t believe this was made entirely inside Dreams on PS5. 🤯 The atmosphere, the voice acting, and the dialogue writing in this intro are next-level. This is what peak creativity looks like.
    Watch the full intro here: youtube.com/watch?v=eU-uNy_mmaI

    #DreamsPS5 #PS5Pro #GamingCommunity #IndieDev #Wrotmoore #freaksandgeeks #Bully #problemchild #rockstargames #aclockworkorange
    #ps5 #ps4 #pc #web #videogame #madeindreams #dreamsps4 #dreamsps5 #gameengine #games #fanmadegames #DreamsShowcase #indieg

  24. RE: mastodon.social/@arstechnica/1

    ShieldFont FTW! This is genius.

    "[C]reators should have a meaningful say in whether their work is used to train AI systems."

    "Where consent is not respected, technical design can make taking that work without permission less useful and more costly. … Being discoverable does not mean consenting to AI training.”

    #AI #ShieldFont #Web #WWW

  25. With the #OAuth server capability you can now even add Part-DB's #MCP server as remote MCP server in #ai clients like #claude or #chatgpt. No need to fiddle with configuration files and you can ask the Claude app on your smartphone questions about which parts you have in stock and where you can find it.

    #opensource #selfhosted #selfhosting #web #symfony #php