Search
1000 results for “commons_protocol”
-
cc @evan relating to earlier #TagsPub discussion we had on the matter.
This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.
Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.
More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.
-
cc @evan relating to earlier #TagsPub discussion we had on the matter.
This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.
Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.
More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.
-
cc @evan relating to earlier #TagsPub discussion we had on the matter.
This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.
Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.
More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.
-
cc @evan relating to earlier #TagsPub discussion we had on the matter.
This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.
Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.
More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.
-
cc @evan relating to earlier #TagsPub discussion we had on the matter.
This bot is already combining logic, has multiple 'profle logic' tags. Dunno if "NoBots" is also already common protocol-decaying practice.
Maybe a solution might be that an #ActivityPub bot actor - OT: which I'd personally perhaps had chosen to be Application, not Service actors - would have a botFlags property. Simple to implement, and #FEP that.
More involved but also much more versatile might be a "Botiquette" as:Profile, or even a bots:Botiquette type, and a namespace to register them at, and where others may find what they mean and how they operate exactly.
-
- a modern, easy to use SIP stack for use with a modern, easy to use programming language that actually supports common protocols
while working on #pixelebbe , i failed to set up a fax service over SIP for users to fax a simple document to me.
I don't want to have to set up a whole PBX just to discover that after installing ~80 closed-source libraries it doesn't connect to the SIP-Server because that server *offers* encryption and my PBX for some reason doesn't support that. -
Fwd: "A call for broadening the altmetrics tent to democratize science outreach" https://doi.org/10.1371/journal.pbio.3003010
"Furthermore, wider adoption of common protocols, such as ActivityPub in Fediverse, or of bridging services, such as Bridgy Fed, would allow greater visibility, communication and data sharing among media platforms." 1/
-
How about looking at the matter this way:
The #Fediverse is a federation of *loosely-coupled* systems that perform CRUD operations on structured data (#ActivityStreams) using a common protocol (#ActivityPub).
It's basically all driven by open standards vs proprietary #APIs.
Net effect, no instance has unilateral ownership of:
1. User Identity,
2. User Social Network
3. User Content -
@bhaugen these are great questions. As a general response, I have always argued that the key to making the #OpenAppEcosystem work is to make maximum use of common protocols. This includes making use of and supporting free code apps that already use them. Also, helping other apps identify which protocols fit their use cases, and how to implement them.
-
The “fediverse” is the term for the federated social web, a collection of social media concepts (Mastodon, PeerTube, Pixelfed, Friendica, Bookwyrm, etc.) that can all talk to each other by virtue of a common protocol: ActivityPub. The technical details don’t matter. What matters is that, in the fediverse, everyone can have a home without paying tribute to a private company or sacrificing their […]
https://steve.cooleysekula.net/blog/2025/09/28/bridging-science-to-the-fediverse/
-
Memoirs of the Early Internet
The Internet is an amazing place, and occasionally you can find things on the web that have somehow lingered online for decades longer than you might expect.
Today I’ll take you on a tour of some parts of the early Internet.
The Internet, of course, is a “network of networks” and part of its early (and continuing) promise was to provide a common protocol that all sorts of networks can use to interoperate with each other. In the early days, UUCP was one of the main ways universities linked with each other, and eventually UUCP and the Internet sort of merged (but that’s a long story).
Let’s start with some Usenet maps, which were an early way to document the UUCP modem links between universities. Start with this PDF. The first page is a Usenet map (which at the time mostly flowed over UUCP) from April of 1981. Notice that ucbvax, a VAX system at Berkeley, was central to the map.
ucbvax continued to be a central node for UUCP for more than a decade; on page 5 of that PDF, you’ll see that it asks for a “Path from a major node (eg, ucbvax, devcax, harpo, duke)”. Pre-Internet email addresses used a path; eg, mark@ucbvax was duke!decvax!ucbvax!mark to someone. You had to specify the route from your system to the recipient on your email To line. If you gave out your email address on a business card, you would start it from a major node like ucbvax, and the assumption was that everyone would know how to get from their system to the major node.
On August 19, 1994, ucbvax was finally turned off. TCP/IP had driven UUCP into more obscurity; by then, it was mostly used by people without a dedicated Internet connection to get on the Internet, rather than an entire communication network of its own. A few days later, Cliff Frost posted a memoir of ucbvax; an obscurbe bit of Internet lore that is fun to read.
UUCP was ad-hoc, and by 1984 there was an effort to make a machine-parsable map to help automate routing on UUCP. This was called the pathalias project, and there was a paper about it. The Linux network administration guide even includes a section on pathalias.
Because UUCP mainly flowed over phone lines, long distance fees made it quite expensive. In 1985, the Stargate Project was formed, with the idea of distributing Usenet by satellite. The satellite link was short-lived, but the effort eventually morphed into UUNET. It was initially a non-profit, but eventually became a commercial backbone provider, and later ISP. Over a long series of acquisitions, UUNET is now part of Verizon. An article in ;login: is another description of this history.
IAPS has an Internet in 1990 article, which includes both pathalias data and an interesting map of domain names to UUCP paths.
As I was pondering what interesting things a person could do with NNCPNET Internet email, I stumbled across a page on getting FTP files via e-mail. Yes, that used to be a thing! I remember [email protected].
It turns out that page is from a copy of EFF’s (Extended) Guide to the Internet from 1994. Wow, what a treasure! It has entries such as A Slice of Life in my Virtual Community, libraries with telnet access, Gopher, A Statement of Principle by Bruce Sterling, and I could go on. You can also get it as a PDF from Internet Archive.
UUCP is still included with modern Linux and BSD distributions. It was part of how I experienced the PC and Internet revolution in rural America. It lacks modern security, but NNCP is to UUCP what ssh is to telnet.
-
Here's the best Authorized_Fetch backgrounder I've found
My executive summary:
dot Social will send anything to anyone who asks for it, and will accept anything from anyone who sends it, although the details are complicated
"If Authorized Fetch is not enabled, requests to access public posts and profile information are anonymous. This is due to the current design of ActivityPub, the common protocol that all fediverse servers use to communicate with each other"
Here: https://hub.sunny.garden/2023/06/28/what-does-authorized_fetch-actually-do/
Bet Zuck is happy about this...
-
Let's go into the security side of things.
This is a follow-up to: Let's talk SMS 2FA and its shortcomings in the context of an energy crisis (and electronic components shortage)
For the value proposition of the SMS network to work (deliver texts whenever, wherever & in a timely manner), every part of it needs tight integration with every cell carrier on the whole planet. All carriers over the world agreed on a common protocol.
Since every country regulates its own requirements for mobile carriers in its borders, they all have varied requirements and incentives. This means that upgrading anything, protocol wise, has been reported to be a challenge. Interoperability is a necessity, therefore any changes are a detriment or can't happen.
Some consequences, without the recipient or the sender knowing about it:
- Any carrier asked to forward a message can see that message in clear text
- Any carrier along the chain can alter the text before forwarding it to the next hop
- Carriers can send copies to anyone, keep a backup indefinitely in their database etc
In some cases, the message can even be redirected to a different recipient altogether.
(These have all been reported to happen)
This is a systemic problem in the mobile carrier network. Neither senders nor recipients can do anything about it. By design, the messages aren't encrypted. There is risk of abuse.
Here's another issue: a phone number change.
Say you enable SMS 2FA on services X, Y and Z. Time passes and one day you change your phone contract, perhaps willingly, perhaps due to an emergency or any number of reasons. In any case, do you go back to X, Y and Z to do the 2FA change procedure? Do you remember that you need to do it before the old contract expires? Do you even have the time, if it was an emergency? Perhaps the next time you remember is because of a 2FA prompt on these services, but now the message gets sent to a phone number that is no longer yours. Do you ask a stranger to forward you the 2FA security code? Was the old number perhaps not attributed to anyone yet?
As hard as I thought about this recently, there is probably still a service out there where I set up SMS 2FA years ago and I have forgotten about it. The next time I change my phone number, that service will be lost to me.
Other minor failings inherent to SMS transport:
- Connectivity: the phone might not have cellular connection, perhaps located in a blind spot or the building is shielded, etc
- Battery: the phone might be out
- Credits: the sender failed to credit their account with their own service provider
- Third party: the service that is billing the service you are directly using, has an outage, went out of business, made a technical change that's incompatible with your direct service, etc, delaying their capacity to send SMS by anything from hours to weeks
Here are a few things we can do to help drive down the necessity for cell towers (and therefore network hardware production, cement, etc), as individuals:
1- Enable our mobile devices to favor WiFi over the cell network, for texts and calls. This doesn't work everywhere (mostly at home, friends and family, possibly at work) but it already represents a huge portion of the time we spend anywhere.
It's just one checkbox in our phone settings.
2- Disable cell data when we aren't using it, especially when we are using a more stable network (WiFi). The phone doesn't need to keep track of nearby cell towers when the local WiFi meets all our requirements. If the towers don't get pinged, their load decreases, they don't reach capacity, there is reduced need to build hardware redundancy, less electronics being produced, less strain on the energy requirements, less strain on the rare metals industry, less hydrocarbures required overall.
This is slightly more involved since we need to tap a button whenever we get home, but it's definitely doable.
(To be continued)
-
Many new people think Mastodon is too complicated. I think that's in part because some of its jargon is obscure.
"Server" = site
"Instance" = site
"Federation" = network
"Fediverse" = network (fancier term)
"Defederate" = block (a site)
"Toot" = post
"Boost" = repostThe "Fediverse" is a bunch of websites, running various software, talking to each other using a common protocol – as with email.
Much "complexity" can be fixed by speaking plain English.
-
- come to fedi, where @flancian has made a big web spider to let you [[wikilink]] into the web of everything.
- peertube is YouTube but if it made sense. does anyone have a visual demo of a p2p video streaming system?
- I haven't even used pleroma but it seems weird and cool, here is a practical example of why federation with a common protocol / different interfaces is uniquely powerful vs. platforms.
etc.are there any #zine #zines #fedizines around????
-
@Tutanota
Checking your own code is not an audit. An audit, by definition is conducted by third-parties. Users will decide who they trust to audit the client they use with your service, whether it's yours or a third-party one. If what you're doing is transparently secure, rather than depending on #SecurityByObscurity, surely it's based on common protocols, and standard crypto not #RollYourOwn, and has clearly documented specs that third-parties can follow securely.
@resist1984 -
@Tutanota
Checking your own code is not an audit. An audit, by definition is conducted by third-parties. Users will decide who they trust to audit the client they use with your service, whether it's yours or a third-party one. If what you're doing is transparently secure, rather than depending on #SecurityByObscurity, surely it's based on common protocols, and standard crypto not #RollYourOwn, and has clearly documented specs that third-parties can follow securely.
@resist1984 -
CW: Long Post: Intro to wtf a "Fediverse" is for new wafrn peeps
So, first off: Welcome!
glad to have you here, and I hope you'll like this little corner of the web :)
As you might've seen, people talk of "the fedi" or "the Fediverse" around here a lot, so I wanted to demistify that!
What the hell is a "Fediverse"?
Fedi is a place on the web, like where you are right now, but it's also a bit more than that. It's a network of people and communities, and the sites we use are also networked in of themselves.
On the Fediverse, there's a bunch of different sites that pass letters between eachother. These letters are the posts, the likes, the follows you leave and pretty much any other interaction.
When I follow-request someone, it's like sending them a letter from my home address (Wafrn) to their address (Mastodon.social) that says "Alexia would like to follow this person". When they accept it, I get sent a letter back that says "Your follow-request was accepted".
When I like a post, I send a letter "I liked this post" to the person that posted.
Posts themselves are also like this, but just sent en masse; When I post, I send a bunch of letters all around the internet, to every other site that Wafrn knows, that says "Alexia just posted!" that includes the post I just made. And the same goes for replies as well.
And everyone else does all of this too!
How does Bluesky play into this?
Bluesky is quite different! There instead of passing around notes, I just kinda write down my post, put it into a little ring binder with my other posts, and then there's this collection agency that looks at my ring binder tells everyone else about my posts. All posts go through this collection agency, so to speak.
very different in that sense!
What does "Fediverse" stand for, actually?
Fediverse is a combination of "Federated" and "Universe", where "Federated" is a word used to describe (in this case) how computers can work together with a common "language", or rather the proper term, using a common protocol.
The details of what protocol aren't too important, but if you're a nerd of that kind you may look into ActivityPub :)
#wafrn #new-to-wafrn #new-to-fedi -
The first use of common computer protocol was when Moses aborted the Egyptians' process with a control-sea.
-Tom Galloway
#Retromemes #computer #jokes #computingJokes #computerhistory
I'm doing a re-formatting of this e-book and out of nowhere the 90'ies say hello.
-
@trib @warkolm Would either of you be interested in testing out a HACS package for ingesting CAP-au (Common Alerting Protocol) feeds published by emergency management authorities, to generate alerts for any events nearby a designated location? (1/2)
#HomeAssistant #Emergency #EmergencyAlerts #CommonAlertingProtocol #Australia -
The OMN path, building the activist openweb infrastructure
The #OpenMediaNetwork (#OMN) offers a clear, practical path to (re)building the #openweb, grounded in #4opens. It does this by leveraging common open protocols like #ActivityPub (#AP) and #RSS, alongside existing #FOSS software, to create a distributed network of media platforms where people and groups can join, participate, and contribute. This, like the #Fediverse, is a challenge to the centralised, corporate-dominated structures which define so much of the current internet landscape.How to […]https://hamishcampbell.com/the-omn-path-is-building-the-openweb-infrastructure/
-
#politics, #politology, #sci-fi, #books @bookstodon
Anyone to provide references to some woks on political models of created worlds?
Think Stephenson's Diamond Age and its Common Economic Protocol. -
@virtualpierogi @sri @jsalvador @ben @nlnet
When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.
If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.
And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.
-
@virtualpierogi @sri @jsalvador @ben @nlnet
When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.
If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.
And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.
-
@virtualpierogi @sri @jsalvador @ben @nlnet
When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.
If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.
And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.
-
@virtualpierogi @sri @jsalvador @ben @nlnet
When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.
If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.
And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.
-
@virtualpierogi @sri @jsalvador @ben @nlnet
When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.
If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.
And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.
-
Yesterday I led a half-day workshop for a group of high school students. The content was purely practical: a lot of labs and hands-on exercises and challenges about computer networks, #networktrafficanalysis and #cybersecurity.
Girls made their own Ethernet cables to connect to our lab network. Then they analyzed common network protocols and their privacy issues and how the browser settings can affect the amount of sensitive information in the network traffic.
Pro tip: together with HTTPS-Only Mode in all windows, also enable DNS over HTTPS using Increased Protection or Max Protection.
Pro tip 2: even with those hardened settings, it is often possible to see which websites the user visits, because of TLS SNI or TLS CertificatesAfter that, the girls had the opportunity to try CTF-like activity in the lab network full of old #MikroTik and #Ubiquiti devices and virtual machines with various services exposed.
A little bit off-topic: This was the first workshop I completely led using my old #ThinkPad with #FreeBSD
#MayTheSourceBeWithYou
#PCAPorItDidntHappen#education #womeninstem #womenintech #SecurityGirl #AjTyvIT #wireshark #CTF #handsonlearning #learningbydoing
-
Yesterday I led a half-day workshop for a group of high school students. The content was purely practical: a lot of labs and hands-on exercises and challenges about computer networks, #networktrafficanalysis and #cybersecurity.
Girls made their own Ethernet cables to connect to our lab network. Then they analyzed common network protocols and their privacy issues and how the browser settings can affect the amount of sensitive information in the network traffic.
Pro tip: together with HTTPS-Only Mode in all windows, also enable DNS over HTTPS using Increased Protection or Max Protection.
Pro tip 2: even with those hardened settings, it is often possible to see which websites the user visits, because of TLS SNI or TLS CertificatesAfter that, the girls had the opportunity to try CTF-like activity in the lab network full of old #MikroTik and #Ubiquiti devices and virtual machines with various services exposed.
A little bit off-topic: This was the first workshop I completely led using my old #ThinkPad with #FreeBSD
#MayTheSourceBeWithYou
#PCAPorItDidntHappen#education #womeninstem #womenintech #SecurityGirl #AjTyvIT #wireshark #CTF #handsonlearning #learningbydoing
-
Yesterday I led a half-day workshop for a group of high school students. The content was purely practical: a lot of labs and hands-on exercises and challenges about computer networks, #networktrafficanalysis and #cybersecurity.
Girls made their own Ethernet cables to connect to our lab network. Then they analyzed common network protocols and their privacy issues and how the browser settings can affect the amount of sensitive information in the network traffic.
Pro tip: together with HTTPS-Only Mode in all windows, also enable DNS over HTTPS using Increased Protection or Max Protection.
Pro tip 2: even with those hardened settings, it is often possible to see which websites the user visits, because of TLS SNI or TLS CertificatesAfter that, the girls had the opportunity to try CTF-like activity in the lab network full of old #MikroTik and #Ubiquiti devices and virtual machines with various services exposed.
A little bit off-topic: This was the first workshop I completely led using my old #ThinkPad with #FreeBSD
#MayTheSourceBeWithYou
#PCAPorItDidntHappen#education #womeninstem #womenintech #SecurityGirl #AjTyvIT #wireshark #CTF #handsonlearning #learningbydoing