Mastodawn

elmariachi Dec 22, 2022

Anne Roth Dec 22, 2022

Hab gerade den Teil des #LogbuchNetzpolitik zu #DigitaleIdentität und #eIDAS gehört (https://logbuch-netzpolitik.de/lnp447-videorekorder-fuers-internet?t=1%3A44%3A01%2C1%3A54%3A00)

Das ist die Gesetzgebung zu unser aller neuen Identität als gläserne Bürger*innen, das Ende jeglicher #Anonymität.

Bissi geschockt war ich v. d. bewussten Entscheidung von @edri *gegen* eine Kampagne dazu, berichtet von @socialhack .

Wobei natürlich letztlich nicht EDRi (allein) zuständig dafür ist, dass es netzpolitische Kampagnen gibt, aber liebe Leute: Hier gibt es ein Problem.

elmariachi Nov 29, 2022

tante Nov 29, 2022

Am 14. Dezember reden wir im Bundestag über #web3 und #metaverse. Und holy shit ist das zu großen Teilen eine fantastisches Expert*innengruppe. Mit @malteengeler @Lilith und @molly0xfff kann da nix schief gehen.

elmariachi Nov 26, 2022

used today's afternoon to rearrange the stickers on my x1's lid to better reflect my current stack. Decided to stay with that machine a little longer after upgrading to Fedora 37. Kept some older ones for nostalgia.

elmariachi Nov 26, 2022

Joshua Topolsky Nov 25, 2022

Just read a story about all the new social networks popping up/off right now and decided to look at Hive. The stark contrast between what they're doing and Mastodon is really something. Hive feels like a cheap knock-off of every network you already hate. Bad content suggestions, no interesting discourse, tons of people posting for clout... and just a terrible vibe. No thanks.

elmariachi Nov 23, 2022

Courtney Stubbert Nov 21, 2022

New report on Web3 tech -

Recommendation #3: “We need better research on the design, maintenance, and use of Web3 technologies.”

Agreed. Add putting UX researchers and designers on your web3 project teams to this rec. The long game is about usability, accessibility and equity. If those don’t exist you won’t have adoption.

Also, just quit using marginalized communities to whitewash your entitled excitement for new shiny tech.

https://www.mctd.ac.uk/crypto-and-other-web3-tech-is-being-used-experimentally-on-at-risk-communities/

#uxdesign #research #web3

Crypto and other Web3 tech is being used experimentally on at-risk communities

Refugees and low-income populations are at the frontline in absorbing the risks and failures of Web3 technological development such as cryptocurrencies.

mctd.ac.uk

elmariachi Nov 23, 2022

cstreet Nov 22, 2022

The only communities I'm seeing in the DAO space with activity in their servers now (that I am a member of) are the ones built for "humans first" and the some of the impactDAOs and protocols solving real world problems with #web3 tech. Other than that-- its a ghost town.

elmariachi Nov 22, 2022

Fission Nov 19, 2022

We're heading into the weekend by announcing our intent to add #IPFS support to #Mastodon

This means that media attachments can also be collectively shared across the fediverse, just like messages already are.

Initial funding page up on @opencollective if you want to support, and we'll dig in more on this next week! https://opencollective.com/fission/contribute/ipfs-media-support-for-mastodon-48315

Fission - IPFS Media Support for Mastodon - Open Collective

While ActivityPub federates messages and accounts, media attachments of images, audio, video, and other file attachments don't move in the same way. This will initially focus on adding IPFS storage of media to the Mastodon / Hometown codebase, so that …

elmariachi Nov 22, 2022

Boris Mann Nov 22, 2022

#FoundKey, a #NodeJS #ActivityPub server, has an open issue discussing #IPFS support https://akkoma.dev/FoundKeyGang/FoundKey/issues/222

via @dmitri

[Discussion] IPFS support?

Hi! I want to implement some IPFS support into Misskey/Foundkey, and I wanted to get some feedback about how an implementation should work and throw around some ideas First off, I'm not sure if this would fit into the main FoundKey repository or the goals, but I still wanted to ask around about how some of y'all think an implementation should work :p Also, I know deletion is an issue with IPFS, so any implementation would be opt-in and add addition warnings on the front-end about IPFS's permenance. I had some ideas: ## Simply store IPFS gateway URLs This wouldn't require any changes to the DB and not that much changes on the frontend either. The backend would purely handle connecting to a local IPFS node to upload the files, which would then be served via the gateway URL. Pros: - Simple! - Would work for most cases. Cons: - Would probably need regexes to determine how to handle IPFS files when you want to delete them - Tons of if statements to handle these IPFS links - Probably not elegant or maintainable - Not permanent, survives a rollback ## Store IPFS CIDs in the DriveFile database It would need schema changes but I feel would be the most elegant solution and is what I'm working on right now. Add an ipfsCID column to DriveFile, leave all other fields null; the client could then simply use ipfs:// URLs if the IPFS extension is installed or most likely use a new exposed `meta` property `ipfsPublicGateway` to get file links. Pros: - Would be a bit more code to add, but I feel would be a bit more maintainable and patchable compared to the previous option. - More explicit as to what files are on IPFS and what files are not. Cons: - Requires a breaking DB change, so you can't just change forks, and must apply the patch. ## ... For both options, there would need to be backend changes to support both a local IPFS gateway to upload and pin files, and to serve the IPFS links from a chosen public gateway. Also, I'm not sure how IPFS would interact with webpublic or thumbnails. My idea was to forgoe thumbnails and webpublic entirely when IPFS is enabled, but I have another idea that involves storing the webpublic, thumbnail, and original file under an IPFS folder. To me though, this feels like it would be another Misskey-ism and not fit very well with IPFS. Maybe the thumbails should be stored exclusively local, and don't use webpublic? Another idea to improve file availability: Expose IPFS Peer IDs through Nodeinfo so that other instances can add Fediverse peers as IPFS peers, which would help connect nodes and make files load faster through the DHT.

Akkoma Development

elmariachi Nov 22, 2022