@shlee i've used, built, and/or sketched out enough Fedi user preferences pages to know that is too many knobs. so begin with one big switch that you have to pick an option on, get people started off right for what they're intending with their account
Posts
-
https://fediversereport.com/last-week-in-fediverse-ep-84/ -
https://fediversereport.com/last-week-in-fediverse-ep-84/@gabboman i've heard it on here as "Big Fedi vs. Small Fedi" (i think that phrase first came from @evan but if not i don't know where he got it)
this would be the per-user version. a UX challenge for instance server or even client devs.
-
https://fediversereport.com/last-week-in-fediverse-ep-84/@erincandescent @halcy is there a leaderboard? there should be a leaderboard. ladder ranked posting
-
https://fediversereport.com/last-week-in-fediverse-ep-84/i still think Fedi servers should show a PvP/PvE switch when you set up an account:
- one configures your account to opt into all the discovery stuff and to opt into future discovery stuff
- the other defaults you to unlisted, requires follow requests, turns on no-robot meta tags, opts you out of discoverable/indexable, hides your social graph, etc. and opts you out of future discovery stuff
then you can customize it from there if you care, but it's getting too complicated
-
https://fediversereport.com/last-week-in-fediverse-ep-84/Last Week in Fediverse – ep 84
Fediforum happened this week, mozilla.social shuts down, and Mastodon announces the Fediverse Discovery Project.
fediversereport.com (fediversereport.com)
During a FediForum session about Fediscovery, Mastodon CTO Renaud Chaput confirmed that between 8% and 10% of active accounts have opted into Mastodon’s search, a year after it has been released. It indicates one of the fundamental challenges of any design that is opt-in: very few people will change the default settings, irregardless of what the settings are about. As Discovery and Search systems gain value by covering a bigger network, it shows the fundamental tensions that Mastodon gGmbH will have to grapple with while building Fediscovery.
yeah that sounds about right
-
@oliphant question: does the concept of an ActivityPub relay (as the various pieces of software that do this currently exist) have any relevance to an island network? there are a variety of them but they seem to be universally poorly documented.@atomicthumbs @oliphant not Oliphant but if i was building a nontrivial island network and wanted complete federation within the archipelago (every federatable post available to every instance, so that any user can see any other user's total history, not just what happened to get there, and to provide a good federated timeline) i'd want relays to make this happen.
unfortunately GotoSocial doesn't support them yet, nor can it operate as one:
- https://github.com/superseriousbusiness/gotosocial/issues/1123
- https://github.com/superseriousbusiness/gotosocial/issues/1124
those are potentially on the GtS roadmap for next year
Glitch and Akkoma do support them already, though i think they both need to use external software. aode-relay seems pretty common on running relays i've seen recently
-
queers forming polycules for mutual support instead of benefiting from generational wealth is us favoring composition over inheritance@trwnh @erincandescent yeah no don't etymologize me. if someone calls me a fellow irl i'm going to fucking fight them, it's as gendered as "dude"
-
queers forming polycules for mutual support instead of benefiting from generational wealth is us favoring composition over inheritance@erincandescent not a fellow
-
queers forming polycules for mutual support instead of benefiting from generational wealth is us favoring composition over inheritance@erincandescent yep, gradually moving all my best posts over to this GtS instance for a future when i can shut down demon.social
-
I genuinely don't understand how a few dozen RPS from fedi server autofetch can bring down folks' websites@noracodes Eugen's boosted pictures of my cats on several occasions. a few link previews aren't shit compared to that, and i run on very low end VMs
-
queers forming polycules for mutual support instead of benefiting from generational wealth is us favoring composition over inheritancequeers forming polycules for mutual support instead of benefiting from generational wealth is us favoring composition over inheritance
-
Ohohoho this is interesting https://www.ietf.org/archive/id/draft-ietf-httpbis-safe-method-w-body-05.html@noracodes hell, it's about time
good find
-
princess.industries going down for a bump to current main (plus p.i special sauce)GtS updates taking like a minute is still a novelty to me vs. Mastodon
-
princess.industries going down for a bump to current main (plus p.i special sauce)princess.industries is back
-
princess.industries going down for a bump to current main (plus p.i special sauce)princess.industries going down for a bump to current main (plus p.i special sauce)
-
also curious to see if the akkoma frontend will properly render regular markdown from the glitch-soc frontend@erincandescent @alterae @alterae https://spec.commonmark.org/0.31.2/#emphasis-and-strong-emphasis to the best of my knowledge,
_foo_
maps to emphasis/italics in both Gruber Markdown and CommonMark, and underline was never in either -
also curious to see if the akkoma frontend will properly render regular markdown from the glitch-soc frontend@alterae @alterae Glitch's Markdown parser is cursed and nonstandard (known issue, bug open for years), and its HTML sanitizer is a bit aggressive, rendering headings as just bold last time i checked
GotoSocial's can handle some HTML in Markdown; i use the
<small>
tag all the time. Fedi posts get rendered to HTML when they get federated, and it's down to the HTML sanitizer of the viewing instance to decide which tags make it through, and then the client to decide which to render, if any.(Misskey-to-Misskey federation might be an exception, iirc they tack on the MFM source as an extra nonstandard property, but it's been forever since i looked into it)
-
people actually want working search, who knew?we can produce networks that work differently with existing Fedi software, but it'll still be enforced more by social contracts than by tech, and it won't look like Fedi, it'll look like this: https://writer.oliphant.social/oliphant/the-archipelago-an-island-network-in-practice
-
people actually want working search, who knew?you can have an account on mastodon.social and use their search today!
you can check out the repo for a Fedi instance server, cut out any search restrictions if it even had any to start with, spin it up, and connect to a big relay today!
you can use the FediBuzz firehose API today! it doesn't even require authentication!
i'm sure if you need commercial near-real-time access to most of Fedi with an SLA, someone's selling that, and they're incorporated somewhere that doesn't give a fuck about GDPR or CCPA
-
people actually want working search, who knew?replies to the announcement post https://mastodon.social/@MastodonEngineering/113125057908864709 don't get how Fedi works and didn't read the whole page but want to fight about it anyway
Fedi has always leaked like a sieve. everyone already has your public posts, including Meta. it was built for this.
sorry if you're learning this today but god damn. how many times are we collectively going to have to explain that in general, you can't control what happens on other people's computers