S
👍👍👍😁
Size: a a a
2019 December 31
S
Ребзя, а у кого есть опыт установки и работы в Qubes OS на интел-проце без VT-d ? Под двумя осямм - винда и линь.
NK
Без лишних разглагольствований хочу всем пожелать безопасного и счастливого 2020 года. Любите друг друга, делайте бэкапы и не забывайте вовремя ставить обновления.
Обнимаю всех, кроме одного.
❤️☃️🎄
Обнимаю всех, кроме одного.
❤️☃️🎄
2020 January 03
M
private (有需要私信): @Mionl
2020 January 04
G
Впн умер?
0
Свой впн пора иметь :) сервер в хецнере стоит 5 евро в месяц
G
Блин, купил подписку на 180 дней - уже второй сбой с полной преступностью сервиса (
w
Преступностью
EV
G
*недоступностью
G
Истекут оставшиеся 30 дней - перейду на другой сервис (
2020 January 05
V
S
Что это значит
V
послушай.
V
это значит, что всё, что ушло в эфир, может быть доступно кому угодно
ИА
Горячие дискуссии по поводу спорного выступления создателя Signal Мокси Марлинспайка на конгрессе #36с3 продолжаются. Вот, например, ответ команды Matrix.
ИА
Из комментов:
>A 'chat' client in the style of eg WhatsApp, but based on S/MIME over SMTP/IMAP, seems perfectly doable, and appropriate for most people's needs, with the obvious advantage of being supported by traditional email clients as a fallback.
>Additionally, message threading is the feature I most appreciate in a messaging system, but which is painfully lacking in most products (and no, Slack doesn't cut it). SMTP has built-in support for it.
>marcus_holmes 1 day ago [-]
>I'm old enough to remember when this was exactly how email was used. (but using a normal email client).
It was acceptable to send one-word email replies, and there were email chains of hundreds of emails (I was the guy who tended to "snip" them after 20 or replies).
>Now email seems to have taken over from where snail mail was: bills, newsletters, and formal communication. Chat is now the norm.
>Though I do notice a generational divide: one of my co-founders is in his 60's, and will phone randomly (which is now considered rude), another is a bit younger and prefers email to messaging, but will message to ask if it's OK to call. My younger colleagues send formal email replies, and use Whatsapp/Keybase for all other communication. I vetoed using Slack in the organisation completely ;)
>I wonder if in another 30 years, chat apps will be the formal channel, and something else will have taken over for just chatting.
https://news.ycombinator.com/item?id=21944875
>A 'chat' client in the style of eg WhatsApp, but based on S/MIME over SMTP/IMAP, seems perfectly doable, and appropriate for most people's needs, with the obvious advantage of being supported by traditional email clients as a fallback.
>Additionally, message threading is the feature I most appreciate in a messaging system, but which is painfully lacking in most products (and no, Slack doesn't cut it). SMTP has built-in support for it.
>marcus_holmes 1 day ago [-]
>I'm old enough to remember when this was exactly how email was used. (but using a normal email client).
It was acceptable to send one-word email replies, and there were email chains of hundreds of emails (I was the guy who tended to "snip" them after 20 or replies).
>Now email seems to have taken over from where snail mail was: bills, newsletters, and formal communication. Chat is now the norm.
>Though I do notice a generational divide: one of my co-founders is in his 60's, and will phone randomly (which is now considered rude), another is a bit younger and prefers email to messaging, but will message to ask if it's OK to call. My younger colleagues send formal email replies, and use Whatsapp/Keybase for all other communication. I vetoed using Slack in the organisation completely ;)
>I wonder if in another 30 years, chat apps will be the formal channel, and something else will have taken over for just chatting.
https://news.ycombinator.com/item?id=21944875
S
это значит, что всё, что ушло в эфир, может быть доступно кому угодно
А как же шифрование. Кстати, про wpa3 кто-нибудь в курсе?
P
А как же шифрование. Кстати, про wpa3 кто-нибудь в курсе?
Дырявый