Recent comments in /f/technology

cute_spider_ni_srsly wrote

Reply to comment by devtesla in wikipedia but BLOCKCHAIN by voxpoplar

Editing on Everipedia is modern and visually appealing. For example, we embrace memes (in a scholarly way, of course), incorporate GIFs within the copy, and display images and videos in a way to make them stand out.

wikipedia is dead

2

hollyhoppet wrote

Reply to wikipedia but BLOCKCHAIN by voxpoplar

“The Everipedia IQ blockchain provides a new paradigm change and knowledge economy to disrupt the old centralized internet knowledge encyclopedia model similar to Wikipedia. By creating a new incentive structure and a distributed backend hosted within a blockchain, the new Everipedia knowledge base will be able to improve upon all fundamental features of Wikipedia.”

How is this not a parody

4

devtesla wrote

Reply to wikipedia but BLOCKCHAIN by voxpoplar

How is Everipedia different from Wikipedia and similar sites?

  • Anyone can make pages about anything (as long as they are properly cited).
  • Editing on Everipedia is modern and visually appealing. For example, we embrace memes (in a scholarly way, of course), incorporate GIFs within the copy, and display images and videos in a way to make them stand out.
  • Talk pages are designed as discussion threads. This allows our editors to continuously discuss news-related items about their favorite topics.
  • Celebrities can have verified accounts. Not only does this allow them to have conversations with their fans on their own page, but they can also contribute information to their own pages... without having to rely on secondary sources!
  • Every page from Wikipedia is already here on Everipedia to build on top of and improve.
  • All these reasons make Everipedia the greatest knowledge project ever!
4

jaidedctrl wrote (edited )

Reply to Coding Is for Everyone—as Long as You Speak English by Moonside

yes, this!

I've been thinking for a while that we should switch from plain-plaintext to a sort of meta-plaintext. it could store multiple values in the same position; different text would be shown in your text-editor depending on the language, and it'd be converted to plain-plaintext when editing finishes (or programs would support this multi-lang meta-plaintext, or it'd be handled by the kernel/FS drivers somehow).

EDIT:

I.E., person A sees "<body>", person B sees "<korpo>", but both values are stored in the file at the index 1234. Indexes should be used for phrases (AKA meanings)-- "if true then {add 1 2 3}" would be one index, let's say 3. There can be many different values per index (for multi-lang)-- there might be an esperanto index at 3, too, "se vera do {adici 1 2 3}". The particular index displayed would be determined by your language, or the one you specify.

Since there are multiple values for the same index, they'd all have "key" used to access it-- the french might be "fr", chinese "zh", etc. And since indexes are directly related to meaning, people would need to manually specify when a "block" ends and begins-- a simple keybinding in text-editors could ease that a lot. Some additional add-ons for visualizing the different blocks would make it easier to move blocks around in the file, etc.

There also ought to be a key designated as the default for each file-- "en" is safe, for compatibility levels.

If this is implemented on the system-library-side, core functions for opening files and reading data streams should accept an additional argument-- key. If the key isn't specified, then the default key is assumed, and the functions only pass along a data-stream (or what have you) with the file of default indexes. Thus compatibility with old programs that don't understand meta-plaintext etc is preserved. Or something like that.

3