Would it make sense for Notesnook to be able to publish notes to ActivityPub? Is that a right use case for it or would it require hacks? What would be the best way to approach/implement this?
From a very quick research, it'd require a self hosted fediverse compatible server. Users would have to sign up or their accounts would need to be created there.
Thank you for putting out that query - short answer is...
Yes. You definitely have a use case here, but first, being just a little familiar with your product I'd like to welcome you to the #Fediverse even though your arrival coincided with the November Rain phenomenon that was much todo about nothing, and in the end, most Twitugees simply returned there after creating accounts here - I'm glad you stuck around! You're product is FOSS, and this is a #FOSS world here in the Fediverse, so it makes sense, this being your natural home and where people can expect to find you :)
Ever since I decided to ditch the proprietary Evernote, I've been using a #Vim Plugin that uploads my buffer to a Gist in an easy peasy way - it would be really kewl if I had a way to send (encrypted or unencrypted) notes to myself as a Fediverse DM, or share some of them with a select group of others in such a manner - Maybe (if it's textual in nature) actual clips I've saved. The graphics, well, if they are uploaded as a graphic that will work too, and they can even be sent to #Pixelfed accounts (if there is a graphics or movie file).
So, you're concerned about having to setup a centralized server or something that your userbase can be recognized on or something? Perhaps like a relay of sorts? I don't think that's the way to go actually. It sounds like a lot of heartache that might not even surivive beyond the intial proof of concept is rolled out - Spam being just one reason that makes the likelihood of failure a distinct possibility.
Here's what I think you can try doing, and it will alleviate any grandiose plans you may have been kicking around - Keep it in the client. A feature mechanism that either lets you clip and post it as an #ActivityPubNOTE to a user's actual instance (server) where they already have an account - You can collect the user's Fediverse account credentials and use that to post to their own existing account - no additional infrastructure is required on your part.
Those posts can be a single post to oneself (a private Fediverse DM to themselves) or it can include a list of recipients - just like any other post you can make.
This will also afford you the absolute maximum in #Spam_control too! You don't have to accept any registrations obo your Fediverse features - you're merely allowing people with existing Fediverse accounts to enter their credentials into your client and then your users make the decision as to whether they want to use your existing store or their Fediverse account to publish the clips to their stores there.
Since you've been around here for a while now, I'm sure you've realized how severely limited mastodon is when it comes to ways you can exploit the existing capabilities in the Fediverse - I've already mentioned Pixelfed, but there's a lot of other platforms that support HTTP signatures necessary for backfills and e2ee constructs; the support for BBCode and/or Markdown; post containing text with character counts greater than the paltry 500 characters that masto can muster, #LaTEX (actually, only Misskey and Firefish support that at this time AFAIK); local only posts (shared only with those who have accounts on the same instance), and a host of other unsupported features in masopub.
I appreciate that you made the effort to address this as an ActivityPub and Fediverse capability, and not simply, "yet another mastodon branded feature". Especially when mastodon won't be able to take advantage of many of the advanced features you already offer that other more capable Fediverse platforms can make use of :)
If you focus on adding support for people to enter their Fediverse account credentials, or multiple accounts like #Takahe and #Fedilab and #Misskey support, Then those are the servers you need right there! The spam problem remains as it is with the particular instances, since they control the new account registrations.
There's also the rapid adoption of #smolweb and single-user focused Fediverse platforms too, such as:
And of course, any platform, now matter how heavy or resource intensive can be deployed as a smolweb or single-user instance (even the klunky kludgey mastodon). And speaking of which, there are several popular forks that don't have these limitations that are very popular like #Hometown and #Glitch-soc, Etc.
There may even be some use cases for #Lemmy and #Kbin too, as link/discussion boards too - perhaps posting from a users vault/store to those platforms? There's a lot of different possibilities but ActivityPub can open up a huge market for you while at the same time Fediverse is exposed to large numbers of people who will discover that they too may have a good use case to adopt for themselves a Fediverse account :)
tl;dr: Basically, yes! there's a huge use case for your thoughts there - and if you're reading this on a Mitra, #Pleroma, Soapbox, #Akkoma, Firefish, Friendica, Hubzilla, or Misskey server, you'll see some very pretty formatting in Markdown - if you're reading this on a regular mastodon server (not one of the really good and popular forks), then... not so much - but at least mastodon does degrade Markdown and HTML somewhat gracefully :)
Well I hope that helps and do feel free to reach out to me via my contact methods listed in my profile or in the Fediverse-City Matrix room, and I'm sure that we can get a few of some of the more prominent Fediverse platform devs to round-table with you for some wire framing sessions.
I'm confident that you'll find a lot of support in your endeavor to achieve this initiative.
Wow. I just learned that my instance is going to close. No shade on the administrator — stuff happens. I'll move.
But an instance outright shutting down really exposes the hazard in posts being left behind when you move. Unless I archive and rehost them, everything I've written here will be lost.
Even if I do archive and rehost them, anything that linked to stuff I wrote here will be broken.
@interfluidity
Yet another example of why we need true #NomadicIdentity, like what Mike Macgirvin proposed 10-ish yrs ago for ActivityPub & subsequently built into #streams. (Just read a post about that but now can't put my hands on it.)
While the above examples can be used for images, Pixelfed was built for, well, images. It was made to cater for uploading photos ah sharing your digital artworks.
Meanwhile, Bookwyrm is best for, can you guess it? #Books! It features bookshelves where you can categorise your collection. You can also track your reading. Leave reviews. #Authors can too, if they want.
It's no different to comparing the old #Twitter vs #Facebook vs #Instagram vs #Goodreads. All of it can host photos and albums, but Instagram is focused on sharing images. Twitter for #microblogging. Facebook for socialising (or ads). Goodreads for books and reviews.
The difference? The latter are disconnected. While the former, the fediverse, are interoperable.
Serious question, no offense or provocation intended: With this stuff being baked into Hubzilla and, apparently, also design-wise into Bluesky / AT, can anyone out here involved with the #ActivityPub outline why nomadic / easily portable identity isn't built-in here by design? Looking at the (to-be-expected) dynamics of instances going up and down, blocking each other or moving to newer, different pieces of software, this seems an absolutely obvious requirement, so I wonder why this has been left out of the standard / spec?
While this is true, there's more history. At the time #ActivityPub became recommendation the people involved knew that important improvements were required in future iterations. This just never happened. Specs never evolved and projects created their own solutions.
For many years, what's now #Streams and #Nomad protocol, created by @mike has had nomadic identity. Why this hasn't picked up by other projects? Idk, getting such adoption is likely just as hard as evolving specs.
@smallcircles Yes, exactly, something like this was bothering me here while thinking about that, too. In quite some fields (including this, including, too, particular aspects of message delivery as seen in example in SMTP), it seems quite some interesting aspects of pre-existing technology have been omitted or ignored in #ActivityPub, and I'm trying to understand the reasons for that. Why not build on things and learnings that already have been made? Are/were, in example, the #Streams / #Nomad implementations or designs too complex for building on?
gonna plan out all my streams for this month tomorrow.
Streams every Thursday and Friday at 6PM Central, that's my standard now! gotta clear some stuff off my plate so I can focus on SPOOKY STUFF ALL OCTOBER!!
"Mike Macgirvin, former dev lead on Friendica and Hubzilla, is taking a proactive stance on the new changes [to the Privacy Policy of Meta's new fediverse-facing DataFarm] with an update to his new project, Streams.
...The new enhancement examines remote fetch requests against a list of who should be allowed to access a resource. It may prove to be a viable protection against excessive data harvesting."
#RadioFreeFedi ist eine Initiative, die zwei #InternetRadio#Streams (im #PLS Format) anbietet, welche ausschließlich Inhalte von MusikerInnen oder ProduzentInnen enthalten, die im #Fediverse zuhause sind. #Musik, #ShortStories, #Poems. Die Streams können z.B. mit dem #Mediaplayer#VLC abgespielt werden, aber auch mit verschiedenen anderen Playern, die das PLS-Format kennen, natürlich auch unterwegs auf Mobilgeräten. Nachfolgend verlinkter Artikel (en) hat die Details und kann euch auch weiterleiten, wenn ihr selber Musik oder kleinere Podcasts produziert und euere Inhalte in die Streams von RadioFreeFedi bringen wollt: https://wedistribute.org/2023/06/radio-free-fedi/
Recordings from Saturday 22nd July
📼 📼 📼
Sorry for the delay, folks! It's been a busy couple weeks... Thanks 🙏 to those that had a slot and to everyone who tuned 📺 in!
Files 📁 will only be available for 7 DAYS 🗓️ from today and require a password 🔒 to access, found below ⬇️.
RECORDINGS: https://cells.jnktn.tv/public/a8cd7c2c2d73
PASSWORD:
k^e5VVfE^nftMf342fS8kcD
Let us know if you have any issues 😖 accessing. #jnktn#streams#recordings#music#audio#video#online
@kalisz79@74@m0bi13@pawelszczur@ftdl@rysiek@miklo
Wracam do wątku z 26 lipca o publikacji #wydarzenia#events w fedi, bo to dla mnie ważne.
<dygresja1>
ciężko było znaleźć ten wątek – trzeba haszować tematy
</dygresja1>
Postanowiłem zrobić eksperyment i zrobiłem to samo wydarzenie w kilku miejscach, które obsługują wydarzenie jako osobny rodzaj postu.
Utrzymujemy wydarzenia na Friendice, ale wydarzenia są niewygodne w użyciu; zrobienie wydarzenia długo trwa – zdjęcie z linkiem trzeba wprowadzać ręcznie kodem.
Mniej więcej to samo na Hubzilli, tylko Hubzilla ma opcje pozwalające modyfikować, jak wydarzenie będzie wyglądać w AP (i tak wychodzi tak sobie).
Najwięcej nadziei daje Mobilizon z wtyczką do WordPressa (nie testowałem jeszcze). Ale instancja mobilizon.pl ma bugi (albo w ogóle mobilizon ma bugi) – brak opisów w niektórych opcjach (nie wiadomo, co się klika). Jeszcze inne błędy wyskakują i nie jest łatwo ustalić, gdzi się coś źle wypełniło, bo nie ma opisu. No ale generalnie działa.
#Wishlist:
• porządna instalacja mobilizon
• coś bardziej zaawansowanego niż Mastodon. Ja bym był za #Streams od Mike Macgirvin (pierwszy twórca Friendica). To jego ostatnie dzieło z porządnym szyfrowaniem i obsługą nomadyczności, uproszczone w stosunku do Hubzilli. To by była chyba jedyna publiczna instalacja na świecie tego, bo Mike się absolutnie nie reklamuje. Streams umożliwia też zaszyfrowane kanały i zasoby prywatne (potrzebne organizacjom): https://codeberg.org/streams/streams https://codeberg.org/streams/streams/src/branch/dev/FEATURES.md