Seems to work on #MissKey.> They can convey meaning well
If everyone agrees on the meaning of the picture, sure, but this is not the case. Various emojis can have vastly different meanings to different groups of people. If you're also going to add in custom emojis this is going to be even worse, you're throwing around emojis that are literally undefined by the majority of the world population.
With your example "boosts appreciated", making a hashtag BoostsAppreciated is clear, concise, and accessible to all. I've never even heard of a dedicated emoji for this, and if you suddenly started to use those I'd have to wonder what you're trying to convey, and use the alt-text to actually get anywhere. Seems like more hassle than just using text in the first place.> They can be used in addition to other textual hashtags
This is true, but do you expect people to just use double the hashtags going forward? One with readable text, the other in image form which you then have to hope works in every context?> textual hashtags [...] aren't always as accessible in their meaning either
Everyone can make "bad" hashtags, but I don't think making the pool worse is going to improve that. If any, it'd make it worse, now people can make bad hashtags with both text and images.> There are cultures around emoji use, that give meaning in certain contexts, and those cultures are part of social fabric and cohesion then
That sounds like a rather big assumption. Are you aware of any cultures that are currently unable to use hashtags, that have a strict need to use basically any image they can think of? To me this sounds incredibly unlikely, especially in the context of the #Fediverse.
@stgiga Except your instance does not run 🐘#Mastodon, it runs 🦈#Sharkey (a fork of :misskey_mi:#Misskey, which itself was developed independently from Mastodon so is not a fork of the latter). If you want a more general, software-agnostic term, then call it a #Fediverse instance.
@stgiga@youronlyone@youronlyone & talking about #Fedi history by the way, since the doc itself says it is a living doc, there are a few notable instances not yet mentioned there that were recently developed by high-profile (or at least notable enough for us) Fedi users & might have verifiable links or posts that can give them a place within the doc’s timeline:
• #Fedibird (#Mastodon fork) by @noellabo
• #Sharkey (a very popular #Misskey fork) by @Amelia (& others from the @Sharkey project) since 2023
• maybe #IceShrimp (#Firefish fork?), unsure if it’s notable enough for inclusion or if supported by verifiable links (even I don’t know who created it).
I leave it up to @youronlyone whether certain popular extensions (if not forks per se) like #GlitchSoc (extending Mastodon) & #Soapbox (extending or modifying #Pleroma) can be added to the timeline as well.
Also, I will definitely not suggest for inclusion (or even a footnote mention) a certain #Akkoma fork that was given an obscene name by a fringe group of people (let’s just pretend it never existed, OK?) :ablobcatknitsweats:
They're the mascot for #SharkeyWorld, an instance powered by @Sharkey (cc: @ruud). It's a community of roughly ~120 members, and part of the rapidly growing squad of instances based on this #Misskey fork.
Haai is also the Dutch word for shark, and also is a homophone for a greeting (Hi!).
😂 That was odd! When I mentioned @darnell on my #WordPress blog, it pinged my #Flipboard account on my iPhone even though #ActivityPub is not yet activated (I received a push notification, which later revealed nothing 😆).
So I've run this poll until yesterday. The question was whether the Fediverse has quote-posts.
20 users voted for yes, 8 users voted for no.
Of course, this poll wasn't representative. I dare say my "bubble" is more Fediverse-savvy than the average, and I know I had quite a number of voters from Hubzilla and (streams). So the result is greatly skewed towards "yes". And still, 40% of all voters thought the Fediverse had no quote-posts.
This shows how well especially Mastodon users know the Fediverse.
Oh, and by the way: The Fediverse does have quote-posts. Just about everything that isn't Mastodon can quote-post, and it all can even quote-post Mastodon toots with next to zero resistance. And in fact, quote-posts in the Fediverse are about six years older than Mastodon.
I'mma just copypasta your hashtag line below ;) Let's not forget, in #Misskey parlance: #ReNotes - which arguably, might be the most etymologically correct of all of them, since most (at least masto) posts are 'notes', rather than 'articles'.
And in fact, quote-posts in the Fediverse are about six years older than Mastodon
That might be a good tidbit for Yuki to expand upon in his Fediverse history doc at Codeberg ?
Misskey, a decentralized micro-blogging platform, is in need of financial support.
Misskey is not a business, it is a non-profit, not a company.
The only income for the project comes from your donations.
If you like Misskey, please help us continue to develop it! https://www.patreon.com/syuilo
Those who donate a certain amount may have their name added to Misskey's credit.
Thank you for contributing to the future of Fediverse! #misskey
Tbh I'm not enthusiastic about a #Mastodon#hardfork. Not necessarily because of the #techdebt or even because it's technically inferior to other #ActivityPub implementations (which are both true), but because I cannot be sure if that new fork is going to adopt the same attitude as Mastodon in choking the rest of the #fediverse with its proprietary extensions and #EmbraceExtendExtinguish / #EEE.
I'd rather not have the uncertainty. Either start from scratch like #GoToSocial is doing or help the other two mainstream AP families which are #Misskey and #Pleroma. That's the only way we can ensure no implementation overwhelmingly dominates the fedi. :seija_coffee:
If your profile and posts are set to "public" and you can read this very post, you should have no sense of "privacy" here on Fedi. That means ANYONE can reply.
There's 20,000+ instances and new ones every day, there's NO WAY to tell who is accessing your posts or what they're doing with them.
Fediverse is not some kinda "bastion for privacy" nor is there any sort of "consent" required to see your posts if they are public.
The only way you can be 100% sure that your followers are the only ones that directly see your posts is to make your profile and posts private. Even then, screenshots exist.
Remember, you're on the internet. Once you post it, it's probably not going away. This is true everywhere.
If there were ever a single post that truly shows how running a Fedi instance is, that I could boost to the moon, it's this one.
People still somehow think that Fedi is "opt-in" or "privacy focused" or even "community focused". None of these things are true and I wish more people understood.
It's not a BAD thing, per se. I like it, personally. I choose who I want to interact with by blocking those instances I DON'T want to interact with, but it's OPEN BY DEFAULT is something some people can't grasp.😬
https://loops.video is a very promising ActivityPub platform for short form video, and could use your financial support to help fund and sustain this initiative!
I think the fedi needs to be more about clients/apps than it is currently.
Agreed, and I kinda touched on this earlier about how the #Threadiverse should've simply been a frontend where people just use their main fedi account instead of having to create another account for forums in a link aggregator... :sagume_think:
Tbh all the #fediverse implementations in the first place should've been backends first and foremost. Why should I not be able to have #Misskey's frontend in #Mastodon or #Pleroma? And the other way around too. This does mean that we will have to all agree on a common client API and MastoAPI will dominate, but I'd rather have Mastodon dictate client API than fediverse implementations. :seija_coffee:
I said it elsewhere, but I say it here too, I HATE how corporate social media sites have taken SOCIAL out of social media.
Thankfully the Fediverse is mostly taking that back. But if we don't expand to get those that are still on corporate social media to move here, then we'll just become the echo chambers we hate. That's why the Threads integration is a good thing. We need to expand.
PSA: Since Threads apparently will be federating replies soon, I thought I should post this again, because there's still a lot of people that don't know.
When a normal user uses "block this domain" it's LITERALLY just a MUTE. The blocked server can still see, interact, and reply to your posts, you just won't be able to see them.
It's kinda like sitting in a room with hungry bears while wearing a blindfold. If you're scared of hungry bears, your best bet is to get out of the room, not put a blindfold on. And by this, I simply mean to migrate to an instance where the blocks are up to your standard on the "instance" level.
Stay informed and make informed decisions, no matter what you choose to do with your Fediverse presence.
The main reason other AP implementations have added it (or in the case of #Misskey, made signing objects enabled by default which was a reluctant decision) as well despite Authorized Fetch / #SecureMode not being documented in the spec is that plenty of big #MastoAdmins have enabled it for their instances thinking it will prevent harassment from instances they've blocked (despite the fact that AF is purely #securitytheater), forcing the rest of the #fediverse to adopt it to remain compatible. Even at the cost of performance (no more caching).
This is plain ol' #EmbraceExtendExtinguish or #EEE for short against AP and the fedi by the Mastodon monopoly, and nobody wants to talk about it because it undermines the narrative a lot of Mastodon admins are putting out to justify their fediblocking of #Threads. Would've been fine if they focused on the (real) harms #Facebook did to Burma for example, that's a totally fine reason to block FB. But screaming EEE just makes me roll my eyes on their #hypocrisy. :seija_coffee:
One way to promote the #Fediverse is by making the different fediverse software support custom profile skins and themes. This can potentially create an ecosystem of skin and theme creators, which in turn will make more people talk about it.
I differentiate between a skin and a theme because:
A “skin” is like changing the CSS of the default layout. Adding an image here and there, new icons, and colours and gradients.
While a “theme” can change the layout itself. The widgets available, or shuffle them around. Possible even a way to add custom ones (careful with this though).
You can add, remove, and move widgets around. Use custom ones easily. Change colours easily. Change the widths, the columns, and so on. That is a “theme”. There were even third-party frontend packages a developer can use so they don't have to worry much about it.
Skinning is the simplest method; and this was what made #Plurk popular when it launched in May 2008 (yes, Plurk is as old as the Fediverse network). There was a Plurk skin ecosystem, which in turn increased the number of people talking about Plurk.
Apply the theming feature from the early CMS brands with Plurk's user-level skinning feature, and we create a playground for the users.
#Misskey and forks already had a good start with their user-level skinning feature (and user-level plugins at that). We just need to see it in the other popular fediverse software.
Make it easier to understand. Write guidelines in layman's terms, not dev terms, and maybe, just maybe, we can spark the interest of new users. Who doesn't want a customisable user profile?
I plan to close down my #calckey / #firefish / #misskey fork instance and then replace it with new software on the same domain name.
I suspect however that this will break everything and fail to federate properly with the new instance unless the Misskey instance sends what may be known as a "tombstone" message to it's existing contacts so that they know it's disappearing.
Think the problem will be that the private-key associated with the server will change, and so messages signed from the new server will be rejected.
Anyone successfully closed down an instance then bought it back with new software on the same domain name?
Anyone know if it's possible to get Firefish to emit these tombstone messages?
Or maybe backup the private key to be used by the new instance I guess?
Seems like these things will be impossible once the old server is deleted.
Yep, currently, #Misskey and forks cannot @-tag dotted usernames/webfingers. However, they can find and follow them. They won't be able to reply to them either.
I also replied and added a dotted username from Mastodon (since it works with it) and it appeared like this (see attached).
#Threads user with dotted username (an impossibility in vanilla #Mastodon) spotted in the wild federating with a #Misskey instance (namely, Voskey)! So, does this mean Misskey can handle dotted usernames & thus can further do what #Mastodont?
By the way, that #Threads account belongs to a small Japanese #bakery shop selling #cakes online, in case anyone here wishes to buy from them: @kashi.usuiro@threads.net
(Sadly, it seems you cannot yet directly @ them from #Misskey as the dot immediately breaks the ping for being outside the instance-domain-name part, so I had to fake the ping here by making it a #maskedlink to their URL.)
The year is 2028. All major open source projects are fully staffed and funded by multiple competing spy agencies who are constantly auditing other agencies work, implementing features as requested by their respected governments, as well as trying to slip malware past each other.
Paradoxically, opensource has never been more secure, maintainer burnout is at an all time low; and everyone does all work at a healthy pace during working hours.
Wayland even suddenly got good accessibility features implemented when it was realized that it made keylogging tools easier to write
@clacke@rgegriff@khinsen
Given that #Mastodon had had critical vulnerabilities until Mozilla started to investigate (other popular platforms such as #Misskey, #Peertube, #Lemmy aren't even being investigated of security and audited by independent trustworthy third-party), and the fact that Mastodon and its fork have far more Fediverse-enabled users than other non-Threads (not sure about this), non-Flipboard #Fediverse platforms, they are still a valuable targets for government agencies.