#ipns — Public Fediverse posts

RE: https://indieweb.social/@data0/115884351198568459

Last reminder: Are you using fedi-followers.data0.one ? If you do and want to continue using it, please migrate to the #ipns domain (more info in the quote toot below). The data0.one domain will be gone next week.

#ipfs #ipns #FediTools #followers #activitypub

RE: https://indieweb.social/@data0/114143860462112419

Are you using fedi-followers? If so, you may have to switch to another url because I'll dump the `data0.one` domain soon.

These will STOP working:
https://fedi-followers.data0.one (forwarder)
https://fedi--followers-data0-one.ipns.dweb.link (#dnslink url)

The direct #ipfs #ipns link will continue to work however:
https://k51qzi5uqu5dgivcxhlxa17kjyawt9kc5a2jdlq44o6kpxspltff5gi3sfyo4p.ipns.dweb.link

You can use the backup/restore function to migrate your data. (Remember, it's a local-only web app, your data only lives in your browser and is bound to the domain/origin.)

IPNS (Impertinent Périodique Non Subventionné)

Sortie du numéro 93 du journal d’information et de débat du plateau de Millevaches.

Au sommaire :

• Coupes de subventions, ça continue... Pas d'aide à la presse pour IPNS.
• Le « procès de Limoges » sera celui des technologies du numérique.
• Municipales : comment passe-t-on du nombre de voix au nombre de sièges ? La démocratie directe pas vraiment prévue par la loi.
• Réagir face aux attaques contre les associations.
• Le droit de mourir - « Réenchanter la mort » et « se réapproprier les pratiques funéraires », tels sont les objectifs de la Samaïn.
• Le Loup de la discorde. Quelle place pour l’homme et le loup en Montagne limousine ? Le loup en question et la réponse de l’historien, Jean-Marc Moriceau.
• Qui va à la chasse, une nouvelle revue nommée « Qui va à la chasse...quand des non-chasseuses amatrices de sciences sociales cherchent à lever des lièvres ».
• Jean-Claude Champeau, du braconnier au photographe et auteur naturaliste.
• 4 communes du Plateau solidaires d’une commune ukainienne.

Et plein d’autres choses.

Il est possible de s’abonner à IPNS (en soutien) via le @SyndicatPressePasPareilleSPPP (voir lien ci-dessous).

— https://www.journal-ipns.org/
— https://www.syndicatdelapressepaspareille.org/produit/ipns/

#MediasIndependants #PresseLocale #IPNS #PlateauDeMillevaches #Correze #Creuse #HauteVienne #Limousin

@agowa338 "self-distract". lol. I can't say for real because i'm just getting into #ipfs and formal local-first, but I've found quite a few videos about #ipfs #ipns #ipld on youtube. published in the last 5 years or so.

You might want to check out https://www.inkandswitch.com You probably heard of them but i wanted to post it for completeness' sake.

I recently learned about #IPDB; a distributed database used by #ATProto. I wonder if you could build an #ActivityPub implementation that uses #IPFS for content distribution, and IPDB for distributing the activity data.

#OrbitDB #BigchainDB #DID #CRDT #IPNS

@DimlyLitCorners got some updates from #IPFS leadership on BlueSky:

The crypto algorithm that IPFS uses for public keys and signing mutable names in #IPNS is getting added to #WebCryptography https://groups.google.com/a/chromium.org/g/blink-dev/c/T2kriFdjXsg/m/ZeD_PoLXBwAJ?pli=1

There is a draft spec for CBOR which IPFS uses to store structured data int he #IPLD graph https://datatracker.ietf.org/doc/draft-caballero-cbor-cborc42/

They are discussing it at the #IETF meeting this week in Spain

It seems they are breaking IPFS up into smaller pieces to get it through standards bodies more easily!

Here’s a short guide on how I host websites and single-page applications on the InterPlanetary File System (#IPFS). It covers running a node, #pinning data, #HTTP gateways, the InterPlanetary Name System (#IPNS), and how to get memorable URLs using #DNSLink.

(I've recently published some #browser #tools and #demos on the IPFS and thought you might be interested too. Feedback welcome!)

https://ipfs--howto-data0-one.ipns.dweb.link/

#decentralization #cdn #spa #html #javascript #css

Un petit marquis radicalisé de l’extrême droite en Creuse

Pour dissimuler la catastrophe que serait pour le département l'application du programme de son parti, l'Union des droites pour la République (UDR) d'Éric Ciotti, Bartolomé Lenoir utilise un subterfuge dont usent tous les extrémistes de droite : lancer des fake news et attiser la peur.

Vendredi 18 octobre 2024, sur France 3, il annonçait « une initiative forte contre l'extrême gauche en Creuse » (...) « Je ne veux pas que la Creuse devienne une ZAD » disait-il, au même niveau intellectuel que Trump et ses immigrés qui « mangent des chats. »

Lui-même riche angevin, très parisien et peu creusois, Lenoir sortait « je ne veux pas que des gens qui ne sont pas creusois nous imposent leur culture ». Et de questionner le ministre de l'Intérieur, le 12 novembre, sur la pseudo-«Zad » du  Chammet sur la commune de Faux-la-Montagne qui serait, selon lui, la base d'une centaine d'activistes d'ultra-gauche.

Dans une pétition lancée quelques jours plus tôt il cumulait mensonges et amalgames pour faire croire que le vrai problème des Creusois résidait dans un site tranquillement habité par quelques personnes où des activités tout ce qu'il y a de plus pacifiques se déroulent depuis un peu plus de cinq ans (...).

Voir en ligne le dossier publié par « IPNS », journal d’information et de débats du plateau de Millevaches : https://www.journal-ipns.org/tous-les-dossiers/dossier-lenoir-est-le-brun

#Creuse #Limousin #BartolomeLenoir #UDR #ExtremeDroite #IPNS #FachosHorsSol

I'm seeing an awful lot of Threads sourced nuggets espousing the virtues of, along with optimism surrounding, the #Fediverse lately.

This seems a bit sus to me, like a concerted outreach effort on the part of Meta/Faceplant and a few other largish, commercial actors to popularize their ulterior motives of domination by... Ahem, normalizing the concepts of #DeSoc and more specifically, the ActivityPub powered spaces in the Fediverse.

I actually dunno who MDBHD or John Oliver are, but I'm certain that they're no Oprah, although it would be nice if she would weigh in on the critical mass achieved to date in the adoption of Fediverse technologies that are #FOSS based, and #Privacy respecting.

To date, *Privacy has been of primary consideration and motivation in the development community surrounding the #ActivityPub powered platforms in the Fediverse, but the questionable players entering from the horizontally scaling decentralized social networking industry have, as of late, been overwhelmingly of the deprecated, privacy disrespecting, monolithic silo persuasion. These monolithic-ally inclined companies hailing from vertically thinking companies are an expected, yet suspect group of *privacy mining experts, sophomorically (sic) wading into the deep end of a demographic consisting mostly of privacy minded* individuals and notable developers of the FOSS based portions of the software world.

<tangent> These industrial surveillance engines are already back on their heels as they venture into what many warn as an #EEE incursion - but truth be told, already too late to the game to subjugate, assimilate us: #Diaspora #ZOT #nostr #Nomad #Matrix #TOR #Yggdrasil #I2P #IPFS / #IPNS and others, including blockchain based so-called #Web3 solutions with baked in privacy considerations at the protocol layer are being *Bridged to interoperate with each other and ActivityPub in the Fediverse at rates which the purveyors of industrial surveillance machinery must invariably only describe as "alarming rates" - that's good news for the average schmoes of the world like you and I. </tangent>

So why are we, just in the past few weeks, seeing so much attention given to the Fediverse by these #juggernauts, perhaps #dreadnoughts, that for so long have exhibited such great restraint and avoidance of the mere utterance of Fediverse, ActivityPub, or even alluding to the notions of Decentralization? There's certainly a particular spin in their delivery, leveraging third parties that obfuscate their participation in the dissemination of their, Great News.

Speaking of Dreadnoughts, just how was it that the great Bismarck was taken out? Remember? The outgunned and outmatched Royal Navy took out her port rudder! ⛵ 💥

It was the end of an era. A rudder post. The Bismarck was doomed to circle her watery grave.

But I digress...

Make no mistake, obscuring the lines between the privacy respecting FOSS based camps that have historically steered the direction of DeSoc has taken, and the deprecated, proprietary silo companies which have based their entire existence upon advertising and industrial surveillance models that I refer to as The Sunnyvale Syndrome family of data mining engines, is now seeping through the cracks of a clear delineation between these two prinicples - that of uncompromising privacy and open source development and that of proprietary, closed source subjugation methodologies leveraging **YOU as the product in inventory*.

Feel free to boost and share your comments at length here. A million people other than myself are here in the Fediverse and are really interested in just what kind of impact the introduction of these traditionally privacy raiding Industrialists will have upon their... scratch that, our future online safety.

tl;dr: Your very private, personal medical history and data (and that of your minor children, in violation of FERPA regulations) is being wholesaled and auctioned off by the so-called "Big-Tech" entrants and hopefuls that are at this very time knocking on the front door of the ActivityPub portions of Fediverse... Tread lightly, and consider how your every move going forward affects the unwitting consent to farm and sell your most confidential personal information.

it is up to you - it is your choice to affirm or deny - whether industrial surveillance is your birthright to embrace or your nemesis to destroy... You, We, have that power to decide.

#tallship #Privacy #Sunnyvale_Syndrome #meta #HIPAA #PHI #FERPA h/t to: @liaizon

⛵

.

RT: https://social.wake.st/users/liaizon/statuses/111714899199909225

@pearlbear I wish there was a way to have "permanent" domains. For example, .onion hostnames on #Tor and #IPNS identifiers on #IPFS.

starting with research data is a constrained problem to get some of the fundamentals of data structures, transport, and interop down so that in the next phase we can build identity, peer federation, and communication on top of that. we want to be able to handle bigg blobs of bits as well as liddel messages, and so making a p2p transport layer for RDF-like things leads naturally into the second phase goal of bridging the fediverse which runs on #JSONLD to p2p.

I still am not committed to actually building for RDF, want to learn from prior art without being weighed down by 20+ years of convoluted technical history, but there is a lot to learn about linking graphs there. I think one of the main things I am uncommitted to is needing globally unique URIs for everything, rather than having some things uniquely identifiable (eg. a dataset, a post) with relative locations for other things. That way you can make containers for encryption - peers can refer to the content hash of the encrypted subgraph as location for querying, zero-knowledge mirroring, etc. as well as opaque references to the graph content itself for peers that can decrypt it, but those inner-locations can't be resolved by peers that can't decrypt.

that is still a very unfinished thought, but it's a big missing piece in related technologies like #IPFS where everything must be addressable by CID. its arguably the need that #IPNS and #IPLD are intended to backfill

Did you know you can now use IPNS with ease????

It's cus I made a dope IPNS platform, and it's free to use!

https://ipns.app

Now giving out invite codes!

#IPFS #IPNS #Web3 #decentralized

@cameron @jamescridland

Where are these discussions taking place?

And what's wrong with email? I suppose using #ETH addresses for login, or #RetroShare, something like that might work, but you're still tied to DNS otherwise if that is the big beef with email... Just speculating though, which is why I asked.

If #DNS isn't the offender, then perhaps the simplest would be #Keyoxide, #Matrix, #Fediverse address or #XMPP account verification?

https://github.com/Cameron-IPFSPodcasting/podcastnode-Umbrel

#tallship #FOSS #IPFS #IPNS

Interesting thoughts!

https://esteroids.medium.com/lessons-learned-from-three-months-of-running-a-decentralized-website-e61b565f6cce

#dapps #dweb #ipfs #ipns

OK, so it was THAT easy to share my site on IPFS... 😅 Blog post possibly incoming in a few days. In the meantime, check my IPFS-published blog here :)

https://chrispanag.eth.link (or just chrispanag.eth if you are feeling Brave)

#brave #eth #ipfs #ipns

@dredmorbius Putting those tags on this clarification:

I don't want to now the deep ins and outs, I want a conceptual understanding of a few things to see if I can use it for a specific purpose.

The problem is that all explanations either wave their hands and talk about saving files "out there", or leap into details of hashes and content addressable stuff. There's nothing in the middle. Or at least, if there is, I haven't found it.

#IPFS #ipns #hivemind #dearlazywebs

@ColinTheMathmo Tagging #IPFS and #ipns might help ;-)

Also #hivemind #DearLazywebs

Okay, so, #Samizdat updates!

And I mean this also in the stuff-being-updated sense: #IPFS libs got updated. Tried updating #GunJS too, got told by devs that the whole 0.2020.x line is b0rked and unstable (why do you publish it as stable in npm then, *sigh*): https://0xacab.org/rysiek/samizdat/-/issues/62

Dived into implementing #IPNS+IPFS plugin:
https://0xacab.org/rysiek/samizdat/-/issues/2

Turns out in-browser IPNS is nowhere near ready. So implemented IPNS-via-gateway plugin (live on https://samizdat.is): https://0xacab.org/rysiek/samizdat/-/blob/master/plugins/gateway-ipns.js:

Ugh #IPNS is *slow*.

I am also more and more considering moving #Samizdat away from Gun. Gun is currently used to map from a well know address ( Gun user pubkey) to the content-adressed resources in IPFS. This can be done using #IPNS.

So far my experience with Gun has been bumpy. It seems a bit easier to use than IPNS, but with all the trouble I've had with it... not sure it's worth it.

I'll probably develop gun+ipfs plugin a tiny bit more, and then move focus to IPNS/IPFS. Added benefit: fewer dependencies.