ASCII byte is 7 bits. 8 bits is an octet.
Today’s social media transform us into merely numbers.
No problem for me.
Alts: @Kierunkowy74 (kbin.earth) @Kierunkowy74 (PieFed)
Polish account: @Kierunkowy74
Mastodon: @74 or @Kierunkowy74 (alt)
ASCII byte is 7 bits. 8 bits is an octet.
1 floppy = 1.44 MO
1 CD = 700 MO
1 DVD = 4,7 GO
1 HD DVD = 15 GO
1 Blu-Ray = 25 GO
And the only region for whom the explore tab is working is America as nothing is localized.
Explore tab is sorted by language, not by region, so it works too for any sufficiently large foreign language country (Spain/Latin America, Portugal/Brazil, Italy, France, Germany, Sweden, Poland, Czechia, Russia, China, South Korea, Japan).
I wish Mastodon implemented Akkoma-style bubbles of related instances, which would allow to create, like, Explore tab but only from (manually selected) several Australian instances.
Vivaldi web browser opening their Mastodon instance brought me to the Fediverse. I started from Mastodon, but became curious of other fedi softwares - /kbin is one of them. I am on kbin.social as my Threadiverse instance in English since April '23, before Reddit API affair.
With biased by design I have meant something like Conservapedia, RationalWiki, etc… They do not try to make neutral point of view, as is (or at least should be) applied on Wikipedia.
You could peek at two opposing views on the same article, for example.
Post-truth as a service.
Wikipedia is not a Big Tech nor a commercial enterprise prone to enshittification nor it profits from surveillance capitalism. We don’t need another, competing, universal source of enclopedical information. Wikipedia, on contrary to X, Reddit, Facebook, etc. is not going anywhere. Any self-styled Wikipedia alternative ended up dead, thematic, or biased by design.
However there are many thematical and fan wikis hosted on Fandom, which itself is a commercial company and there were already some contoversies concerning it. Wikis on Fandom are very resource-intensive compared to Wikipedia or independent thematical wikis.
Ability to edit at several wikis from the same account without being tied to Fandom could be one of things that Ibis offers and could benefit independent wiki sites.
And of course, MediaWiki is free software and federation could be added as a functionality.
As you wish!
You are looking at subscriber numbers, and this table counts Monthly Active Users (who posted, commented or voted) of the community.
(yes, it is a table now :))
Its federation. Even to that point, than I can reply to you when not using Lemmy at all. I am writing this from /kbin.
You probably want to use a regional instance to have more relevant users, groups and events, but there is a global search engine for Mobilizon
For example, I am using a Polish instance, with an unsuprising domain https://mobilizon.pl
With an account, you are able to publish events, with header image, title, category, tags, date, place, description (with formatting available), and metadata. The event can be accesible publicly, or only via link.
The event (if public) can federate (and be boosted to e.g. Mastodon) and be commented, but you are able to turn off the comments.
Individual account can only be followed from Friendica, but not from Mastodon.
For more features you want to create a group. A group can be followed from Friendica and Mastodon, but only Mobilizon accounts can become its members. Group members are able to participate in discussions (not visible from outside), manage a “common resource folder” - links, make group events and group announcements
You can experiment with Mobilizon features with a demo instance
There is already a Meetup alternative - Mobilizon
From the project website:
Sublinks, crafted using Java Spring Boot, stands as a state-of-the-art link aggregation and microblogging platform , reminiscent yet advanced compared to Lemmy & Kbin.
But the author of PieFed, written in even more popular language than Java (Python) said:
The thing with the more twitter-style ActivityPub projects is they send activities to individual users inboxes a lot, whereas with the threadverse it’s all shared inboxes. So there’s a fundamental difference in the way they use the protocol which makes scaling those projects much more difficult. My gut feel is that adding full microblog support would increase the size and complexity of the codebase by at least 50% and triple the server load. Maybe much more. It just doesn’t seem worth it.
A feature creep?
(maybe they see a bus factor = 1 as the only issue of /kbin, though)
kbin.social federates with Threads