POKÉMANIAC SIPH wants to fight! @Siphonay

0 posts0 participants0 posts today

ajftah yes, when your geolocation api is either broken, or simply doesn't cope with <a href="https://aus.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> and ends up making wild guessesps, dear vendor, I am in Melbourne

eXOfàsiaEn línia general, per aquí defensem que la infraestructura de fibra òptica hauria de ser un comú, de forma similar a les carreteres o les línies elèctriques. En ciutats com Zürich és el cas: una empresa municipal administra la part física, subcontractant el manteniment i la instal•lació si s'escau: <a href="https://www.ewz.ch/de/private/glasfaser.html" rel="nofollow noopener noreferrer" target="_blank">https://www.ewz.ch/de/private/glasfaser.html</a> Els proveïdors paguen a aquesta empresa municipal per l'accés a la part física (al mateix preu, totes les empreses) i competeixen en prestacions i atenció als clients finals, que poden canviar de proveïdor super fàcil donant el múmero del punt terminal de Fibra Òptica. Aqui això no és una realitat i llogar la part física, encara que sigui als grans, te sentit; però clarament no és una competència en igualtat de condicions. Apart de la capa física, hi ha moltes coses involucrades en un ISP (Proveïdor de Serveis d'Internet), i aquí és on potser la crítica a <a href="https://mastodon.social/users/somconnexio" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@somconnexio@mastodon.social</a> és parcialment vàlida, però cal ésser conscients que per la seva estructura cooperativista hi ha una sèrie de limitacions salarials que fan que potser no puguin assumir amb personal propi certes tasques; no és pas una qüestió fàcil d'adreçar, i segur que està en el seu ràdar. A eXO, per l'escala (petita!) i la tipologia de sòcies, tot el que va més enllà de la capa física ho porta l'associació mateixa amb feina voluntària i col•laboracions estretes; així els routers poden ser genèrics (n'hi ha amb <a href="https://exo.cat/fedi?t=openwrt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenWRT</a>, mikrotik, <a href="https://exo.cat/fedi?t=freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>, …), les IPs són pròpies (eXO és membre del <a href="https://exo.cat/fedi?t=ripencc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RIPENCC</a>), hi ha una IPv4 pròpia i una delegació de bloc /56 de <a href="https://exo.cat/fedi?t=ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>, si canviem de domicili les nostres IPs vénen amb nosaltres, i si ens hi volem implicar, podem involucrar-nos en l'operativa de l'associació, aprenent com es fa i com funciona internet en el procés. Sobretot el tema de l'escala petita fa que el preu d'accés a la capa física sigui alt, i que les despeses fixes es distribueixin entre poques connexions. Tampoc hi ha un ànim de lucre, inversions ni especulacions, així que els serveis s'han de poder sostenir econòmicament. Això fa que no sigui viable oferir els preus tan baixos com els que ofereixen altres ISP, però sí que baixaran, i sobretot contribuïm a mantenir una infraestructura de manera diferent, mancomunada i comunitària, i a poder oferir serveis al públic general com ara meet.guifi.net / meet.eXO.cat, que és operat i suportat econòmicament 100% per l'associació. CC: <a href="https://bcn.fedi.cat/users/marcelcosta" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@marcelcosta@bcn.fedi.cat</a> <a href="https://bcn.fedi.cat/users/polme" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@polme@bcn.fedi.cat</a>

Jima :Compromise_bi_flag:I understand I ultimately have you to thank for this, <a href="https://mstdn.social/@wesgeorge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@wesgeorge</a>... 👀😂<a href="https://mspsocial.net/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>

Nivex 🐧 📻I made a developer meme cc <a href="https://social.anoxinon.de/@Codeberg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Codeberg</a> <a href="https://tenforward.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a>

calcifer :nes_fire:I’ve got to know a lot of tech by sort of accreting knowledge over time, so I often don’t have a good answer to “how do I learn about XYZ?” type questions To wit, a friend just asked me how to get started learning about IP <a href="https://hackers.town/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a> and basic <a href="https://hackers.town/tags/networkSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networkSecurity</a> and… I’m not sure? Anyone have a good suggestion?<a href="https://hackers.town/tags/netsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netsec</a> <a href="https://hackers.town/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a>

Daniel Melzak<a href="https://mastodon.social/@gamingonlinux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gamingonlinux</a> "Added support for IPv6 for signaling" one of the best features that could be added to projects like this.<a href="https://mastodon.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a>

Alexey Vazhnov<a href="https://mastodon.social/@unfa" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@unfa</a> , just use <a href="https://social.tchncs.de/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> for a connection between the VPS and home infrastructure! 😉

goetz 🚲<a href="https://mastodon.social/@quux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@quux</a> Darfst Du, aber es geht bei <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> einfach ins blackhole.<a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> 7 de-fra04d-rc1-lo0-0.v6.aorta.net (2001:730:2d00::5474:8015) [AS6830] 17.815 ms * * 8 * * * 9 gate-3.heinlein-hosting.de (2001:67c:2050:5::251:1) [AS20546/AS199118] 32.131 ms * * 10 gate-4.heinlein-hosting.de (2001:67c:2050:5::252:1) [AS20546/AS199118] 32.300 ms * * 11 gate-4.heinlein-hosting.de (2001:67c:2050:5::252:1) [AS20546/AS199118] 2835.437 ms !H 2836.625 ms !H 1939.501 ms !H

goetz 🚲Everyone wanting <a href="https://chaos.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> to support <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> should up-vote this issue: <a href="https://github.com/orgs/community/discussions/151477" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/orgs/community/discussions/151477</a>

goetz 🚲<a href="https://chaos.social/@motp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@motp</a> <a href="https://social.mailbox.org/@mailbox_org" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mailbox_org</a> <a href="https://social.heinlein-support.de/@heinleinsupport" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@heinleinsupport</a> Traceroute würde nicht gehen, dass wäre gewollt so. Wurde von Support noch auf einen Knowledge Base Artikel verwiesen. Das aber auch ein curl -v6 <a href="https://opentalk.mailbox.org" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://opentalk.mailbox.org</a> nicht geht wurde von Support gar nicht verstanden.Es gibt einfach keine Route zum Ziel gibt. <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>

strifelNAT should have never been invented. If it had not been invented, we would have good <a href="https://chaos.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> by now

goetz 🚲<a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> ist hart. Eigentlich finde ich die Dienste und Angebote von <a href="https://social.mailbox.org/@mailbox_org" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mailbox_org</a> super. Habe aktuell einen Account dort, wollte aber mit mehreren weiteren dort hinwechseln.Leider sind die Dienste per <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> immer mal wieder kaputt. Aktuell sind das Support System (seit 4 Wochen), ein MX und OpenTalk betroffen.Wer kann denn einen <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> Mail/Groupware Anbieter in Europa mit einem vergleichbaren Leistungsumfang empfehlen?

Vivien GUEANTAccélération de la transition IPv6 ? Bouygues Telecom fait évoluer ses conditions de peering (interconnexion directe avec un réseau). <a href="https://mamot.fr/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> largement déployé devient un pré-requis: Bouygues demande au moins de 40% de trafic IPv6 pour monter l'interconnexion. ➡️ <a href="https://lafibre.info/peering/politique-peering/72/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lafibre.info/peering/politique-peering/72/</a>

gyptazyWe techies really are nerds living in our own little bubble. Every time I talk to friends outside of IT, they just laugh at the things we take for granted. In our world, it’s completely normal to assume that everyone has their own domain, self-hosts everything, avoids anything proprietary like it’s the plague, and probably has a dozen side projects running on some self-built server in their closet.But then there’s my friend, a mechanic, who finds this absolutely hilarious. To him, it’s like expecting every car mechanic to not only have their own repair garage at home but also to manufacture their own tools and, while they’re at it, maybe even start their own car brand. It sounds ridiculous when you put it that way - but to us, that’s just how things should be!<a href="https://mastodon.gyptazy.com/tags/nerds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nerds</a> <a href="https://mastodon.gyptazy.com/tags/geek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geek</a> <a href="https://mastodon.gyptazy.com/tags/geeky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geeky</a> <a href="https://mastodon.gyptazy.com/tags/hackers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hackers</a> <a href="https://mastodon.gyptazy.com/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://mastodon.gyptazy.com/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sysadmin</a> <a href="https://mastodon.gyptazy.com/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devops</a> <a href="https://mastodon.gyptazy.com/tags/cloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloud</a> <a href="https://mastodon.gyptazy.com/tags/socialmedia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#socialmedia</a> <a href="https://mastodon.gyptazy.com/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastodon</a> <a href="https://mastodon.gyptazy.com/tags/fedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fedi</a> <a href="https://mastodon.gyptazy.com/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://mastodon.gyptazy.com/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> <a href="https://mastodon.gyptazy.com/tags/server" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#server</a> <a href="https://mastodon.gyptazy.com/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://mastodon.gyptazy.com/tags/domain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#domain</a> <a href="https://mastodon.gyptazy.com/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a> <a href="https://mastodon.gyptazy.com/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.gyptazy.com/tags/niche" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#niche</a> <a href="https://mastodon.gyptazy.com/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.gyptazy.com/tags/runbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#runbsd</a> <a href="https://mastodon.gyptazy.com/tags/bsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bsd</a>

rvstaverenResistance lingers, old habits bind, Transition stalls, inertia's heavy weight, Yet IPv6, a beacon for the mind, A sea of addresses, vast and great.In the internet's evolution's tale, IPv6, the future, will prevail. (2/2) <a href="https://mastodon.online/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>

rvstaverenChatGPT, Create a sonnet about the struggle of <a href="https://mastodon.online/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> adoption in the InternetAmid the digital realm, a battle waged, IPv6, a protocol unseen, Yet in its promise, a future staged, A struggle vast, where change remains between.IPv4, the stalwart of the past, Its address space exhausts, a limit near, In cyberspace, a crisis unsurpassed, The march of time, a call we now must hear. (1/2)

Gυιdσ Kσѕтσиѕ<a href="https://mastodon.nl/@internet_nl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@internet_nl</a> Ik haal nog steeds 100% met mijn selfhosted webservertje op een Ziggo dual stack Internet verbinding. 👯<a href="https://mastodon.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://mastodon.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a>

Maddy, HD DVD enjoyerSo this latest Plex beta is pretty sick. I expected HEVC transcoding to make for more efficient bandwidth use, but I didn't expect HEVC transcodes to RETAIN Dolby Vision/HDR10 in the stream with HARDWARE transcoding (Intel Arc GPU on Linux) - I'm impressed!Also, peep that sexy IPv6 address 👀 Nothing in particular special about it, I'm just really happy to see more widespread usage. ❤️ <a href="https://hachyderm.io/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> <a href="https://hachyderm.io/tags/Homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Homelab</a> <a href="https://hachyderm.io/tags/Plex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Plex</a>

Colin Cogle :verified:<a href="https://infosec.exchange/@jerry" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jerry</a> Switch to <a href="https://mastodon.colincogle.name/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>, and then you can take a decade off while hackers deprecate IPv4. /s

John KristoffNo one apparently noticed until today that Google's <a href="https://infosec.exchange/tags/Gmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gmail</a> infrastructure appears to be using an <a href="https://infosec.exchange/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> transition mechanism 6to4 internally, and in a way that is technically in violation of spec. I realized they are mapping IPv4 10/8 addresses (see IETF RFC 3056).As Brian later points out in the thread, this is odd, but who cares?<a href="https://mailarchive.ietf.org/arch/msg/v6ops/wkvXhL8Z_Jy9fFFki_T2VnFi958/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://mailarchive.ietf.org/arch/msg/v6ops/wkvXhL8Z_Jy9fFFki_T2VnFi958/</a>I find it kind of fascinating that this has been going on for years. Operationally curious and and presuming Google has it's own internal 6to4 gateways for this and maybe other things. From a research and security perspective, I'm wondering if a collection of emails can be analyzed to derive any kind of patterns or structure. Practically I'll ask some Google people I know when I see them next and see if they'll just tell me more.

Recent searches

Search options

Administered by:

Server stats:

#ipv6