Кто-нибудь знает ещё реселлеров, работающих за рубли, кроме asuka.host/ ?
А то там только OVH да Hetzner, которых блокируют, а мне бы что-нибудь менее мейнстримное
Asuka.Host – Хостинг нового поколения
Тут должна быть отсылка на Евангелион, но её не будет. Домены, хостинг, VM / Cloud и Dedicated.asuka.host
usr поделился этим.
@yesfreenet
тоже пробовал - открываю пару вариантов - установите какой-то софт и в нём сможете торговать
тут я перестаю понимать смысл этих действий и ухожу
можешь пояснить, зачем мне какой-то софт, чтобы переводить кому-то рубли? и как я должен проверить, что этот софт безопасен?
Ну тут лишь свои личные познание в коде помогут проверить. А так, если оплачивать, то стоит только через какие-то приватные криптовалюты, по типу XMR и ZEC (имеет открытые и скрытые адреса, будьте внимательны), Dash, тоже приватен, если использовать смешивание.
Это как агрегатором выступает. А доверять или же нет, это дело каждого.
Ну а так, реально раздражает, когда прям просят что-то скинуть, карту на фоне сделки, чек транзакции.
Но если так подумать, то есть треугольник.
Где есть картодержатель - злоумышленник - криптодержатель
Если картодержатель сделает транзакцию на номер криптодержателя. А криптодержателя отправит средства на реквизиты, которые дал ему злоумышленник, то тут уже будет проблема с законом, в которой криптодержателя останется без крипты. А картодержатель сможет вернуть свои средства заявлением в банк.
А злоумышленник окажется с криптой, которую он получил БЕСПЛАТНО.
Данных карт куча гуляет и аккаунтов банков. Стоит быть осторожнее.
Dmitry нравится это.
@yesfreenet
да, понимаю это всё
в таком случае - если припрёт - буду пытаться покупать у знакомых тут или IRL людей
идея крипты, конечно, крутая, а реализация вышла как обычно, с учётом человеческого фактора и обстоятельств(
Dmitry нравится это.
yesfreenet поделился этим.
Но это только Биткоин, причём предпочтительно на lightning, и нужно сколько-то уже иметь, чтобы внести депозит (обычно 3% от суммы сделки).
@yesfreenet @cybertailor
Оказывается, ASCII-арт это сложна, даже с редактором
Кто бы мог подумать...
yesfreenet поделился этим.
Оказывается, ASCII-арт это сложна, даже с редактором
А то ж! Непросто! Почувствуй себя во времена BBS. 😀
Ну вот нафига ты это подсунула?! Это же игрушка, в коротую можно играть бесконечно! 😀
Кстати, отлично работает оффлайн как сохранённая html-страница.
Считаю что это теперь лучшая экранизация фнафа
youtu.be/UiXy7pu9Jzc
cybermap.kaspersky.com/
#cyberattack #attack #cybermap #map #incident #hack #crack #spam
Какой будет моя ёлка в новый год.
#интересное
@amicalucis вроде бы когда-то кидала ссылку на онлайн карту кибератак, но плохо помнится. Поэтому кину Касперского, она более яркая 🤣
MAP | Kaspersky Cyberthreat live map
Find out if you’re under cyber-attack here #CyberSecurityMap #CyberSecurityMAP | Kaspersky Cyberthreat live map
Собрал себе новый вилсет на замену стоковому. Триггером было 5 проколов за неделю при отсутствии поддержки tubeless. Вес колёс улучшился на 10% и 17%. Сразу же обновил personal best на сегменте, где не мог этого сделать уже несколько месяцев.
В общем колёса решают!
#cycling #commuting #DTSwiss #Shimano
Dmitry нравится это.
поделились этим
Dmitry нравится это.
Against the dark forest
against the dark forest
The complex of ideas I’m going to call the Dark Internet Forest emerges from mostly insidery tech thinking, but from multiple directions.Erin Kissane (wreckage/salvage)
нравится это
поделились этим
кек, ладно, это шутка) Там из-за новых экспериментов директора и бухгалтерии зарплата (и аванс) дробится по куче статей и приходит кусочками. Этот пришел вот таким. :'D
Все равно, конечно, зарплаты на дне.
Когда-то мне выдали стипендию в сберкассе, я уже плохо помню процесс, но, по-моему, это выглядело примерно так:
- даёшь сберкнижку (бумажную) и просишь проверить
- её засовывают в типа принтер и в ней пропечатывается сумма на счету
- с восхищением смотришь на напечатанное, берёшь специальную бумажку и пишешь на ней сколько надо внести или снять, что и выдают
Сколько давали тоже не помню уже, но как-то крайне мало. И вот на мою бумажку в кассе посмотрели и сначала достали две купюры, потом передумали и выдали пачку самых мелких со словами "это чтоб побольше казалось" 😀)
Wandering Thinker нравится это.
У нас тоже плачут, что зарплаты на дне и условия труда - г-но.
Решил из любопытства посмотреть как работают на складах Озон. Там много людей работают. В т.ч. по вахте.
Прошел обучабщую смену и отработал одну стандартную смену. Так вот после этой "работы", я почувствовал себя не только олигархом но и оценил насколько шоколадные у нас условия. Попробуйте и вы сравнить, каково оно )
yesfreenet поделился этим.
о, у меня богатый опыт работы, и я, в общем-то, не жалуюсь на условия, разве что иногда ною, но это фигня. Есть с чем сравнить, от цеха до секретаря)
Этот пост не о том, что я жалуюсь, собсвтенно, а про то, как рисуют нашу работу обещания властей и почему-то кто-то этим обещаниям верит, потом начиная бычить на научных сотрудников.
Это ля всё из-за грантов, которые рисуют лямками, но их ещё и отработать надо.
А скрин можно сохранить? Думаю, что если буду думать, что я хреново получил, буду смотреть на него. И понимать, что наука, дело почётное, но не всегда прибыльное. Иногда всем бывает интересно сколько и где заработали.
Кажется, что главное не сколько, а как распорядишься...
okay i promise it’s last one for the night
i put a cutie inside the printer
поделились этим
поделились этим
нравится это
This is the way. We can all do our part to build and evangelize the fediverse.
And don’t say things like it’s too complicated or nobody will listen to us. That’s objectively not true.
There are 20 million fediverse users. Stay positive and keep moving forward!
@Шуро должны, но на улице такое говнище. Максимум - попросят очистить номер от налипшего снега
Там в правилах есть исключение, мол если вся машина как кусок говна, то и как бы номеру тоже можно быть таким же, но необходимо устранить загрязнение, если попросит сотрудник ДПС
This Week in Plasma: Battery Charge Cycles in Info Center.
blogs.kde.org/2024/11/23/this-…
This week we of course continued the customary bug-fixing, but got some nice new features and UI improvements too!
#KDE #Plasma #KDEPlasma #Linux #FOSS #OpenSource
Blue нравится это.
Технический комитет Linux Foundation официально объявил о временном отстранении автора BсacheFS
Управляющий технический комитет организации Linux Foundation (Technical Advisory Board) объявил об ограничении участия Кента Оверстрита, автора BсacheFS, в разработке ядра через запрет приёма pull-запросов на протяжении цикла формирования релиза 6.13. Решение принято на основе рекомендации комитета, отвечающего за соблюдение кодекса поведения в сообществе разработчиков ядра Linux (CoC Committee). Подтверждено, что причиной отстранения стало оскорбление Михала Хочко без последующего подтверждения способности дальнейшего участия в технических дискуссиях без личных нападок.
opennet.ru/opennews/art.shtml?…
Технический комитет Linux Foundation официально объявил о временном отстранении автора BCacheFS
Управляющий технический комитет организации Linux Foundation ( Technical Advisory Board ) объявил об ограничении участия Кента Оверстрита, автора BсacheFS, в разработке ядра через запрет приёма pull-запросов на протяжении цикла формирования релиза …www.opennet.ru
Но, увы, валенки мои были да сплыли. Хорошая обувь для неспешной зимней прогулки. Неподалёку, в одном небольшом городе, можно было за приемлемые деньги купить валенки ручной валки. Они были мохнатые и очень тёплые. Но производство давно сгинуло.
Помню у деда с войны было много проблем с ногами. Зимой они постоянно мёрзли дома, поэтому у него были домашние валенки. Обычные с виду, но носил их только дома.
Подыскиваю себе на зиму теперь хорошие валенки из натуральной шерсти. Может валяют ещё где в округе. Ох как хорошо сидеть в зимней засидке в валенках. Скучаю по этой не очень практичной, но тёплой обуви.
#зима #валенки
Купить валенки в Минске. Только качественный товар!
Валенки для зимы купить в Минске. Примерка и доставка. 300+ довольных клиентов.valenki-shop.by
🌟🐾 Check out my cutest #Animal of the Year contender! 🐾🌟
Can anyone help me with its name?
My best guess is... #EWOK! 😂
🖼️ 1: Ewok living its best life, blending in perfectly with Imperial life 🕵️
🖼️ 2: At night, taking out its Ewok attire, ready to join the fight against the empire! ⚔️
What do you think? 💬
Images CC0: madeindex.org
#Starwars #wildlife #Humor #animals #wildlifephotography #fanart #collage #illustration #imperialwalker #cc0 #photography #funny #cute #art #image #photo
Yay for the Dassie. They are a familiar sight on Table mountain and other rocky places in South Africa.
They have non-slip pads on their paws and designated toilet places.
Господа и дамы, скоро Новый год! Предлагаю устроить интерактив, а именно сыграть в Тайного Санту.
Тайный Санта — это игра, в которой участники готовят по одному подарку, а затем все подарки случайно распределяются между участниками игры. В начале игры выбирается ведущий. В данном случае им буду Я.
Желающие сыграть пишут в этом треде, что хотят участвовать. Приём заявок на участие будет происходить до 15 декабря включительно.
Далее, когда участники собраны, время готовить подарки. До 22 декабря включительно необходимо подготовить подарок и в личные сообщения написать ведущему (желательно с фотографией), что подарок готов. К сообщению необходимо приложить свои номер мобильного телефона и имя и фамилию, получателя подарка, а также адрес отделения CDEK, из которого вам будет удобно забрать свой подарок. Это необходимо для доставки ваших подарков. Бюджет и тематика подарка не ограничены.
Когда все подарки будут подготовлены, 23 декабря каждый участник получит случайный адрес отделения CDEK и реквизиты получателя (номер телефона, имя, фамилия). Доставку оплачивает отправитель. С этого момента можно отправлять ваши подарки.
По всем вопросам обращайтесь в ближайшее отделение CDEK или ко мне.
Я участвую! Присоединяйтесь и вы.
![The sun sets behind the sea, its reflection golden on the beach sand. [Fuji X-T5 / Tamron 18-300]](https://lastfree.space/photo/preview/640/730797 "The sun sets behind the sea, its reflection golden on the beach sand. [Fuji X-T5 / Tamron 18-300]")
ghost with a camera 👻📷 поделился этим.
Вот идёшь по воду, набираешь, возвращаешься домой и тут рвётся дужка, которая ручка. Зажигалка под рукой, поджигаешь, 20 секунд плавишь, плотно сжимаешь, приварилось. Дело меньше минуты. Да, можно и ручку другую, и бутылку, но зачем, если и так пока держит
Как-то так
Шуро нравится это.
How Decentralized Is Bluesky Really? dustycloud.org/blog/how-decent…
A technical deep-dive, since people have been asking me for my thoughts. I'll expand a bit on some of the key points here in a thread. 🧵
поделились этим
You know what, we'll come back to "bidirectional Conway's Law", let's talk about Direct Messages for a minute because I think those are telling
Direct Messages in Bluesky, wait how do they work if ATProto is public?
Did you guess?
DMs are centralized! All DMs flow through Bluesky
The point is that I have *seen in the wild* people saying "Oh yeah Bluesky added DMs to their decentralized protocol" and augh
I know they aren't claiming this but it's very clear to me that people are reading things as being completely different architecture than it is
But to Bluesky's credit, Twitter's DMs aren't decentralized either! And getting and shipping something that works, now for the influx of Twitter users, again... I am sympathetic
Bluesky's team is doing an INCREDIBLE JOB in that way of scaling to meet the incoming stream of Twitter refugees
On that note, again, I am not reading the replies right now because I am (a) afraid to and (b) I'm never gonna finish this and we are a bit over HALFWAY THROUGH the analysis but I have this fear that EVERYONE is mad at me, Bluesky fans, fediverse fans
I am trying to be analytical. I am trying!!!
I said we are about halfway through and criminy we're halfway through the afternoon, I need a break to get some tea
We have a few big topics left:
- Decentralized identity, how does it work (magnets too, yes)
- The Org is a Future Adversary
- Christine critiques the fediverse
- Wrap up
And so, it is TEA TIME
Go get yourself a hot beverage. Put honey or agave in it, if you like. Dairy, or perhaps, non-dairy, if you prefer.
=== BREAK TIME! Time for tea! ===
Okay, I am back and I am back with tea! I made "black tea with ginger" and I put some whipped honey in it. I also made tea for my spouse
I am drinking out of an oversized mug from @baconandcoconut that says "I'm that person who likes to serve on open source program committees", which is not actually accurate but I do anyway
I am also sad about the US House of Representatives being shitty to trans people who work there and are just trying to make it through the day
I used to do data modeling contracting for the US HoR on our legal system, true story, which sends me back to a time when I did a lot of data modeling
A lot of data modeling I did in that time was in the W3C Verifiable Credentials group that was working on Verifiable Credentials, zcap-ld (my spec), and, oh hey, Decentralized Identifiers (DIDs, the name is not my fault)
So actually I was pretty excited when I heard that Bluesky was gonna use DIDs!
Back in 2017 I wrote a whitepaper: "ActivityPub: from decentralized to distributed social networks" and it also suggested using DIDs github.com/WebOfTrustInfo/rwot…
I no longer think DIDs are necessary to solve this, but then and now I think *decentralized identity is important*
rwot5-boston/final-documents/activitypub-decentralized-distributed.md at master · WebOfTrustInfo/rwot5-boston
RWOT5 in Boston, Massachusetts (October 2017). Contribute to WebOfTrustInfo/rwot5-boston development by creating an account on GitHub.GitHub
In that sense, I am really glad Bluesky is taking on decentralized identity, as a concept! And DIDs, in a way, are a good signal.
But there are several problems, the first of which is: Bluesky supports two kinds of Decentralized Identifiers and they're both -- you guessed it -- centralized!
Before we get there, let's talk about what the DID spec was and what DIDs are. The core DID spec is an *abstract interface* for key management which provides a way of representing keys (and some other metadata) which can be created, retrieved, and updated/rotated.
So far so good...
The other requirement you would expect, based on the name, is that Decentralized Identifiers are *actually decentralized*.
When I got involved in DID work, that was actually the expectation of everyone. Then it was loosened. What? Why on earth?!
The reason actually stems from the first centralized DID method that Bluesky supports: did:web.
did:web is centralized, and kinda useless. It just works by a regex rewrite of the DID's name to an https URI and then it's retrieved. Anywhere you use did:web, you could have just used an https: URI
"Now wait Christine, didn't you say earlier that the web is decentralized and open? So therefore, did:web is decentralized and open"
Yeah but the naming system of the web is CENTRALIZED
We use DNS and ICANN (and then we add another centralization layer with TLS/SSL CAs)!
Everyone in the DID standards space KNEW that did:web was centralized, so why on earth was a centralized identifier permitted for something named "Decentralized Identifiers"?
The answer is easy. did:web is easy to implement, many DID methods were not.
did:web existed for test suites.
I was kind of exiting that particular area of standards when this happened but colleagues will tell you that I, and some others, were deeply upset and troubled by this
"Sure having a nearly no-op DID to pass the test suite is helpful but it shouldn't be labeled as a DID, people will get confused!"
Confusion, on its own, is one thing. But the problem is when confusion turns into decentralization-washing.
"This is going to turn into decentralization-washing!"
"It's just to pass the test suite!"
[... time passes ...]
"Actually we like did:web now, it's a DID method everyone can implement!"
But it's ONLY EXPERTS IN DIDs WHO UNDERSTOOD THIS
Most users hear "Decentralized Identifiers" and they think they know what's being delivered, the distinction between the *spec* being called that and the *mechanism used* being centralized... you have to go digging to find that out
So did:web is not only useless, it misleads people about the problem domain entirely, but hey it's now the most broadly deployed DID method in the world, congrats everyone!
Speaking of centralized Decentralized Identifiers, did I mention that did:plc is centralized?
For that matter, where did the term did:plc come from? Early versions of "did:plc" documentation called it the "Placeholder" DID method, that's what it stands for, to motivate changing it later
Well the docs no longer say that, it now says "Public Ledger of Credentials"
Good backronymn, but...
did:plc is centralized, and that bothers me because once again, users think something is more decentralized than it is, because they're being *told* it's decentralized
The particular way in which did:plc is centralized doesn't bug me too much but once again, few users have read into this
Aside from being irritated about the name misleading, I don't mind the centralization of did:plc too much (other things, I am more concerned about, we'll get there)
There's one organization that can be queried via their API that keeps a definitive list of certificate and their updates
In theory, once a DID is registered with Bluesky, it cannot be altered by Bluesky, because a cryptographic update from the original key is necessary; it's a certificate chain, a good design
Bluesky can refuse to share did:plc documents or their updates, but it can't manufacture updates
This is pretty good tbh, it lowers the stakes a lot to have certificate chains
I love certificate chains, certificate chains are great
Honestly, having a centralized registry for them, it's not the best but it's not the worst (aside from that damn naming thing)
However...
There are some strange, strange things about did:plc that heightens the centralization concerns and, well
I'm not a cryptographer, but some of my good friends are cryptographers, etc etc. I got some... reactions to what is to follow
The first strange thing to me is that did:plc uses sha256 and, AFAICT, not sha256d (which is really just running sha256 again over the hash). Unless I am missing something? Am I wrong?
Maybe it's not a concern because of doc parsing but it's best practice to protect against length extension attacks
The next concerning thing is that did:plc truncates the hash to just *15 bytes* of entropy.
I'm... again I'm not a cryptographer, but why throw away all that delicious entropy? So the did fits in 32 characters? Weird choice, and it means collisions are cheaper
This is public information, I don't need to file a CVE to tell you about the truncation of entropy. I am, again, not a cryptographer. Maybe it's fine?
I do remember the Debian short IDs fiasco tho gwolf.org/2016/06/stop-it-with…
Why not hold onto all the entropy you can get?
DIDs weren't meant to be seen by the user; cryptographic identifiers in general *shouldn't be*, they should be encapsulated in the UI.
We'll get to UI stuff in a bit.
I just don't understand this decision though, it just seems weird to me but maybe a cryptographer will tell me it's fine, actually
At any rate, I continue to not understand it, maybe it's fine, but it did play a part in that "Hijacking Bluesky Identities with a Malleable Deputy" blogpost, which is fascinating and, unlike me, is written by a Real Cryptographer (TM) da.vidbuchanan.co.uk/blog/hack…
Good post btw
One way in which the truncation shows up in that blogpost which I thought was curious is that the attack involved generating a *longer* truncated hash
The fix ended up resulting in codifying the hash length: 24 characters, and no longer github.com/did-method-plc/did-…
Constant identifier len of 24 by dholms · Pull Request #31 · did-method-plc/did-method-plc
Locks down the truncated hash to 24 chars Closes #27GitHub
There's another thing about that blogpost that caught my attention. I will just quote it:
> However, there's one other factor that raises this from "a curiosity" to "a big problem": bsky.social uses the same rotationKeys for every account.
At any rate, one way or another, you can presumably use did:plc to move yourself from one server to another so in the interest of "credible exit" this is a good choice
Though, one might take a moment to ask: who controls the keys if you *do* want to move?
Bluesky has identified, I'd say correctly even, that key management for users is an *incredibly* hard thing to do.
But the solution, once again, ends up pretty centralized: for all users on Bluesky's main servers at least, Bluesky generates and manages the keys for them.
I am, once again, kinda sympathetic and kinda unsettled simultaneously.
- Sympathetic: key management *is* hard and we just don't have the UX answers to solve that, and Bluesky is once again trying to deliver to Twitter refugees
- Unsettled: it's centralized, but... there's something *more* troubling
The big promise here, the "credible exit" side of things is that for most users, the vision they have is that if Bluesky gets bought by a big evil company, no problem, move somewhere else
But for those same users, Bluesky still *controls their keys* and thus *controls their destiny*
Regardless, Bluesky has this "your domain is your id!" thing, and that's pretty cool, the domain maps to your DID and your DID maps to your domain
Well, I'm not gonna get into this in detail here, I do on the blogpost if you wanna read it but, the cyclic dependency might be an actual cycle
tl;dr on that UX part:
- users only know domains, they don't know the DIDs
- turns out that's a phishing attack when those can change at any time
- if bsky.app ever goes down how do you actually know I *really* mapped to that name
- and a whole lot of "liveness" problems that enter there
It is time for TEA BREAK 2: THE REHEATENING
I will also go to the bathroom
TMI? If you've read this far into this weird thread I am already giving you too much info
=== TEA BREAK 2 ===
I have returned, with tea
I am still not reading notifications. Well, I have seen a few fly by on the fediverse which is blipping and blooping nonstop in the Mastodon UI so people are clearly reading it there
Bluesky says "30+". How big is the +?? I will resist temptation to look and assume "31"
"Where are we going with this Christine?"
Well you could have just read the blogpost but 3 more sections remain, we are approximately 2/3 there
I know, bear with me, what is left is:
- What should the fediverse do?
- Preparing for the organization as a future adversary
- Conclusions
Yes, I changed the order of the remaining sections, not from the blogpost but from the last time I said what was left on this thread
pray I do not reorder them again
Before we get into the next section, earlier I left an easter egg, which you could reply to and say "I found the easter egg" or something
Now you can put 2 eggs
I 2 was once an egg
(Look I specifically transitioned so I could never be accused of making dad jokes again so that does not qualify)
Alright you've heard enough critiques of Bluesky for a bit and I SAID I was gonna critique the fediverse and I am a WOMAN OF MY WORD
So let's get into it!
I have actually critiqued ActivityPub and the fediverse a lot! I have kind of never stopped critiquing it, ever since the spec was released. There's a lot that can be improved!
I have even gotten criticism from AT LEAST ONE ActivityPub spec author for critiquing AP-as-deployed but I do anyway
Actually something that is funny about ActivityPub is that there's "ActivityPub the spec", which I think is pretty solid for the most part, and "ActivityPub-as-deployed"
Many of the critiques I'm about to lay out we left holes in the spec for which I hoped would be filled with the right answers
One thing we have already discussed so, before I will say anything else, I will repeat: content addressing is really good, and I'd like to see it happen in ActivityPub, and it's *possible to do*, I even wrote a demo of it gitlab.com/spritely/golem/blob…
Bluesky does the right thing here, AP should too
README.org · master · spritely / golem · GitLab
Golem is a demonstration of how to distribute content over ActivityPub securely over peer to peer networks.GitLab
Content addressing is important. It should not matter where content "lives". It should be able to live anywhere.
A server should be able to go down, and content should survive.
Go content addressing!
Actually with this and several other things I am going to bring up, I actually made sure there was space to do things right: there was a push to make ActivityPub "https-only"
I pushed back on that, I didn't want that requirement, and it was exactly for this reason: enabling content addressing
This isn't the only time I left a critique of ActivityPub-as-Deployed as opposed to ActivityPub-as-it-could-be: see also OCapPub, which critiques the anti-abuse tools of AP as inadequate and leading to "the nation-state'ification of the fediverse" gitlab.com/spritely/ocappub/bl…
Oh, and ocaps!!!
ActivityPub left giant holes in the spec around two things which sound the same but which are not the same: Authentication and Authorization
Trying to mix these two, you accidentally get ACLs, and then you get confused deputies and ambient authority, plagues of the security world
Anyway, if you know *anything* about me, you know I am a big fan of capability security (ocaps) and that's the foundation of our work over at @spritely
But we will come back to ocaps in a second because it turns out OCapPub is not the only time I proposed AP + ocaps!
The other time I wrote about ActivityPub + ocaps was in a proposal to, yes, Twitter's Bluesky process in 2020 with Jay Graber titled... "ActivityPub + OCaps"! gitlab.com/-/snippets/2535398
I think that document laid out all the right ideas for *the fediverse* (not saying bsky, the fediverse)
Now I want to be clear here that I *don't* think that proposal was necessarily the right one for Bluesky, and I *do* think Jay Graber *was* the right person to lead Bluesky
What I wanted to do required a lot more research, and we have done that over at @spritely instead
The reason I bring up the proposal here is that I think it has all the right analysis of *what the fediverse should do*, if it was going to rise to the challenge of fulfilling its true potential
So let me lay out what the things in that proposal were:
Here is your recipe for making the "Correct Fediverse IMO (TM)":
- Integrate ocaps, which is possible because actor model + ocaps compose
- Content addressed storage!
- Decentralized identity (notice the *y*, I did not say DIDs) on top of ~mutable CAS storage
- Petname system UX
(cotd...)
(cotd ...)
- Better anti-spam / anti-harassment using OCapPub ideas
- Improved privacy with E2EE ("encrypted p2p" even a better goal)
Whew! An improved fediverse?
"Uh, Christine, this sounds like a lot, do you think the fediverse can take this on?"
The ocap stuff, I tried getting fediverse implementers excited about this and tbh, it's pretty hard to design into a Ruby on Rails or Django style framework and mindset. Backporting the right designs to existing systems is a real challenge.
Especially ocaps need to go bottom-up.
For this reason, @spritely's tech looks like it's very focused on computer science'y low-level BS, but that's actually because it's *too hard to build the systems I want right now on top of current technology*, we need stronger foundations
But people have to build for today too
Let's leave the ocap stuff to the side for now, then. Let's focus on what Bluesky and the fediverse have to learn from each other.
- The fediverse should adopt content-addressed storage and decentralized identity
- Bluesky should adopt real, actual federation and decentralization
Of course, adapting an existing system as deployed isn't easy.
I will say though that I think if Bluesky were to become *actually decentralized* it would look a lot like ActivityPub in terms of having directed messaging. This will also introduce similar challenges around eg replies, etc.
To the end of the fediverse, perhaps I sound bitter, "they didn't adopt ActivityPub the way *I* saw it!"
The truth is that Mastodon didn't, but Mastodon also saved ActivityPub. It then painted a vision of the future that wasn't, at least, what Jessica Tallon and I expected of it. But it saved AP.
The fediverse and Bluesky, at great effort, could learn a lot from each other in the immediate term.
In the longer term, neither is implementing the ocap vision I think is critical for the big vision, and in a way, I think maybe neither can be easily rearchitected to achieve it. Well, not yet.
When I laid out the ideas of OCapPub to various fediverse developers, the response was "this sounds cool but I have *no idea* how to retrofit a Rails/Django app for this kind of actor-oriented design".
And they were right.
Remember when I said Conway's Law flows in both directions?
Conway's Law says that a technical architecture reflects the social structure under which it was built. But the reverse is also true. The social structures *we can have* are made possible by the affordances of the tools we have available.
"Tech problems/social problems": false dichotomy.
Всё-таки, улун Дун Дин Морозного пика совершенно не получается пить "под работу" или "под книжку".
Каждый глоток - это "ух ты-ы!.."
Чайная медитация - и только она.
нравится это
yesfreenet поделился этим.
"Держу в курсе: в соседнем офисе сейчас спели Марсельезу, а потом сказали - "А теперь запишем этот алгоритм"."
Мы сидим несколько... в удивлении.
поделились этим
Чаще всего. 🤷♂️
поделились этим
Мя ��
в ответ на sad axolotl • • •Шуро
в ответ на Мя �� • • •Гороскоп говорит, что завтра будет понедельник.
Про день там нет конкретики. Предполагаю, что день наступит ближе к середине января.
Мя ��
в ответ на Шуро • • •как это нет конкретики, если гороскоп на сегодня?
@Chia
Шуро
в ответ на Мя �� • • •