Searching We Love Privacy Club

Twts matching #shorts
Sort by: Newest, Oldest, Most Relevant
@asbjorn@norrebro.space
feeds.twtxt.net
 (3y ago)

I was introducing someone I know to #Mastodon a few years back, starting with:

“So let’s find a server that suits your niche interests. What are you looking for?”

…thinking that I knew all the fedi communities pretty well.

They responded cheekily “Is there a european-foreign-policy server?”

Of course I came up short, and they ended up making an account on a generalist server.

But fedi has grown a lot since!

So happy that eupolicy.social, respublicae.eu and social.netwo … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Ignite Realtime Blog: Certificate Manager plugin for Openfire release 1.1.1
The Ignite Realtime community is happy to announce a new release of the Certificate Manager plugin for Openfire.

This plugin allows you to automate TLS certificate management tasks. This is particularly helpful when your certificates are short-lived, like the ones issued by Let’s Encrypt.

This release is a maintenance release. It adds translations. More details are available in the [changelog] … ⌘ Read more

⤋ Read More
abucci
anthony.buc.ci
 (3y ago)
↳ In-reply-to » Dear Stack Overflow, Inc.

Seems to me you could write a script that:

  • Parses a StackOverflow question
  • Runs it through an AI text generator
  • Posts the output as a post on StackOverflow

and basically pollute the entire information ecosystem there in a matter of a few months? How long before some malicious actor does this? Maybe it’s being done already 🤷

What an asinine, short-sighted decision. An astonishing number of companies are actively reducing headcount because their executives believe they can use this newfangled AI stuff to replace people. But, like the dot com boom and subsequent bust, many of the companies going this direction are going to face serious problems when the hypefest dies down and the reality of what this tech can and can’t do sinks in.

We really, really need to stop trusting important stuff to corporations. They are not tooled to last.

⤋ Read More
abucci
anthony.buc.ci
 (3y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@carsten@yarn.zn80.net That’s a dissembling answer from him. Github is owned by Microsoft, and CoPilot is a for-pay product. It would have no value, and no one would pay for it, were it not filled with code snippets that no one consented to giving to Microsoft for this purpose. Microsoft will pay $0 to the people who wrote the code that makes CoPilot valuable to them.

In short, it’s a gigantic resource-grab. They’re greedy assholes taking advantage of the hard work of millions of people without giving a single cent back to any of them. I hope they’re sued so often that this product is destroyed.

⤋ Read More
xuu
txt.sour.is
 (3y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@movq@www.uninformativ.de

twtxt, as I believe it was originally intended, are short little status updates – that’s it.

So, basically a .plan file for finger. But, on the web. like a *web*finger. We have come full circle on this loop!

⤋ Read More
xuu
txt.sour.is
 (3y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@prologic@twtxt.net short version: context is a linked list that is passed down a call stack that can share timeout, cancellation, or other data as needed by lower functions in the call stack.

⤋ Read More
Oatmeal
feeds.twtxt.net
 (3y ago)

In reply to: Oatmeal - week notes

The worst kind of blogging is blogging about blogging, so, I’ll keep this blogging about blogging short!

I’ve made some minor updates to the design of the website that have improved it’s usability a wee bit, and are a step in the right direction toward upping my accessibility game. The major remaining accessibility issues are around color contrast and some structura … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Arnaud Joset: Updates: chatty server and HTTPAuthentificationOverXMPP
It’s been a long time since I updated this blog. It will be a short update post about two projects.

chatty_server

The first is chatty_server, a small XMPP bot I use to interact with my server. It allows me to get information about the CPU load, traffic, weather etc.
It also has a small feature to get reminder messages. There was a bug that allowed anyone to spam reminders. Anybody can add the bot to their rooster and could create random reminders t … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (4y ago)

Gajim: Gajim 1.4.6
Gajim 1.4.6 fixes some bugs with the status icon and notifications. Emoji short code detection has been improved.

Fixes and improvements

Several issues have been fixed in this release.

  • Improved detection of emoji short codes
  • Tray icon withlibappindicator has been fixed
  • Groups are now preserved when changing a contact’s name
  • Windows: Notifications shouldn’t appear in the taskbar anymore

Have a look at the [chan … ⌘ Read more

⤋ Read More
marcos-marado-atmind_booster
feeds.twtxt.net
 (4y ago)

**RT by @mind_booster: My latest @locusmag column is “The Swerve,” a short essay about the shape that hope takes when happy endings are off the table:

https://locusmag.com/2022/07/cory-doctorow-the-swerve/ 1/**
My latest @locusmag column is “The Swerve,” a short essay about the shape that hope takes when happy endings are off the table:

locusmag.com/2022/07/cory-do… 1/

![](https://nitter.net/pic/media%2FFW6b … ⌘ Read more

⤋ Read More
lyse
lyse.isobeef.org
 (4y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@movq@www.uninformativ.de @prologic@twtxt.net I just reread the spec and it seems to be even a bit outdated regarding machine-parsable conversation grouping. We long dropped the need to specify a whole hash tag with URL (#<hash url>), the simplified version without the URL (#hash) is enough.

The hash tag extension specification is kind of missing the same. However, I’m not sure if that short form is considered supported in general (as opposed to be a special case for subjects only) by the majority of the twtxt/yarn community.

Now the question arises, in order to keep things simple, should we even only allow the simplified twt hash tag for subjects and forbid the long version? This would also save quite a bit of space. The URL is probably not shown anyways in most clients. And if so, clients might rewrite URLs to their own instances. On the other hand, there’s technically nothing wrong with the long version in current parser implementations. And deprecating stuff without very good reason isn’t cool.

⤋ Read More