Hello there!
I’m also @savvywolf@furry.engineer , and I have a website at https://www.savagewolf.org/ .
He/They
Exfat does not support permissions, so when it gets moved to the drive, that information is lost.
If permission information is important to you and compatibility with non-linux devices isn’t, you can reformat the device as ext4 to support all linux features.
Oh is that what it is…
* awkwardly zips up pants *
If you’re itching to test Orion for Linux, you’ll have to wait. No public builds are available yet, and when testing versions do arrive, they’ll initially be restricted to paid Orion+ and Kagi subscribers.
If reading this has you itching to try it out, you’ll have to wait. No public builds of Orion’s Linux port are available for testing, and when available, the plan is to only give paid Orion+ and Kagi subscribers first dibs – crushing, but there is a reason for it.
Seems they didn’t give it a proofread before publishing. :p
Got curious about this.
One notable difference between X11 and W3C is the case of “Gray” and its variants. In HTML, “Gray” is specifically reserved for the 128 triplet (50% gray) . However, in X11, “gray” was assigned to the 190 triplet (74.5%) , which is close to W3C “Silver” at 192 (75.3%) , and had “Light Gray” at 211 (83%) and “Dark Gray” at 169 (66%) counterparts. As a result, the combined CSS 3.0 color list that prevails on the web today produces “Dark Gray” as a significantly lighter tone than plain “Gray” , because “Dark Gray” was descended from X11 – for it did not exist in HTML nor CSS level 1[8] – while “Gray” was descended from HTML.
I’ve seen people suggesting and using Anubis, haven’t used it myself though.
doesn’t rely on any servers or instances .
Yet is hosted on Github and presumably requires a working DNS and HTTPS system to download.
Users connect to your node directly, p2p, and nobody can stop you.
Except your ISP and/or government.
the protocol is text only, to embed media, you need to host it on the regular ( Centralized ) internet, and then you link to it like https://example.com/image.jpg, and the host will stop hosting that image and report your IP.
So your supposedly non-centralized project requires external hosting? It’s like NFTs where the images were just worthless links. :P Also, uh, base64 encoding is a thing and clients will absolutely start supporting it.
the community creator can assign mods, mods can remove posts from that community.
… Isn’t this what you’ve been trying to avoid?
if a community is badly moderated, the user will never see it, it wont be recommended to him.
Finally, a mention of content discovery. How is your recommendation system implemented? What decides whether a community is worth being recommended?
Also being p2p, seedit is not private, so it can’t really be used for illegal activity
Wait… Isn’t your whole pitch that it was censorship resistant? Can you clarify your threat model here, who are you actually worried about censoring your platform?
[ActivityPub servers] are hard to run and manage.
And using a completely unknown new service and protocol isn’t? I’m sure there’s tons of documentation out there for hosting Mostodon or Lemmy servers.
the problem with federated social media is that each federated instance is just a regular centralized sites.
I agree with this, but not for the reasons you’ve stated.
P2P also scales infinitely, which is the reverse of centralized websites like federated instances: the more users there are, the faster it gets.
P2P scales much worse than centralized systems. Centralized systems scale at N connections per node, while P2P systems scale at N^2 connections per node.
You know what, I don’t mind this project. We need a place for far right people to go to to avoid “censorship” (getting banned from a subreddit for doing nothing but throwing slurs at people) and collaborate on their “plans” (killing minorities) on a platform that is “private” (easily traceable, unencrypted and linked to your IP address).
Personally, I think that the discussion around this will evolve as the news spreads, but I agree with Robert on this one. Sure, X/Twitter has become a less welcoming place than before, but shutting out a significant portion of your community without seeking their input first isn’t a sensible move for such a foundational open source project.
Nah, I think I’m cool if Debian doesn’t respect the input of Nazi sympathisers.
TBF, they could probably make the “releases” page more prominent rather than having it buried in all the “code” stuff.
Syncing software is not a backup. I’ve had cases where they get confused and end up deleting data. They’ll also blindly copy over corrupted or randomwared files.